Doesn't this violate one of the basic tenets of Galaxy - reproducibility? 
Without the ability to provide full traceability to the inputs, one can make no 
guarantees about the outputs.

John Duddy
Sr. Staff Software Engineer
Illumina, Inc.
9885 Towne Centre Drive
San Diego, CA 92121
Tel: 858-736-3584

[] On Behalf Of Paul-Michael Agapow
Sent: Monday, May 16, 2011 7:45 AM
Subject: [galaxy-dev] A tool with no inputs

One of my colleagues is having trouble developing a peculiar tool: it has no 
inputs. This makes sense in our local context - it fetches some constantly 
updating remote data for the current user - but implementing it has escaped our 
skill. Galaxy complains about a tool with no params (i.e. an empty <inputs>). 
It complains about a tool with no <inputs> tag. Hidden input fields don't seem 
to work (i.e. looks like I'm getting the cached value of the form).

It is admittedly a fairly niche use-case and we could put in a dummy field and 
simply not use it, but that seems inelegant. Any suggestions?

Paul Agapow (
Bioinformatics, Centre for Infections, Health Protection Agency


************************************************************************** The 
information contained in the EMail and any attachments is confidential and 
intended solely and for the attention and use of the named addressee(s). It may 
not be disclosed to any other person without the express authority of the HPA, 
or the intended recipient, or both. If you are not the intended recipient, you 
must not disclose, copy, distribute or retain this message or any part of it. 
This footnote also confirms that this EMail has been swept for computer 
viruses, but please re-sweep any attachments before opening or saving. 
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