You're correct in that currently the workflow API affords no method for runtime
modification of tool parameters, other than inputs. Depending on your needs,
it might be feasible to have a few static workflows that you reuse often via
the workflow API. If that isn't the case, and you think it'd be likely that
you'll want to, say, programmatically modify parameters at runtime based on
input data heuristics, then the API does need to be extended. The first place
to look at would be lib/galaxy/web/controllers/workflow.py (run() method), to
see the general approach to running workflows and providing parameters in the
existing infrastructure. Then, see the API version at
lib/galaxy/web/api/workflows.py (create() method) for a comparison.
Let me know if you need any help with this at all. Once it's done, if you're
willing, we'd certainly like to merge the changes back in and include the
functionality in the base galaxy distribution.
On Dec 5, 2011, at 5:10 PM, Richard Park wrote:
> I was wondering what would be the best way to extend Galaxy's API
> functionality to allow for runtime modification of tool parameters?
> I have successfully been able to run workflows programmatically using
> the API, following the basic steps in:
> However, it is unclear to me, what would be the best way to run
> workflows through API with specific parameters at various steps.
> Should I generate new workflows for every workflow that requires
> different parameters and upload this to galaxy? Or would it be better
> to extend the API to allow for runtime parameter configuration? If
> this is the case, any pointers on how to extend this would be greatly
> Thank you,
> Richard Park
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at: