Hi Dannon,
Is there a guide or format you need for submitting pull requests? I'd
like to contribute my API enhancements specifically for importing,
creating, deleting workflows. I also had a delete library api call,
but I think that was also added to the galaxy code recently.
thanks,
Richard
On
Hi Richard, that'd be great! The easiest thing for us is a bitbucket pull
request on a clean fork (with your changes applied) of galaxy-central.
-Dannon
On Jun 21, 2012, at 4:54 PM, Richard Park wrote:
Hi Dannon,
Is there a guide or format you need for submitting pull requests? I'd
like to
Richard,
For specifying or changing species, you may want to inspect the input via the
API (api/histories/id/contents/id/) and snag the genome_build attribute
that way. Or am I missing the issue you're running into?
As an aside, I'd love to look at the runtime parameter specification changes
Hi Dannon,
Thanks for the pointers. I am new to developing to galaxy and any help
or guidance would be much appreciated. Are there any docs to help me
understand how to code/debug galaxy? And if you have any suggestions
for the general process of extending the API i would be very grateful.
thanks,
Hello,
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:
scripts/api/execute_workflow.py.
Richard,
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