User Jobs - Revision history

GiulioFontana: /* Non-interactive jobs */

2026-03-06T14:19:03Z

Non-interactive jobs

← Older revision		Revision as of 14:19, 6 March 2026
Line 203:		Line 203:

	'''<nowiki>#</nowiki>SBATCH --job-name=<name>'''		'''<nowiki>#</nowiki>SBATCH --job-name=<name>'''


	~~: <nowiki>#</nowiki> The following directives of the preamble are optional and activate SLURM's email notifications:~~

	~~: <nowiki>#</nowiki> the first specifies where they are sent; the following 3 set up notifications start/end/failure of job execution~~

	~~'''<nowiki>#</nowiki>SBATCH --mail-user <email_address>'''~~

	~~'''<nowiki>#</nowiki>SBATCH --mail-type BEGIN'''~~

	~~'''<nowiki>#</nowiki>SBATCH --mail-type END'''~~

	~~'''<nowiki>#</nowiki>SBATCH --mail-type FAIL'''~~

	<nowiki>#</nowiki>----------------end of preamble----------------		<nowiki>#</nowiki>----------------end of preamble----------------

GiulioFontana at 10:43, 3 February 2026

2026-02-03T10:43:43Z

← Older revision		Revision as of 10:43, 3 February 2026
Line 1:		Line 1:
	= ~~<span style="background:#ffff00">~~Running jobs with SLURM~~</span>~~ =		= Running jobs with SLURM =

	Users of Mufasa '''must''' use SLURM to run resource-heavy processes, i.e. computing jobs that require one or more of the following:		Users of Mufasa '''must''' use SLURM to run resource-heavy processes, i.e. computing jobs that require one or more of the following:
Line 227:		Line 227:
	</blockquote>		</blockquote>

	= ~~<span style="background:#ffff00">~~Executing jobs on Mufasa~~</span>~~ =		= Executing jobs on Mufasa =

	== Key concept ==		== Key concept ==

GiulioFontana: /* Running jobs with SLURM */

2025-11-24T21:48:48Z

Running jobs with SLURM

← Older revision		Revision as of 21:48, 24 November 2025
Line 1:		Line 1:
	= Running jobs with SLURM =		= <span style="background:#ffff00">Running jobs with SLURM</span> =

	Users of Mufasa '''must''' use SLURM to run resource-heavy processes, i.e. computing jobs that require one or more of the following:		Users of Mufasa '''must''' use SLURM to run resource-heavy processes, i.e. computing jobs that require one or more of the following:

GiulioFontana: /* Options of srun and sbatch */

2025-11-24T21:48:25Z

Options of srun and sbatch

← Older revision		Revision as of 21:48, 24 November 2025
Line 43:		Line 43:
	and then executes the program.		and then executes the program.

	=== ~~<span style="background:#ffff00">~~Options of <code>srun</code> and <code>sbatch</code~~></span~~> ===		=== Options of <code>srun</code> and <code>sbatch</code> ===

	The <code>[options]</code> part of <code>srun</code> and <code>sbatch</code> commands is used to tell SLURM what resources the job needs to be executed the job and how much time it will need to complete its execution.		The <code>[options]</code> part of <code>srun</code> and <code>sbatch</code> commands is used to tell SLURM what resources the job needs to be executed the job and how much time it will need to complete its execution.

GiulioFontana: /* Running jobs with SLURM */

2025-11-24T21:47:24Z

Running jobs with SLURM

← Older revision		Revision as of 21:47, 24 November 2025
Line 7:		Line 7:
	* a significant amount of RAM.		* a significant amount of RAM.

	In fact, only processes run via SLURM have access to all the resources of Mufasa. Processes run outside SLURM are executed by the [[System#Login server\|login server]] virtual machine, which has minimal resources and no GPUs. Using SLURM is therefore the only way to execute resource-heavy jobs on Mufasa ~~(this~~ is a key difference between Mufasa 1.0 and Mufasa 2.0).		In fact, only processes run via SLURM have access to all the resources of Mufasa. Processes run outside SLURM are executed by the [[System#Login server\|login server]] virtual machine, which has minimal resources and no GPUs. Using SLURM is therefore the only way to execute resource-heavy jobs on Mufasa. This is a key difference between Mufasa 1.0 and [[System#Mufasa 2.0\|Mufasa 2.0]].

	== <code>srun</code> and <code>sbatch</code> ==		== <code>srun</code> and <code>sbatch</code> ==

GiulioFontana: /* Running jobs with SLURM */

2025-11-24T21:46:48Z

Running jobs with SLURM

← Older revision		Revision as of 21:46, 24 November 2025
Line 7:		Line 7:
	* a significant amount of RAM.		* a significant amount of RAM.

	In fact, only processes run via SLURM have access to all the resources of Mufasa. Processes run outside SLURM are executed by the [[System#~~Bastion~~ server\|~~bastion~~ server]] virtual machine, which has minimal resources and no GPUs. Using SLURM is therefore the only way to execute resource-heavy jobs on Mufasa (this is a key difference between Mufasa 1.0 and Mufasa 2.0).		In fact, only processes run via SLURM have access to all the resources of Mufasa. Processes run outside SLURM are executed by the [[System#Login server\|login server]] virtual machine, which has minimal resources and no GPUs. Using SLURM is therefore the only way to execute resource-heavy jobs on Mufasa (this is a key difference between Mufasa 1.0 and Mufasa 2.0).

	== <code>srun</code> and <code>sbatch</code> ==		== <code>srun</code> and <code>sbatch</code> ==

GiulioFontana: /* Running jobs with SLURM */

2025-11-24T21:46:24Z

Running jobs with SLURM

← Older revision		Revision as of 21:46, 24 November 2025
Line 1:		Line 1:
	= Running jobs with SLURM =		= Running jobs with SLURM =

	Users of Mufasa '''must''' use SLURM to run resource-heavy processes, i.e. computing jobs that require ~~any~~ of the following:		Users of Mufasa '''must''' use SLURM to run resource-heavy processes, i.e. computing jobs that require one or more of the following:
	* GPUs		* GPUs
	* multiple CPUs		* multiple CPUs
			* powerful CPUs
	* a significant amount of RAM.		* a significant amount of RAM.

GiulioFontana: /* Non-interactive jobs */

2025-11-24T20:32:51Z

Non-interactive jobs

← Older revision		Revision as of 20:32, 24 November 2025
Line 165:		Line 165:
	The template includes all the options [[#Using SLURM to run a container\|already described above]], plus a few additional useful ones (for instance, those that enable SLURM to send email messages to the user in correspondence to events in the lifecycle of their job). Information about all the possible options can be found in [SLURM's own documentation].		The template includes all the options [[#Using SLURM to run a container\|already described above]], plus a few additional useful ones (for instance, those that enable SLURM to send email messages to the user in correspondence to events in the lifecycle of their job). Information about all the possible options can be found in [SLURM's own documentation].

	In the template below, '''#SBATCH directives''' are requests made to SLURM. #SBATCH directives have a leading "#" ~~but~~ that does ''not'' mean that they are comments~~, just~~ as the <code>#!/bin/bash</code> at the beginning of a shell script is not a comment as well.		In the template below, '''#SBATCH directives''' are requests made to SLURM. Notice that, though #SBATCH directives have a leading "#", that does ''not'' mean that they are comments: exactly as the <code>#!/bin/bash</code> at the beginning of a shell script, while starting with "#", is not a comment as well.

	Other lines in the script that begin with <code>#</code> not followed by SBATCH are comments.		Other lines in the script that begin with <code>#</code> not followed by SBATCH are comments.

GiulioFontana: /* Non-interactive jobs */

2025-11-24T20:31:14Z

Non-interactive jobs

← Older revision		Revision as of 20:31, 24 November 2025
Line 165:		Line 165:
	The template includes all the options [[#Using SLURM to run a container\|already described above]], plus a few additional useful ones (for instance, those that enable SLURM to send email messages to the user in correspondence to events in the lifecycle of their job). Information about all the possible options can be found in [SLURM's own documentation].		The template includes all the options [[#Using SLURM to run a container\|already described above]], plus a few additional useful ones (for instance, those that enable SLURM to send email messages to the user in correspondence to events in the lifecycle of their job). Information about all the possible options can be found in [SLURM's own documentation].

	In the template below, #SBATCH directives are requests made to SLURM. #SBATCH directives have a leading "#" but that does ''not'' mean that they are comments, just as the <code>#!/bin/bash</code> at the beginning of a shell script is not a comment as well.		In the template below, '''#SBATCH directives''' are requests made to SLURM. #SBATCH directives have a leading "#" but that does ''not'' mean that they are comments, just as the <code>#!/bin/bash</code> at the beginning of a shell script is not a comment as well.

	Other lines in the script that begin with <code>#</code> not followed by SBATCH are comments.		Other lines in the script that begin with <code>#</code> not followed by SBATCH are comments.

GiulioFontana: /* Non-interactive jobs */

2025-11-24T20:30:39Z

Non-interactive jobs

← Older revision		Revision as of 20:30, 24 November 2025
Line 151:		Line 151:
	''Usually, a Linux shell script is given a name ending in ''.sh,'' such as ''my_execution_script.sh'', but this is not mandatory.''		''Usually, a Linux shell script is given a name ending in ''.sh,'' such as ''my_execution_script.sh'', but this is not mandatory.''

	''Within any shell script, lines preceded by <code>#</code> are comments (with the notable exception of the initial <code>#!/bin/bash</code> line)''.		''Within any shell script, lines preceded by <code>#</code> are comments (with the notable exception of the initial'' <code>#!/bin/bash</code> ''line)''.

	''Use of blank lines as spacers is allowed.''		''Use of blank lines as spacers is allowed.''