Hi,
I would like to start a local galaxy instance allowing user-defined cpu number.
In the deployment I want to use the local plugin in the job_conf as shown below.
Does anyone have an example on how to do that using a combination of job_resource_params_conf.xml
and job_conf.xml
What I understand so far is that:
- The
job_conf/destination/parameters
local_slots
is responsible to set theGALAXY_SLOT
environment variable when associated to a local runner.
My job_conf.xml
file is as follow:
<?xml version="1.0"?>
<job_conf>
<plugins>
<plugin id="local" type="runner" load="galaxy.jobs.runners.local:LocalJobRunner"/>
</plugins>
<destinations default="local">
<destination id="local" runner="local">
<param id="local_slots">4</param>
</destination>
</destinations>
<resources default="default">
<group id="default">local_slots</group>
</resources>
</job_conf>
My job_resource_params_conf file is as follow:
<parameters>
<param label="local_slots" name="local_slots" id="local_slots" type="integer" min="1" max="32" value="4" help="number of cpu" />
</parameters>
With this, the GALAXY_SLOT
environment variable is set to 4
. Without the line <param id="local_slots">4</param>
it is not set and defaults to 1 on most tools.
The number of threads specified by user is not respected using this config or some variants I have tried.
Can everyone provide me with an example on how to use the job_resource_params_conf.xml
with the local plugin ?
Thank you,