Thanks Jeremy
I've given up on that approach to nested workflows - too inefficient,
too fragile. If I have lots of time (and a grad student to help out)
I've got some ideas about having a deep look at the tool runner side of
Galaxy with an eye to efficiently implementing the mapping of input data
Peter,
I'm not ignoring you. However, there are others on the Galaxy team that are
more familiar with the API and can provider better answers. I expect they'll
chime in soon to address your questions.
Best,
J.
On May 20, 2012, at 5:39 PM, Peter van Heusden wrote:
Hi Jeremy
I'm need this
Hi Jeremy
I'm need this for something I'm implementing at the moment, and how I'm
thinking about it is making a tool that uses the API to call a workflow.
There are a few problems though, correct me if I'm wrong:
1) In order to make an input history item available to the called
workflow, the
Nested workflows aren't yet possible, but they're definitely something we'd
like to do in the future.
Best,
J.
On May 17, 2012, at 9:48 AM, Peter van Heusden wrote:
Hi there
Is there a way in Galaxy to use workflows as components in workflows?
I've got two datasets that start as Genbank
I would like to reiterate this point in as far as this single feature is preventing us from implementing large workflows in our organization in Galaxy...It is just not feasible to re-do all workflow steps each time in complex studies...Is there any way we can speed up the implementation of this
Hi there
Is there a way in Galaxy to use workflows as components in workflows?
I've got two datasets that start as Genbank files and are processed
(features extracted, translated to AA) by a small workflow, and then
BLASTed against one another. Ideally I'd like to modularise the initial
steps as
