template.file. This
file is processed with brew and then submitted to the queue using the
sbatch command. Jobs are killed using the scancel command and
the list of running jobs is retrieved using squeue. The user must
have the appropriate privileges to submit, delete and list jobs on the
cluster (this is usually the case).The template file can access all resources passed to submitJobs
as well as all variables stored in the JobCollection.
It is the template file's job to choose a queue for the job and handle the desired resource
allocations.
Note that you might have to specify the cluster name here if you do not want to use the default, otherwise the commands for listing and killing jobs will not work.
makeClusterFunctionsSlurm(template = findTemplateFile("slurm"),
clusters = NULL)character(1)]
Path to a brew template file that can be used for the job description.
Alternatively, the template as a single string (including at least one newline “\n”).
Defaults to a heuristic which looks for a template file in the following locations and picks
the first one found:
user_config_dir); on linux is is usually “~/.config/batchtools/slurm.tmpl”.
character(1)]
If multiple clusters are managed by one Slurm system, the name of one cluster has to be specified.
If only one cluster is present, this argument may be omitted.
Note that you should not select the cluster in your template file via #SBATCH --clusters.ClusterFunctions].makeClusterFunctionsDocker,
makeClusterFunctionsInteractive,
makeClusterFunctionsLSF,
makeClusterFunctionsMulticore,
makeClusterFunctionsOpenLava,
makeClusterFunctionsSGE,
makeClusterFunctionsSSH,
makeClusterFunctionsSocket,
makeClusterFunctionsTorque,
makeClusterFunctions