Quickstart/Slurm - Revision history

Pysdlb: /* squeue -u username */

2022-11-17T11:54:46Z

‎squeue -u username

2022-11-17T11:54:16Z

‎squeue -u username

2022-11-17T11:54:00Z

‎Introduction to Slurm Commands

2022-11-17T11:48:34Z

‎squeueme

2022-11-16T09:34:06Z

‎interactive

2022-11-15T15:13:22Z

‎scancel

2022-11-09T15:25:11Z

‎interactive

2022-11-09T15:24:52Z

2022-11-09T15:17:09Z

‎interactive

2022-11-09T15:16:20Z

added scancel

@@ Line 78: / Line 78: @@
 ==== squeue -u username====
-Using the flag -u and your username will provide only your running jobs.
+Using the flag -u and your username will provide only your jobs.
 <pre style="background-color: #000000; color: white; border: 2px solid black; font-family: monospace, sans-serif;">
 [749094@login01 ~]$ squeue -u 749094

@@ Line 85: / Line 85: @@
    compute mpi_benc   749094 R      31:02      2 c[005,007]
 </pre>
 <!-- === squeueme ===
 The '''squeueme''' command provides similar information as squeue however it shows only jobs you are running making it easier to identify what you have running, and provides more specific information relating to your jobs:

@@ Line 40: / Line 40: @@
 [username@login01 ~]$ squeue
               JOBID  PARTITION     NAME   USER   ST      TIME  NODES NODELIST(REASON)
-   compute  clasDFT   465449 R      16:36      1 c006
+   compute  clasDFT   749094 R      16:36      1 c006
-   compute mpi_benc   465449 R      31:02      2 c[005,007]
+   compute mpi_benc   749094 R      31:02      2 c[005,007]
    compute  orca_1n   465449 R    1:00:32      1 c004
    compute  orca_1n   465449 R    1:04:17      1 c003
@@ Line 76: / Line 76: @@
 | List of nodes a job is running on also provides a reason a job is not running e.g. a dependency on a node.
 |}
 <!-- === squeueme ===

@@ Line 77: / Line 77: @@
 |}
-=== squeueme ===
+<!-- === squeueme ===
 The '''squeueme''' command provides similar information as squeue however it shows only jobs you are running making it easier to identify what you have running, and provides more specific information relating to your jobs:
@@ Line 112: / Line 112: @@
 | List of nodes a job is running on also provides a reason a job is not running e.g. a dependency on a node.
 |}
 ===scancel===
 scancel is used to cancel your jobs. Only jobs running under your userid may be cancelled. No output is given by this command, but you can check squeueme to see if it has gone.

← Older revision		Revision as of 09:34, 16 November 2022
Line 125:		Line 125:


−	[[~~Newmainpage~~ #Quickstart\| Back]] / [[Quickstart/Batch Jobs\| Next (Batch Jobs)]]	+	[[Main Page #Quickstart\| Back]] / [[Quickstart/Batch Jobs\| Next (Batch Jobs)]]

← Older revision		Revision as of 15:25, 9 November 2022
Line 120:		Line 120:

	=== interactive ===		=== interactive ===
−	The [[Quickstart/Interactive\| ~~'''~~interactive~~'''~~]] command, available on the Viper login node will start an interactive session on a compute node allowing you to start work.	+	The [[Quickstart/Interactive\| interactive]] command, available on the Viper login node will start an interactive session on a compute node allowing you to start work.

← Older revision		Revision as of 15:24, 9 November 2022
Line 121:		Line 121:
	=== interactive ===		=== interactive ===
	The [[Quickstart/Interactive\| '''interactive''']] command, available on the Viper login node will start an interactive session on a compute node allowing you to start work.		The [[Quickstart/Interactive\| '''interactive''']] command, available on the Viper login node will start an interactive session on a compute node allowing you to start work.
		+
		+
		+
		+
		+	[[Newmainpage #Quickstart\| Back]] / [[Quickstart/Batch Jobs\| Next (Batch Jobs)]]

← Older revision		Revision as of 15:17, 9 November 2022
Line 120:		Line 120:

	=== interactive ===		=== interactive ===
−	The '''interactive''' command, available on the Viper login node will start an interactive session on a compute node allowing you to start work. ~~More information on this command can be found at [[Quickstart/Interactive]]~~	+	The [[Quickstart/Interactive\| '''interactive''']] command, available on the Viper login node will start an interactive session on a compute node allowing you to start work.