The only rather stupid-looking solution I have is to extract, as part of a workflow, each multi-sequence fasta (it's always eight of them) with __EXTRACT_DATASET__, then run vapor on each of those datasets and the list:paired collection.
I can live with that if it's the only way, but don't want to build something dumb.
IIRC we do support that in the backend, but haven't enabled this for lack of a user interface. Just to be sure, can you share a history with your workaround ? I wonder if this could also be done by nesting your collection deeper
hey workflow gurus! staramr specifies species using a drop down (this is necessary to run PointFinder) - while the user could set this by changing the "default tool parameters" at pipeline invocation time, is there any way to ask for a user input parameter for the pipeline (so it shows up right at the top like other pipeline inputs) and connect this to the dropdown?
Guess we got ~ 2-3 weeks to get the user interface in, it seems doable if there's no too many unexpected things popping up
Some iuc tools are not up to date in usegalaxy.org, this makes some upgrade PR failing, would it be possible to update them (toolshed.g2.bx.psu.edu/repos/iuc/rgrnastar/rna_star/2.7.8a+galaxy1 and toolshed.g2.bx.psu.edu/repos/devteam/bowtie2/bowtie2/2.5.0+galaxy0). Thanks