Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This user's guide for the CMS supercomputer is intended to provide the minimum amount of information needed by a new user of this system. As such, it assumes that the user is familiar with basic notions on scientific computing, in particular the basic commands of the Unix operating system, and also with basic techniques for the execution of applications in a supercomputer.

The information in this guide includes basic technical documentation about the CMS supercomputer, the software environment, and also on available applications.

Please read it carefully and if any doubt arises don't hesitate to contact our support mail (see below in Getting help).


Connecting to

...

GridUI

View Cluster usage guidelines

...

  • set ofrequested resources:
    • number of computing resources: nodes(including all their CPUsand cores) or CPUs(including all their cores) or coresnumber of accelerators (GPUs)
    • amount ofmemory: either per node or per (logical) CPU
    • the (wall)time needed for the user’s tasks to complete their work
  • a set ofconstraints limiting jobs to nodes with specific features
  • a requested node partition(job queue)
  • a requested quality of service(QoS) level which grants users specific accesses
  • a requested account for accounting purposes

...

  • sbatch <job script>: submits a job script to the queue system (see below for job script directives).
  • squeue  [-u user ]: shows all the jobs submitted by all users or by the user if you specify the -u option.
  • scancel <job id>: removes his/her job from the queue system, canceling the execution of the job if it was already running.
  • srun: submit interactive job, run (parallel) job step
  • squeue: view queued jobs
  • sinfo: view partition and node info
  • scontrol: detailed control and info on jobs, queues, partitions
  • sstat: view system-level utilization (memory, I/O, energy)֒→for running jobs / job steps
  • sacct: view system-level utilization֒→for completed jobs / job steps (accounting DB)
  • sacctmgr: view and manage SLURM accounting data
  • sprio: view job priority factors
  • sshare: view accounting share info (usage, fair-share, etc.)

...

sbatch job.sh

sbatch -N 2 job.sh

sbatch -p batch --qos qos-batch job.sh

sbatch -p long --qos qos-long job.sh

sbatch --begin=2019-11-23T07:30:00 job.sh

sbatch -p batch --qos qos-besteffort job.shsbatch -p gpu --qos qos-gpu --gres=gpu:4 job.sh

sbatch -p bigmem --qos qos-bigmem --mem=2T job.sh

...

squeue / squeue -l / squeue -la / squeue -l -p batch / squeue -t PD

scontrol show nodes / scontrol show nodes $nodename

sinfo / sinfo -s / sinfo -N

sinfo -T

Software

Modules Enviroment

The Environment Modules package provides for the dynamic modification of a user's environment via modulefiles. Each modulefile contains the information needed to configure the shell for an application or a compilation. Modules can be loaded and unloaded dynamically and atomically, in a clean fashion. All popular shells are supported, including bash, ksh, zsh, sh, csh, tcsh, as well as some scripting languages such as perl.

The most important commands of module tool are: list, avail, load, unload, switch and purge

  • module list shows all the modules you have loaded

  • module avail shows all the modules that user is able to load

  • module load let user load the necessary environment variables for the selected modulefile (PATH, MANPATH, LD_LIBRARY_PATH...etc)

  • module unload removes all environment changes made by module load command

  • module switch acts as module unload and module load command at same time

Job submitting with Modules

...

User questions and support are handled at:

...

If you need assistance, please supply us with the nature of the problem, the date and time that the problem occurred, and the location of any other relevant information, such as output or log files.

...