Thanks JOhn for the tip...
I take it it was disabled since it is still in development?
I tried it, but you have to manually match the pairs it looks like to me?
In my API way of running paired end, I actively search for the matching read 2
for every read1 I get (_R1 and _R2 suffix)...We need to
The general case is hard and it was brought up repeatedly at the
Galaxy community conference. One path might be this work
(https://bitbucket.org/galaxyp/galaxy-central-homogeneous-composite-datatypes)
on defining datasets that represent homongenous collections of files,
but there are no easy
Very likely you have to use the API for these kinds of workflows.
The UI for Galaxy is very limited in workflows that deviate from the One Input
paradigm.
Even for the most common workflow (paired end DNA sequencing of multiple
samples ) you have to resort to using the API...Puzzling...
