Ahh, I see what you're asking. I thought you were referring to providing dataset inputs by name, my mistake.Currently running workflows through the API doesn't support defining inputs other than datasets, that is, it expects workflows to be fully pre-defined with nothing 'set at runtime' other tha
Huh? I have many string inputs to some particular workflow steps...Those are parameters etc that need to be entered or chosen from a dropdown..How would we deal with those kinds of entries into a workflow in the API? Or do all of them have to be pre-set?ThanksThonOn Feb 21, 2012, at 04:21 PM, Danno
Hi Dannon,
I think he is referring to the dataset input key in the dictionary.
Thon, I think this thread could be helpful:
http://galaxy-development-list-archive.2308389.n4.nabble.com/Using-workflows-with-steps-with-several-inputs-through-the-API-td4267374.html
In summary, you want to ./display
There is no string input. If the string you're looking for is, say, the name
of a dataset what you'd do is make separate calls to the history and workflow
API.
For example, if you had a history "My important history", and a dataset "My
input dataset", and no knowledge of the id's (as you shoul
One more question...How do I pass a string value to one of the workflow input steps?Is there an equivalent of ldda and hda, maybe "str"..So 38=str="Some value"Where could I find a list of the expected dataset sources?ThanksThonOn Feb 21, 2012, at 03:46 PM, Dannon Baker wrote:Hi Thon, You have the
Hi Danon,thanks for the info...Indeed I had tried hda (I sorta figured H was for History, LD was for Library Dataset) but I got an error complaining about step 91 (I only had one step) but I figured out that the API probably uses a different number of the steps, so this worked./display.py 92cc01ed9
Hi,
Also, if it is in fact a history id and you will be using 'hda',
remember to use 'hist_id=' instead of 'Test API History'.
-Carlos
On Tue, Feb 21, 2012 at 6:46 PM, Dannon Baker wrote:
> Hi Thon,
>
> You have the right idea about what's going wrong here. Galaxy is trying to
> pull up a lib
Hi Thon,
You have the right idea about what's going wrong here. Galaxy is trying to
pull up a library dataset with the ID you specify, but it doesn't exist.
In this context, src refers to the 'type' of dataset input id, more
specifically whether it's from a history or library. 'hda' indicates
Hi,I tried to run a workflow with the API, but get an Error 500 when I try to run the WF...The paster.log shows the following error...$ workflow_execute.py 92cc01ed93dc0f0fc91e3ded35497c0a http://srp106:8080/api/workflows ebfb8f50c6abde6d 'TEST the API' '1=ldda=7c5ebce002fc9d5c'Paster.loggalaxy.web
