Paul:

I was about to suggest the same - great idea!
++

brad
On Feb 14, 2012, at 11:08 AM, Dannon Baker wrote:

> Hi Paul,
> 
> Thanks for this suggestion, it would definitely make sense to create a 
> reference to the actual workflow inputs in the new history.  I'll see what I 
> can do!
> 
> -Dannon
> 
> On Feb 14, 2012, at 11:05 AM, Paul Gordon wrote:
> 
>> Hi all,
>> 
>> I have noticed that when I run a workflow with output to a new history, the 
>> data sets used as input to the workflow do not become part of the new 
>> history.  Unfortunately, if a job fails in the workflow, the "rerun" 
>> interface for the job can't access the original data…it needs to be manually 
>> imported.  While this is a minor annoyance, it becomes quite the pain if you 
>> ran the workflow for a bunch of input files.  Can I put in a request that 
>> input data be imported automatically into workflow run histories, or have I 
>> missed something in the workflow run options?
>> 
>> Cheers,
>> 
>> Paul
>> 
>> 
>> ___________________________________________________________
>> 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:
>> 
>> 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:
> 
>  http://lists.bx.psu.edu/

Brad Langhorst
langho...@neb.com
978-380-7564




___________________________________________________________
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:

  http://lists.bx.psu.edu/

Reply via email to