Thanks for the response.

I am not seeing this behavior in my workflows.  When I go to run the workflow, 
a gatk dbsnp file is the default selected for all my input dataset steps, even 
though some of them must be fastqillumina or bed/interval files, etc (depending 
on the step they are wired into).  All files in my history are exposed in the 
drop down for each input dataset step, vs. narrowing it down by type.

Ann


On Oct 12, 2011, at 1:30 PM, Dannon Baker wrote:

> Ann,
> 
> Unless I misunderstand what you're asking for, this should already be the 
> case.  For instance, if a workflow step takes in a file of 'tabular' type, 
> only tabular files (and subtypes, including interval, etc.) should be 
> presented as dropdowns in the list.  Types such as plain text, binary files, 
> etc., should be excluded.  Are you seeing other behavior?
> 
> Thanks for using Galaxy!
> 
> -Dannon
> 
> 
> 
> On Oct 12, 2011, at 02:17 PM, Ann Black <annbl...@eng.uiowa.edu> wrote:
> 
>> I am developing a custom workflow in galaxy. I have 4 input files that need 
>> to be fed into various steps of the workflow. I would like to be able to 
>> specify a data type for the inputs such that the pre-populated drop downs 
>> are filtered to datasets of the appropriate type as well as being able to do 
>> some simple validation before the workflow begins. Is there someway to do 
>> this?
>> 
>> Thanks much,
>> 
>> Ann
>> ___________________________________________________________
>> 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.psuedu/

___________________________________________________________
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