I'd like to do the same thing that Tanguy described. I'm trying to figure
out the syntax to this within the workflow editor, but can't quite get it
right. In your example Dannon, would you just set ${dataset_name} as the
"Name" for your "Input dataset" to capture the input dataset name as a
varia
The input dataset steps do not use workflow parameters as they don't
actually create output datasets, but rather act as more of a temporary
handle. Remove the parameter tags from the input steps and just
referring to those same parameter names in the subsequent steps you
wanted to use them wit
Hi Dannon,
Sorry, I guess I still don't quite get it. So I should keep the Input
Dataset name the default which is "Input Dataset". In the next subsequent
step in the workflow I then edit step actions Rename Dataset/output_file
with "${Input Dataset} groomed", for example. This gives me the sam
Ahh, I understand your confusion now. The previous bit you pointed out
was an error indeed, but not the one you were running into. The
variable name should be whatever you want it to be, it doesn't have to
map to an existing value like "Input Dataset", but there's an issue with
the way the ta
I get it now!!
I did my Rename Dataset/output_file with a variable ${input}.
I chose that because I thought that would give me the name of the input file to
that module, which I'm looking to carry on through out the run of my workflow
(though actually I'd like the file name minus the file ext
On 04/13/2011 12:30 PM, Dave Walton wrote:
Is there anyway to access the value of fields that are part of the workflow. Taking the
"Input Dataset" example, that is an input file that goes into my next module. I'd like
to grab the name of that input file, and then append it with a new extensio
Hi,
Thanks for the tips and CC!
Cheers,
Tanguy
___
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.p
