Getting started - Revision history

Erth9960(AT)su.se: /* Submitting your job */

2026-05-21T13:11:25Z

Submitting your job

← Older revision		Revision as of 13:11, 21 May 2026
Line 44:		Line 44:
	Once you have saved your script, you queue it for execution by running the following command:		Once you have saved your script, you queue it for execution by running the following command:

	<syntaxhighlight ~~lang="bash"~~>		<syntaxhighlight>
	sbatch hello-slurm.sh		sbatch hello-slurm.sh
	</syntaxhighlight>		</syntaxhighlight>

Erth9960(AT)su.se at 13:11, 21 May 2026

2026-05-21T13:11:07Z

← Older revision		Revision as of 13:11, 21 May 2026
Line 4:		Line 4:
	First you need to apply for access to the cluster if you haven't already, see [[Applying for access\|this page]] for details. Once you have been granted access, you will need to configure a VPN connection in order to be able to communicate with the server. Students can set up a VPN connection at https://vpn-student.dsv.su.se.		First you need to apply for access to the cluster if you haven't already, see [[Applying for access\|this page]] for details. Once you have been granted access, you will need to configure a VPN connection in order to be able to communicate with the server. Students can set up a VPN connection at https://vpn-student.dsv.su.se.

	When your VPN connection is up and running, you connect to the cluster using an SSH client and your SU credentials. The server address is <code>olympus.dsv.su.se</code>.~~<syntaxhighlight>~~		When your VPN connection is up and running, you connect to the cluster using an SSH client and your SU credentials. The server address is <code>olympus.dsv.su.se</code>.

			<syntaxhighlight>
	me@mylaptop:~$ ssh erth9960@olympus.dsv.su.se		me@mylaptop:~$ ssh erth9960@olympus.dsv.su.se
	erth9960@olympus's password:		erth9960@olympus's password:
Line 18:		Line 20:
	erth9960@slurm-login:~$		erth9960@slurm-login:~$

			</syntaxhighlight>
⚫	~~</syntaxhighlight>~~When you have successfully logged in, you can move on to running your first Slurm job.

		⚫	When you have successfully logged in, you can move on to running your first Slurm job.

	== Running code as a slurm job ==		== Running code as a slurm job ==
Line 38:		Line 42:

	=== Submitting your job ===		=== Submitting your job ===
	Once you have saved your script, you queue it for execution by running the following command:~~<syntaxhighlight lang="bash">~~		Once you have saved your script, you queue it for execution by running the following command:

			<syntaxhighlight lang="bash">
	sbatch hello-slurm.sh		sbatch hello-slurm.sh
	</~~syntaxhighlight>You should see output similar to this:<~~syntaxhighlight>		</syntaxhighlight>

			You should see output similar to this:

			<syntaxhighlight>
	Submitted batch job 1928		Submitted batch job 1928
			</syntaxhighlight>

	~~</syntaxhighlight>~~Since the script does very little work it will probably execute immediately, but if it doesn't you can see its place in the queue by running the command <code>squeue</code>. You can also see details about your job by running <code>scontrol show job NN</code>, where NN is the job ID that was printed (1928 in this example).		Since the script does very little work it will probably execute immediately, but if it doesn't you can see its place in the queue by running the command <code>squeue</code>. You can also see details about your job by running <code>scontrol show job NN</code>, where NN is the job ID that was printed (1928 in this example).

	=== Reading job output ===		=== Reading job output ===
	Since the job is run asynchronously, the output from your job will not be printed to your terminal as usual but written to a file. We don't specify a filename to use, so slurm will use the default name. The default name is <code>slurm-NN.out</code>, where NN is the job ID.		Since the job is run asynchronously, the output from your job will not be printed to your terminal as usual but written to a file. We don't specify a filename to use, so slurm will use the default name. The default name is <code>slurm-NN.out</code>, where NN is the job ID.

	You can read the resulting file with any tool that can read text files, such as <code>cat</code>:~~<syntaxhighlight lang="bash">~~		You can read the resulting file with any tool that can read text files, such as <code>cat</code>:

			<syntaxhighlight lang="bash">
	erth9960@slurm-login:~$ cat slurm-1928.out		erth9960@slurm-login:~$ cat slurm-1928.out
	Hello slurm-node-cpu-01		Hello slurm-node-cpu-01
			</syntaxhighlight>

	~~</syntaxhighlight>~~Here you can see that the code executed on <code>slurm-node-cpu-01</code>, as opposed to <code>slurm-login</code> which is where your terminal session is running.		Here you can see that the code executed on <code>slurm-node-cpu-01</code>, as opposed to <code>slurm-login</code> which is where your terminal session is running.

	== Further reading ==		== Further reading ==

Erth9960(AT)su.se at 14:48, 28 April 2026

2026-04-28T14:48:03Z

@@ Line 1: / Line 1: @@
 This document should help you get started with logging in to the cluster and running a "Hello world" script as a slurm job.
 Running code on slurm is always an asynchronous process. In other words you submit a job to the queue, Slurm schedules the job for execution when relevant resources are available, and any output from your job is recorded in a file.
@@ Line 33: / Line 53: @@
 </syntaxhighlight>Here you can see that the code executed on <code>slurm-node-cpu-01</code>, as opposed to <code>slurm-login</code> which is where your terminal session is running.

Erth9960(AT)su.se: Created page with "This document should help you get started with logging in to the cluster and running a "Hello world" script as a slurm job. Running code on slurm is always an asynchronous process. In other words you submit a job to the queue, Slurm schedules the job for execution when relevant resources are available, and any output from your job is recorded in a file. === Preparing your script === Write the following code into a file named `hello-slurm.sh`
2026-04-28T14:37:13Z

Created page with "This document should help you get started with logging in to the cluster and running a "Hello world" script as a slurm job. Running code on slurm is always an asynchronous process. In other words you submit a job to the queue, Slurm schedules the job for execution when relevant resources are available, and any output from your job is recorded in a file. === Preparing your script === Write the following code into a file named <code>hello-slurm.sh</code> <syntaxhighlig..."

New page
This document should help you get started with logging in to the cluster and running a "Hello world" script as a slurm job.

Running code on slurm is always an asynchronous process. In other words you submit a job to the queue, Slurm schedules the job for execution when relevant resources are available, and any output from your job is recorded in a file.

=== Preparing your script ===

Write the following code into a file named <code>hello-slurm.sh</code>

<syntaxhighlight lang="bash">#!/bin/bash
#SBATCH --job-name=testjob
#SBATCH --partition=cpu

echo "Hello $HOSTNAME"</syntaxhighlight>

The initial <code>#SBATCH</code> comments are special commands read by Slurm, passing instructions about how to execute your job. Here we only choose a name for the job and which partition to run it on. An incomplete list of useful sbatch arguments is available [[Useful sbatch arguments|here]].

<code>$HOSTNAME</code> is an environment variable that contains the name of the server the code is running on.

=== Submitting your job ===
Once you have saved your script, you queue it for execution by running the following command:<syntaxhighlight lang="bash">
sbatch hello-slurm.sh
</syntaxhighlight>You should see output similar to this:<syntaxhighlight>
Submitted batch job 1928

</syntaxhighlight>Since the script does very little work it will probably execute immediately, but if it doesn't you can see its place in the queue by running the command <code>squeue</code>. You can also see details about your job by running <code>scontrol show job NN</code>, where NN is the job ID that was printed (1928 in this example).

=== Reading job output ===
Since the job is run asynchronously, the output from your job will not be printed to your terminal as usual but written to a file. We don't specify a filename to use, so slurm will use the default name. The default name is <code>slurm-NN.out</code>, where NN is the job ID.

You can read the resulting file with any tool that can read text files, such as <code>cat</code>:<syntaxhighlight lang="bash">
erth9960@slurm-login:~$ cat slurm-1928.out
Hello slurm-node-cpu-01

</syntaxhighlight>Here you can see that the code executed on <code>slurm-node-cpu-01</code>, as opposed to <code>slurm-login</code> which is where your terminal session is running.