Hi Dannon,
I am finally getting around to the workflow api.  I am having trouble
with a couple things.  First, I am trying to get the
workflow_execute.py functioning for a workflow that I have here.  I
think I have everything down but how to define the dataset.
Basically, I am trying to reverse engineer the long dataset, workflow
and history ids, and I have been doing so by grabbing their respective
urls and pulling out the ids.  But the workflow execute hash is
encoded like this for the script as far as I can tell:

<hid>=<???>=<hashed dataset id>

But I am kinda stuck at what these guys actually mean.

Which brings me to my general question.  While I appear to be close in
selecting the correct history and workflow ids, it only works right
now as a proof of concept since I would need to sort of generate these
on my own for a user to run a workflow via the galaxy interface.  It
seems you are hashing these history, workflow and dataset ids, but I
am not really sure what you are using to hash them.  Looks like not a
SHA1 sum.  Given only access to the galaxy database, I would like to
execute a workflow, so I would need to be able to generate the hashed
values to throw at the api.  Does that make sense?

Finally, can I generate an api key programatically as well?  Not the
end of the world, but it would be nice.

Thanks much for your help,


On Sat, Mar 5, 2011 at 2:04 PM, Darren Brown <br...@centerspace.net> wrote:
> Hello Dannon,
> This looks exactly like how I would like to run a workflow.  I'll be
> trying this out next week and will let you know how it goes.  Thanks
> much!
> Darren
> On Sat, Mar 5, 2011 at 1:51 PM, Dannon Baker <dannonba...@me.com> wrote:
>> Darren,
>> A first pass at adding workflows to the Galaxy API is now available.  For an 
>> example of how to execute a basic workflow, see 
>> scripts/api/execute_workflow.py.  An example of how this might integrate 
>> into a slightly more complex script using library uploads is available at 
>> scripts/api/example_watch_folder.py.  This preliminary version doesn't allow 
>> runtime modification of tool parameters, so the workflow must not make use 
>> of the 'set at runtime' option, but that feature will be available soon.
>> The API itself is relatively undocumented, though some basic hints and usage 
>> examples can be found in /scripts/api/README
>> Let me know if you have questions or feedback!
>> -Dannon
>> On Mar 2, 2011, at 2:40 PM, Darren Brown wrote:
>>> Hello Dannon,
>>> That is surprising and excellent!  Can't wait to hear more.
>>> Take care,
>>> Darren
>>> On Wed, Mar 2, 2011 at 11:38 AM, Dannon Baker <dannonba...@me.com> wrote:
>>>> Darren,
>>>> While this is not currently possible, I'm currently finishing up a first 
>>>> pass on a workflow API that will allow this sort of interaction and hope 
>>>> to have an early version available by the end of this week.  I can update 
>>>> you when that has been committed.
>>>> -Dannon
>>>> On Feb 24, 2011, at 9:29 PM, Darren Brown wrote:
>>>>> Hello folks,
>>>>> I am using a workflow that needs to be run many times on many
>>>>> different inputs.  I have hacked around and figured out how to pull
>>>>> multiple inputs from a history, but I am a little baffled on how to
>>>>> run a galaxy workflow programatically.  I have searched around fairly
>>>>> exhaustively and am wondering if this is something that anyone else
>>>>> has come across and accomplished.  And links or pointers?
>>>>> Take care,
>>>>> Darren
>>>>> _______________________________________________
>>>>> To manage your subscriptions to this and other Galaxy lists, please use 
>>>>> the interface at:
>>>>>  http://lists.bx.psu.edu/

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:


Reply via email to