Hi,
I am trying to pass some key-value pairs to the result of a tool (such as the
original sample name) but I cannot find a way to do this in the galaxy XML tool
definitions.
I am simply trying to retain in all the data files I produce, the name of the
original sample which the results are rel
This bug irritated me, so I fixed it. Essentially add_file() in upload.py is
not in on the joke that local dirs are relative paths and need the absolute
path tacked onto it.
Is there a written process on how to submit the fix? I could not find it.
Thanks,
Ted
diff -r 21b645303c02 tools/data
I digged some more and I guess I could use the rename dataset option in a
workflow, but I can't find how I can rename a dataset using the original input
name.
I tried to use the same notation as those used in the tools (such as
${input.name}) but that just treats the input.name as a user provide
On Sat, Dec 31, 2011 at 11:43 PM, Thon deBoer wrote:
> I digged some more and I guess I could use the rename dataset option in a
> workflow, but I can't find how I can rename a dataset using the original
> input name.
> I tried to use the same notation as those used in the tools (such as
> ${input
Thanks, but ${foo.name} did not work in the workflow to rename an output file.
It takes ${foo.name} to be a user provided parameter.
${foo.name} will definitely work in tool definitions, but that means I have to
change ALL the default tool names for all the tool in galaxy...Surely there
must be
On Sun, Jan 1, 2012 at 12:29 AM, Thon Deboer wrote:
> Thanks, but ${foo.name} did not work in the workflow to rename an output
> file. It takes ${foo.name} to be a user provided parameter.
>
> ${foo.name} will definitely work in tool definitions, but that means I have
> to change ALL the default t