[galaxy-dev] January 2017 News of the Galaxy: Register now for GAMe 2017!

Hello all, The *January Galaxy News * is hot off the press: - *Galaxy Australasia Meeting (GAMe 2017) *: February 3-9, Melbourne, Victoria, A

Re: [galaxy-dev] wrapper for tool with multiple outputs

Perfect this is working! thanks Jochen On 04.01.2017 13:27, Devon Ryan wrote: Try the following: If you have it output to the working directory then that might solve the problem. Devon -- Devon Ryan, Ph.D. Email: dpr...@dpryan.com Data Manager/Bioinformatician Max

Re: [galaxy-dev] wrapper for tool with multiple outputs

Try the following: If you have it output to the working directory then that might solve the problem. Devon -- Devon Ryan, Ph.D. Email: dpr...@dpryan.com Data Manager/Bioinformatician Max Planck Institute of Immunobiology and Epigenetics Stübeweg 51 79108 Freiburg Germany

Re: [galaxy-dev] wrapper for tool with multiple outputs

Thanks Devan, I just changed it! I have an other question. I used this to catch the output files: visible="true" /> format="bam" visible="true" /> visible="true" /> my problem is that I first get an empty file in

Re: [galaxy-dev] wrapper for tool with multiple outputs

Hi Jochen, Don't have it use /tmp, but rather the current working directory and then everything will work. Galaxy jobs are run in individual working directories, so you can exploit that to ensure that files aren't overwritten. Devon -- Devon Ryan, Ph.D. Email: dpr...@dpryan.com Data Manager/Bioin

[galaxy-dev] wrapper for tool with multiple outputs

Hi, I have a tool that produces multiple output files a log file, two bam files. (https://github.com/nugentechnologies/nudup) The tool it self provides an option called --out to specify a path to a directory with a prefix that will be added to the output files: --out /tmp/out this will pro

[galaxy-dev] installation error on venv dependencies.xml

Hi All, I posted my question before the holidays but i got not reply. Can someone please point me in the right direction? I am having some problems with my tool dependencies to setup a python venv. Dependencies.xml looks like this: [X] [X][cid:7b48a44d-07dd-4838-8f90-5024d9d22593] When i instal