On Thu, Oct 16, 2014 at 11:05 PM, Wolfgang Maier
wolfgang.ma...@biologie.uni-freiburg.de wrote:
Hi,
this is just to make sure: the GALAXY_SLOTS environmental variable set by
Galaxy when running tools will always be a number = 1 with 1 being the
default if nothing else is configured in the job
On 10/17/2014 10:39 AM, Peter Cock wrote:
On Thu, Oct 16, 2014 at 11:05 PM, Wolfgang Maier
wolfgang.ma...@biologie.uni-freiburg.de wrote:
Hi,
this is just to make sure: the GALAXY_SLOTS environmental variable set by
Galaxy when running tools will always be a number = 1 with 1 being the
default
Hi,
I'm not sure to understand ... I was but not now anymore :P
When you find \${GALAXY_SLOTS:-4} in a wrapper, and if you haven't set a
tool_runner (-pe thread 8) for this tool, by default it will use 4
splots ! No ?
Is there a global GALAXY_SLOTS variable ?
Thanks
Gildas
Le 17/10/2014
In theory GALAXY_SLOTS is now always set unless Galaxy is pretty old -
I still think it is important for tools to specify defaults using the
\${GALAXY_SLOTS:-4} idiom so that tools themselves don't have explicit
dependencies on the Galaxy runtime and in case new resource managers
or job runners
On 10/17/2014 02:47 PM, John Chilton wrote:
In theory GALAXY_SLOTS is now always set unless Galaxy is pretty old -
I still think it is important for tools to specify defaults using the
\${GALAXY_SLOTS:-4} idiom so that tools themselves don't have explicit
dependencies on the Galaxy runtime and
Hi Wolfgang,
\${GALAXY_SLOTS:-4} in this case will default to 4 if you have not
configured it in job_conf.xml. Otherwise yes, it will be 1.
Ciao,
Bjoern
Am 17.10.2014 um 00:05 schrieb Wolfgang Maier:
Hi,
this is just to make sure: the GALAXY_SLOTS environmental variable set
by Galaxy when
