Hi Jennifer,
Thanks for the reply.
However, my question was not about building tools.
My question was about building a workflow (using the workflow editor
with existing tools), as a user of galaxy.
Using the workflow editor, when I create a workflow using a tool that
allows a variable number
Hello Daniel,
I had the same problem when I started to work with Galaxy workflows.
My workaround is:
1) Modify the first tool of the workflow
Make it work on a simple text file that contains a list of input file
paths (one by line) instead of several files.
2) Create a galaxy tools that
Hi Daniel,
My apologies! I misunderstood what your question was about.
You are correct, the required inputs are defined when the workflow is
created. For tools that accept a variable number of inputs, when that
tool is added to a workflow, the run-time parameters, including expected
inputs,
Good Morning,
We are also interested in this capability. To give a concrete example, we
sometimes receive multiple sequence runs 1* for the same sample. We would
like to be able to process each run of the sample through BWA and then merge
them together, post process it a bit, and then send
This seems to fall within the recent discussion of map/reduce operators for
workflows, e.g. breaking large jobs up for embarrassingly parallel tasks, then
merging them back at some later point. Dannon mentioned some basic
functionality does exist within Galaxy to do this, but it's at an early
