Content

Code execution

To execute your code you need to

1. build a binary (executable, model code), see Workflow CPU CLX,
2. create a slurm job script like in Workflow CPU CLX with a slurm partition in table Partition for CPU CLX,
3. submit the slurm job script.

> sbatch myjobscipt.slurm
Submitted batch job 8028673
> ls slurm-8028673.out
slurm-8028673.out

Partition for CPU CLX

The compute nodes of the CPU cluster of system Lise are organised via the following Slurm partitions.

See Slurm usage how to pass the 12h wall time limit with job dependencies.

Which partition to choose?

The default partition cpu-clx is suitable for most calculations. The :test partitions are, as the name suggests, intended for shorter and smaller test runs. These have a higher priority and a few dedicated nodes, but provide only limited resources. Shared nodes are suitable for pre- and post-processing. A job running on a shared node is only accounted for its core fraction (cores of job / all cores per node). All non-shared nodes are exclusive to one job only at a time.

The available home/local-ssd/work/perm file systems are discussed under File Systems.

For an overview of all Slurm partitions and status of nodes: sinfo -r
For detailed information about a particular nodes: scontrol show node <nodename>

Charge rates for accounting

Charge rates for the Slurm partitions can be found under Accounting.

Fat-Tree Communication Network of Lise

See OPA Fat Tree network of Lise

List of CPUs