Wolfgang Maier
Wolfgang Maier
Are you still facing this issue, or did you manage to resolve it?
So DESeq2 first: thing is it requires replicates as you found out already. If you don't have those, you cannot use DESeq2. Probably the best you could do is calculate...
For the strange workflow parameter error: - which browser are you doing this in (there maybe some subtle issues similar to what you are seeing with Microsoft browsers - both...
> Like in the filter for selects with dynamic options. Note actually in the select case we check if the referred dataset has the dbkey set while we do this...
Not only is it still the fastest way as @mvdbeek points out, but I'm also still using this a lot in daily work. Mostly out of old habits, but, importantly,...
Ah, the sanitization issue is solved by using a tool-wide ``. Now I know why existing data_source tools include that :-) That leaves only the multiple translator calls.
Ok, so once more I'm happy with my changes and think they are ready for reviewing.
> I am a bit wary about doing that. Was so too, that's why I didn't touch this in my prior PR. However, out of the built-in data source tools...
> Even if easy to fix, breaking tools is something Galaxy works hard to avoid. We have tool profiles to mitigate that, maybe we could consider applying it here. That's...
The one failing test appears to be unrelated again :-)