Using the queue system on skd-cyclone: Difference between revisions

From gfi
No edit summary
Line 11: Line 11:


<pre>
<pre>
# start with sbatch NAME_OF_THIS_FILE directly on machine
# SLURM wrapper script
# start this job with sbatch NAME_OF_THIS_FILE directly on the machine


#SBATCH --job-name=my_slurm_job
#SBATCH --job-name=my_slurm_job

Revision as of 09:58, 1 November 2016

General information

  1. Purpose
  2. Advantages
  3. Disadvantages
  4. Rules and procedures

Short tutorial

  1. create a basic wrapper script for your job
# SLURM wrapper script
# start this job with sbatch NAME_OF_THIS_FILE directly on the machine

#SBATCH --job-name=my_slurm_job
#SBATCH --workdir=/scratch/$USER
#SBATCH --partition=default
#SBATCH --output=results.%j.txt
#SBATCH --error=errors.%j.out
#SBATCH --mail-type=END
#SBATCH --time=12:00:00
#SBATCH --mem-per-cpu=100

<apply any required path settings>
<change to your working directory>
<command to start your job>

# done
  1. submit the script

sbatch ./my_queue_job.sh

  1. receive an email

Converting a script to a queue script

  1. add elements to the header

Description of each element

  1. parameters explained in short

Best practices, Q&A

Further information

  1. Contacts
  2. Links