Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DirectiveDescriptionDefault
--job-name=...A descriptive name of the jobScript name
--output=...      Path to the file where standard output is redirected. Special placeholders for job id (%j) and the execution node (%N)slurm-%j.out
--error=...Path to the file where standard error is redirected. Special placeholders for job id (%j) and the execution node (%N)output value
--workdir=...Working directory of the job. The output and error files can be defined relative to this directorysubmitting directory
--qos=...Quality of Service (or queue) where the job is to be submittednormal
--time=...

Wall clock limit of the job. Note that this is not cpu time limit

The format can be: m, m:s, h:m:s, d-h, d-h:m or d-h:m:s

qos default time limit
--mail-type=...Notify user by email when certain event types occur. Valid values are: BEGIN, END, FAIL, REQUEUE and ALLdisabled
--mail-user=...email address to send the emailsubmitting user
--ntasks=..Allocate resources for the specified number of parallel tasks. Note that a job requesting more than one must be submitted to a parallel queue. There might not be any parallel queue configured on the cluster1
title
Info

You can also use these options as command line arguments to sbatch.

Job variables

Inside a job,  you can benefit from some variables defined by SLURM automatically. Some examples are:

  • SLURM_JOBID
  • SLURM_NODELIST
  • SLURM_SUBMIT_DIR