Difference between revisions of "Annotated SLURM Script"
Moskalenko (talk | contribs) |
m (fixed analysis spelling) |
||
(22 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | [[Category: | + | [[Category:Scheduler]] |
− | + | This is a walk-through for a basic SLURM scheduler job script for a common case of a multi-threaded analysis. If the program you run is single-threaded (can use only one CPU core) then only use '--ntasks=1' line for the cpu request instead of all three listed lines. Annotations are marked with bullet points. You can click on the link below to download the raw job script file without the annotation. Values in brackets are placeholders. You need to replace them with your own values. E.g. Change '<job name>' to something like 'blast_proj22'. We will write additional documentation on more complex job layouts for MPI jobs and other situations when a simple number of processor cores is not sufficient. | |
− | This is a walk-through for a basic SLURM scheduler job script. Annotations are marked with bullet points. You can click on the link below to download the raw job script file without the annotation. Values in brackets are placeholders. You need to replace them with your own values. E.g. Change '<job name>' to something like 'blast_proj22'. | ||
− | + | {|cellspacing=30 | |
− | + | |-style="vertical-align:top;" | |
− | + | |style="width: 50%"| | |
− | < | + | ;Set the shell to use |
+ | <pre> | ||
#!/bin/bash | #!/bin/bash | ||
− | </ | + | </pre> |
;Common arguments | ;Common arguments | ||
* Name the job to make it easier to see in the job queue | * Name the job to make it easier to see in the job queue | ||
− | + | <pre> | |
− | < | ||
#SBATCH --job-name=<JOBNAME> | #SBATCH --job-name=<JOBNAME> | ||
− | </ | + | </pre> |
;Email | ;Email | ||
:Your email address to use for all batch system communications | :Your email address to use for all batch system communications | ||
− | + | <pre> | |
− | < | + | #SBATCH --mail-user=<EMAIL> |
− | + | #SBATCH --mail-user=<EMAIL-ONE>,<EMAIL-TWO> | |
− | </ | + | </pre> |
;What emails to send | ;What emails to send | ||
:NONE - no emails | :NONE - no emails | ||
:ALL - all emails | :ALL - all emails | ||
:END,FAIL - only email if the job fails and email the summary at the end of the job | :END,FAIL - only email if the job fails and email the summary at the end of the job | ||
− | + | <pre> | |
− | < | ||
#SBATCH --mail-type=FAIL,END | #SBATCH --mail-type=FAIL,END | ||
− | </ | + | </pre> |
;Standard Output and Error log files | ;Standard Output and Error log files | ||
:Use file patterns | :Use file patterns | ||
:: %j - job id | :: %j - job id | ||
− | :: %A- | + | :: %A-%a - Array job id (A) and task id (a) |
− | + | :: You can also use --error for a separate stderr log | |
− | < | + | <pre> |
#SBATCH --output <my_job-%j.out> | #SBATCH --output <my_job-%j.out> | ||
− | + | </pre> | |
− | </ | + | ;Number of nodes to use. For all non-MPI jobs this number will be equal to '1' |
− | ;Number of | + | <pre> |
− | |||
− | < | ||
#SBATCH --nodes=1 | #SBATCH --nodes=1 | ||
− | </ | + | </pre> |
− | ;Number of | + | ;Number of tasks. For all non-MPI jobs this number will be equal to '1' |
− | + | <pre> | |
− | < | + | #SBATCH --ntasks=1 |
− | #SBATCH --cpus-per-task= | + | </pre> |
− | </ | + | ;Number of CPU cores to use. This number must match the argument used for the program you run. |
− | ;Total job | + | <pre> |
− | + | #SBATCH --cpus-per-task=4 | |
− | + | </pre> | |
− | < | + | || |
− | #SBATCH --mem= | + | ;Total memory limit for the job. Default is 2 gigabytes, but units can be specified with mb or gb for Megabytes or Gigabytes. |
− | </ | + | <pre> |
+ | #SBATCH --mem=4gb | ||
+ | </pre> | ||
;Job run time in [DAYS]:HOURS:MINUTES:SECONDS | ;Job run time in [DAYS]:HOURS:MINUTES:SECONDS | ||
:[DAYS] are optional, use when it is convenient | :[DAYS] are optional, use when it is convenient | ||
− | + | <pre> | |
− | < | ||
#SBATCH --time=72:00:00 | #SBATCH --time=72:00:00 | ||
− | </ | + | </pre> |
;Optional: | ;Optional: | ||
:A group to use if you belong to multiple groups. Otherwise, do not use. | :A group to use if you belong to multiple groups. Otherwise, do not use. | ||
− | + | <pre> | |
− | < | ||
#SBATCH --account=<GROUP> | #SBATCH --account=<GROUP> | ||
− | </ | + | </pre> |
− | :A job array, which will create many jobs (called array tasks) different only in the '<code>$SLURM_ARRAY_TASK_ID</code>' variable | + | :A job array, which will create many jobs (called array tasks) different only in the '<code>$SLURM_ARRAY_TASK_ID</code>' variable |
− | + | <pre> | |
− | < | ||
#SBATCH --array=<BEGIN-END> | #SBATCH --array=<BEGIN-END> | ||
− | </ | + | </pre> |
;Example of five tasks | ;Example of five tasks | ||
− | :#SBATCH --array=1-5 | + | :<nowiki>#</nowiki>SBATCH --array=1-5 |
− | |||
− | |||
---- | ---- | ||
;Recommended convenient shell code to put into your job script | ;Recommended convenient shell code to put into your job script | ||
− | |||
− | |||
− | |||
− | |||
− | |||
* Add host, time, and directory name for later troubleshooting | * Add host, time, and directory name for later troubleshooting | ||
− | + | <pre> | |
− | < | ||
date;hostname;pwd | date;hostname;pwd | ||
− | </ | + | </pre> |
Below is the shell script part - the commands you will run to analyze your data. The following is an example. | Below is the shell script part - the commands you will run to analyze your data. The following is an example. | ||
* Load the software you need | * Load the software you need | ||
− | + | <pre> | |
− | < | ||
module load ncbi_blast | module load ncbi_blast | ||
− | + | </pre> | |
− | </ | ||
* Run the program | * Run the program | ||
− | + | <pre> | |
− | < | + | blastn -db nt -query input.fa -outfmt 6 -out results.xml --num_threads 4 |
− | blastn -db nt -query input.fa -outfmt 6 -out results.xml | ||
date | date | ||
− | </ | + | </pre> |
+ | |} |
Latest revision as of 20:49, 13 May 2024
This is a walk-through for a basic SLURM scheduler job script for a common case of a multi-threaded analysis. If the program you run is single-threaded (can use only one CPU core) then only use '--ntasks=1' line for the cpu request instead of all three listed lines. Annotations are marked with bullet points. You can click on the link below to download the raw job script file without the annotation. Values in brackets are placeholders. You need to replace them with your own values. E.g. Change '<job name>' to something like 'blast_proj22'. We will write additional documentation on more complex job layouts for MPI jobs and other situations when a simple number of processor cores is not sufficient.
#!/bin/bash
#SBATCH --job-name=<JOBNAME>
#SBATCH --mail-user=<EMAIL> #SBATCH --mail-user=<EMAIL-ONE>,<EMAIL-TWO>
#SBATCH --mail-type=FAIL,END
#SBATCH --output <my_job-%j.out>
#SBATCH --nodes=1
#SBATCH --ntasks=1
#SBATCH --cpus-per-task=4 |
#SBATCH --mem=4gb
#SBATCH --time=72:00:00
#SBATCH --account=<GROUP>
#SBATCH --array=<BEGIN-END>
date;hostname;pwd Below is the shell script part - the commands you will run to analyze your data. The following is an example.
module load ncbi_blast
blastn -db nt -query input.fa -outfmt 6 -out results.xml --num_threads 4 date |