OK...I tried this and it no longer removes the entries from the history...Thanks!I do see that each of the new histories I create still have a reference to some of the other files I pick up from the library (such as dbSNP) but those entries in the history have the number "None" in stead of the usua
On Jul 5, 2012, at 5:40 PM, Anthonius deBoer wrote:
> WOW...I guess I know how you guys that designed the API think :)
>
> Small other question...Is it possible (yet) to pass a parameter to the API
> yet, that is NOT an input step?
> Things that get defined in the workflow step such as {Analysis_
WOW...I guess I know how you guys that designed the API think :)Small other question...Is it possible (yet) to pass a parameter to the API yet, that is NOT an input step?Things that get defined in the workflow step such as {Analysis_Run} that get filled in at runtime?Now it reverts to "X__oc__Analy
On Jul 5, 2012, at 5:33 PM, Thon Deboer wrote:
> data['no_add_to_history']="True" ?
Should do it.
___
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,
Thanks for the fast reply...
How do I add this to the "payload"?
Is it part of ds_map or something else?
data['workflow_id'] =
data['history'] =
data['ds_map'] = {}
data['no_add_to_history']="True" ?
or is it part of the actual definition of the input step?
Thanks
T
I see the bug you're running into. As a temporary solution, executing
workflows via the API with 'no_add_to_history' in the payload should work as
expected. I'll have a permanent fix out shortly.
-Dannon
On Jul 5, 2012, at 5:12 PM, Thon Deboer wrote:
> Hi,
>
> I am continueing to struggle w
Hi,
I am continueing to struggle with the API
I have created a workflow execution engine that submits a workflow using the
examples in the API (scripts/api).
When I run the WF on data in the LIBRARIES everything works fine.
But when I choose a HISTORY as my source of data, the WF executes f
