Differences

This shows you the differences between two versions of the page.

--- using-slurm [2019/02/01 12:30] – [Using SLURM] jean-baka
+++ using-slurm [2019/02/01 12:34] – jean-baka
@@ Line 8: / Line 8: @@
   * highmem
-"debug" is the default queue, which is useful for testing job parameters, program paths, etc. The run-time limit of the "debug" partition is 5 minutes, after which jobs are killed.
+"debug" is the default queue, which is useful for testing job parameters, program paths, etc. The run-time limit of the "debug" partition is 5 minutes, after which jobs are killed. The other partitions have no set time limit.
 To see more information about the queue configuration, use ''sinfo -lNe''.
@@ Line 24: / Line 24: @@
 </code>
-The above tells you, for instance, that compute04 has 8 CPUs while compute2 has 64 CPUs. And that a job sent to the "highmem" partition (a SLURM verb equivalent to "queue", as per the vocabulary in use with other schedulers e.g. Sun Grid Engine), then it will end up being run on either compute03 or mammoth.
+The above tells you, for instance, that compute04 has 8 CPUs while compute2 has 64 CPUs. And that a job sent to the "highmem" partition (a SLURM verb equivalent to "queue", as per the vocabulary in use with other schedulers, e.g. Sun Grid Engine), then it will end up being run on either compute03 or mammoth.
 ===== Submitting jobs =====
 ==== Interactive jobs ====
-How to get an interactive session, ie when you want to interact with a program (like R, etc):
+How to get an interactive session, i.e. when you want to interact with a program (like R, etc) for a limited amount of time, making the scheduler aware that you are requesting/using resources on the cluster:
 <code>[aorth@hpc: ~]$ interactive
 salloc: Granted job allocation 1080