understand, the $__new_file_path__ option is changed in the
universe_wsgi.ini file.
Regardless, the extra files created from the tool does not show in the galaxy
history.
Any ideas?
Best,
Martin Christiansen
: Martin Christiansen martinchristianse...@hotmail.com
To: galaxy-dev@lists.bx.psu.edu galaxy-dev@lists.bx.psu.edu
Subject: [galaxy-dev] Multiple output datasets
Date: Wed, 27 Aug 2014 12:04:46 +0200
Hi all,
I'm implementing a tool for our local galaxy instance which has multiple output
datasets
',
output1.id, name, 'visible', file_type, dbkey(build) ) Where the '_dbkey'
portion of the name is optional.
Stef
- Original message -
From: Martin Christiansen martinchristianse...@hotmail.com
To: Stef van Lieshout stefvanliesh...@fastmail.fm,
galaxy-dev@lists.bx.psu.edu galaxy
and the output directory path. Save all the extra output files to that
directory with the exact format: primary_id_somename_visible_filetype (eg
primary_546_output2_visible_bed)
Stef
- Original message -
From: Martin Christiansen martinchristianse...@hotmail.com
To: Stef van Lieshout
,
Galaxy stores all information about a tool and it's parameters in a
database.
I suppose if something is wrong with your tool, under some circumstances, it
can't be stored in the database.
Cheers,
Bjoern
2014-08-12 9:23 GMT+02:00 Martin Christiansen
martinchristianse...@hotmail.com
Hi Björn,
It looks like this.
tool id=screen_reads name=Screen Reads
descriptionagainst hg19/description
command interpreter=bashscreen_reads.sh $Project.input $Project.samples
$Project $Samples /command
inputs
conditional name=Project
param name=input type=select label=Select
.
Am 12.08.2014 um 08:51 schrieb Martin Christiansen:
Hi Björn,
Most certainly. I have posted it below.
tool id=screen_reads name=Screen Reads
- add here a version number version=0.1
descriptionagainst hg19/description
command interpreter=bashscreen_reads.sh $Project.input
...@gmail.com wrote:
Hi,
Galaxy stores all information about a tool and it's parameters in a
database.
I suppose if something is wrong with your tool, under some circumstances, it
can't be stored in the database.
Cheers,
Bjoern
2014-08-12 9:23 GMT+02:00 Martin Christiansen
