This page generates job scripts for the SLURM resource manager.
Enter the details of your job in the form below and then click on the make script button below.
It is a good idea to give your job a meaningful name. This will help you identify it when listing the job queue.
Suitable for distributed parallel jobs (such as those which use MPI), and single CPU core jobs.
Suitable for shared-memory multithreaded jobs. Note these jobs will be allocated an entire node on the system, but cannot use more than one node.
Enter the maximum number of CPU cores needed by your job.
For standard jobs this specifies the amount of memory allocated to each CPU core requested by the job. The total memory used is equal to the number of cores in the job multiplied by the amount of memory requested. If you leave this blank then your job will be allocated 1 gigabyte per CPU core.
For example if you request 2 CPU cores and 4GB of memory per core, the total memory used by the job is 8GB.
For SMP jobs this is the total memory allocated for the job, irrespective of the number of CPU cores.
Send yourself an email when the job:
|ends with an error|
Use this email address:
You can be notified by email when your job starts running or when it ends (either successfully or with an error).
You can specify an address to receive the email. If you leave it blank the email will be sent to the address registered with your user account.
Enter the maximum amount of time needed by your whole job.
Run the job from:
|The same directory where it is launched.|
|Your home directory.|
|The directory with this name:
Each job is run from a given directory on the computer's filesystem - this is called the working directory in Unix terminology.
You need to set the working directory correctly so that your job can find its input files and generate its output files in the appropriate location.
In most cases it is desirable to set this to the directory where the job was launched, but you might also like it to be your home directory, or from some other specific directory on the computer.
If you specify the directory, it must be an absolute reference (i.e. /home/foo/mydir) or relative to the launch directory.
Enter the modules that you would like to load:
The modules utility sets up your Unix environment for particular versions of specified programs. It is possible to use more than one module in your job (just list all the ones you need on separate lines).
For example to use version 3.2 of the application foo, which was compiled with gcc, you should load the module called: