Question: #{input_name} Doesn't Actually Work
gravatar for madkisson
3.2 years ago by
United States
madkisson30 wrote:


I've been trying to use the #{input_name} code that is recommended in the workflow editing page [link given is:]. This would save me a great deal of time if i could get it to work. All I ever get is a blank space where that code is and then whatever text I add in addition to that. Any thoughts?



workflow tophat • 664 views
ADD COMMENTlink modified 3.2 years ago by Jennifer Hillman Jackson25k • written 3.2 years ago by madkisson30
gravatar for Jennifer Hillman Jackson
3.2 years ago by
United States
Jennifer Hillman Jackson25k wrote:


The example term #{input_name} is often not the actual name of the input file (files) for tools. Each has its own variable name inside of the curly brackets { }.

These values were earlier displayed in the workflow editor and will be again. A ticket to track this restoration of functionality is here:

As a work-around, each tool wrapper will specify the tools inputs and outputs by variable name. Depending on the complexity of the tool, this can be easy or difficult to interpret. But if interested, the Tool Shed (once logged in) will allow you to browse repository tip files in a UI interface quickly to obtain this information. 

Apologies for the current inconvenience, Jen, Galaxy team

ADD COMMENTlink modified 3.2 years ago • written 3.2 years ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 173 users visited in the last hour