Differences between revisions 9 and 10
Revision 9 as of 2021-03-01 16:12:03
Size: 1505
Editor: jbjohnston
Comment:
Revision 10 as of 2021-03-01 16:12:51
Size: 1500
Editor: jbjohnston
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
#/bin/bash
Line 11: Line 10:
}}}
{{{
Line 12: Line 13:
Line 14: Line 14:
Line 16: Line 15:
Line 18: Line 16:
Line 20: Line 17:
Line 24: Line 20:
someApp

Job Scripts

Serial Single Threaded

This example illustrates a job script designed to run a simple single-threaded processes on a single compute node:

#SBATCH --job-name=mySerialjob
#SBATCH --nodes=1
#SBATCH --ntasks-per-node=1
#SBATCH --cpus-per-task=1
#SBATCH --time=0-00:20:00
#SBATCH --mem=3102

module load someApp
someApp

Explanation

A single process run only requires 1 node, as well as 1 cpu and a single task. These are reflected in the example script. We change to the same directory from where we submitted the job ( ${SLURM_SUBMIT_DIR} to produce our output. Then we load the module "someApp" and execute it.

Multi-Threaded Single Node

In this example we are running an application capable of utilizing multiple process threads on a single node (BLAST):

{{{#!/bin/bash

#SBATCH --job-name=myBLASTjob

#SBATCH --nodes=1

#SBATCH --ntasks-per-node=1

#SBATCH --cpus-per-task=8

#SBATCH --time=0-01:00:00

#SBATCH --mem=3102

cd ${SLURM_SUBMIT_DIR}

module load BLAST

blastn --num_threads 8 <...> }}}

Explanation

In this case we still have a single task (our blastn run) but we require 8 cpu cores to accommodate the 8 threads we've specified on the command line. The ellipses between the angle brackets represents the balance of our command line arguments.

command


CategoryHPC