Annotated Slurm Script - Revision history

Weiler at 01:55, 9 March 2023

2023-03-09T01:55:03Z

← Older revision		Revision as of 18:55, 8 March 2023
Line 1:		Line 1:
	[[Category:Scheduler]]		[[Category:Scheduler]]
	This is a walk-through for a basic SLURM scheduler job script for a common case of a multi-threaded ~~analysys~~. 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 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.

	{\|cellspacing=30		{\|cellspacing=30

Weiler at 01:54, 9 March 2023

2023-03-09T01:54:18Z

← Older revision		Revision as of 18:54, 8 March 2023
Line 17:		Line 17:
	:Your email address to use for all batch system communications		:Your email address to use for all batch system communications
	<pre>		<pre>
	##SBATCH --mail-user=<EMAIL>		#SBATCH --mail-user=<EMAIL>
	##SBATCH --mail-user=<EMAIL-ONE>,<EMAIL-TWO>		#SBATCH --mail-user=<EMAIL-ONE>,<EMAIL-TWO>
	</pre>		</pre>
	;GPUs		;GPUs

Weiler at 01:53, 9 March 2023

2023-03-09T01:53:56Z

← Older revision		Revision as of 18:53, 8 March 2023
Line 19:		Line 19:
	##SBATCH --mail-user=<EMAIL>		##SBATCH --mail-user=<EMAIL>
	##SBATCH --mail-user=<EMAIL-ONE>,<EMAIL-TWO>		##SBATCH --mail-user=<EMAIL-ONE>,<EMAIL-TWO>
			</pre>
			;GPUs
			:How many GPUs your job will require
			<pre>
			#SBATCH --gres=gpu:1
	</pre>		</pre>
	;What emails to send		;What emails to send

Weiler: Created page with "Category:Scheduler This is a walk-through for a basic SLURM scheduler job script for a common case of a multi-threaded analysys. If the program you run is single-threaded..."

2023-03-09T01:48:13Z

Created page with "Category:Scheduler This is a walk-through for a basic SLURM scheduler job script for a common case of a multi-threaded analysys. If the program you run is single-threaded..."

New page

[[Category:Scheduler]]
This is a walk-through for a basic SLURM scheduler job script for a common case of a multi-threaded analysys. 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.

{|cellspacing=30
|-style="vertical-align:top;"
|style="width: 50%"|
;Set the shell to use
<pre>
#!/bin/bash
</pre>
;Common arguments
* Name the job to make it easier to see in the job queue
<pre>
#SBATCH --job-name=<JOBNAME>
</pre>
;Email
: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
:NONE - no emails
:ALL - all emails
:END,FAIL - only email if the job fails and email the summary at the end of the job
<pre>
#SBATCH --mail-type=FAIL,END
</pre>
;Standard Output and Error log files
:Use file patterns
:: %j - job id
:: %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>
</pre>
;Number of nodes to use. For all non-MPI jobs this number will be equal to '1'
<pre>
#SBATCH --nodes=1
</pre>
;Number of tasks. For all non-MPI jobs this number will be equal to '1'
<pre>
#SBATCH --ntasks=1
</pre>
;Number of CPU cores to use. This number must match the argument used for the program you run.
<pre>
#SBATCH --cpus-per-task=4
</pre>
||
;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
:[DAYS] are optional, use when it is convenient
<pre>
#SBATCH --time=72:00:00
</pre>
;Optional:
:A group to use if you belong to multiple groups. Otherwise, do not use.
<pre>
#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, similar to [[Torque_Job_Arrays]] on HiPerGator 1
<pre>
#SBATCH --array=<BEGIN-END>
</pre>
;Example of five tasks
:<nowiki>#</nowiki>SBATCH --array=1-5
----
;Recommended convenient shell code to put into your job script
* Add host, time, and directory name for later troubleshooting
<pre>
date;hostname;pwd
</pre>
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
<pre>
module load ncbi_blast
</pre>
* Run the program
<pre>
blastn -db nt -query input.fa -outfmt 6 -out results.xml --num_threads 4

date
</pre>
|}