Re: [galaxy-dev] Question concerning the xml file for local tools with multiple output files.

2014-03-28 Thread Nate Coraor
Hi Lifeng, Another option would be the 'from_work_dir' option to the data tag. Have a look at the tophat repository in the Tool Shed for an example: http://toolshed.g2.bx.psu.edu/view/devteam/tophat --nate On Tue, Mar 25, 2014 at 11:29 AM, Hans-Rudolf Hotz hansrudolf.h...@fmi.chwrote:

Re: [galaxy-dev] Question concerning the xml file for local tools with multiple output files.

2014-03-25 Thread Hans-Rudolf Hotz
Hi Lifeng The easiest way to execute your script will be to provide a wrapper script (written in your preferred language, eg Python, perl, etc). Call the wrapper script like this: commandwrapper $input $output1 $output2/command and define $output1 $output2 according to your needs:

Re: [galaxy-dev] Question concerning the xml file for local tools with multiple output files.

2014-03-25 Thread Hans-Rudolf Hotz
Hi Lifeng I am glad to hear it works WRT your thoughts about using a wrapper script for each tool: I agree it might help you to standardize your tools, however it also introduces an extra step, which needs to be taken care of if you want to change/upgrade your tool. Personally, I would only

Re: [galaxy-dev] Question concerning the xml file for local tools with multiple output files.

2014-03-25 Thread Lifeng Lin
works like a charm. Thank you! I start to wonder if i should use this wrapper approach on all scripts regardless of the original input-output format for standardized integration, and possible automated integrations in the future. On Tue, Mar 25, 2014 at 6:53 AM, Hans-Rudolf Hotz