yep, that works. modifying it to only display with 'input dataset' makes
sense.
Just curious, but how stable is the workflow API for IO nodes? For instance, I
could see creating a custom input node for splitting data for parallel
processing, then combining processed data into a final report
Oh, I see what you're doing, thanks for clarifying. Add an Input Dataset step
and it should work fine. The original intent for multiple input scaling was
really designed explicitly for that scenario using the Input Dataset workflow
steps and the fact that it works for some tools directly was a
Minimal case is a single-node workflow with FastQC (tophat also had the same
problem):
http://test.g2.bx.psu.edu/u/cjfields/w/test
maybe it's tool-specific?
chris
On Feb 3, 2012, at 1:10 AM, Dannon Baker wrote:
> Can you share a workflow that's failing for you on test with me? I just
> tri
Can you share a workflow that's failing for you on test with me? I just tried
a simple workflow with nothing but an input and FastQC and ran with multiple
inputs successfully.
Thanks!
Dannon
On Feb 2, 2012, at 11:15 PM, Fields, Christopher J wrote:
> Just filed as Issue #714 on bitbucket.
Just filed as Issue #714 on bitbucket. I noticed that multiple input seems to
be broken on workflows when selecting more that one file (a single file works).
This is happening on our local instance, using Jan 27 galaxy-dist release, as
well as both main/test.g2.bx.psu.edu Galaxy servers (latte
