You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hpc/13_tutorial_intro_hpc/04_scheduler_fundamentals.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,9 +64,9 @@ To submit this task to the scheduler, we use the `sbatch` command. This creates
64
64
Submitted batch job 137860
65
65
```
66
66
67
-
And that’s all we need to do to submit a job. Our work is done – now the scheduler takes over and tries to run the job for us. While the job is waiting to run, it goes into a list of jobs called the `queue`. To check on our job’s status, we check the queue using the command `squeue -u NetID`.
67
+
And that’s all we need to do to submit a job. Our work is done – now the scheduler takes over and tries to run the job for us. While the job is waiting to run, it goes into a list of jobs called the `queue`. To check on our job’s status, we check the queue using the command `squeue --me`.
68
68
```bash
69
-
[NetID@log-1 ~]$ squeue -u NetID
69
+
[NetID@log-1 ~]$ squeue --me
70
70
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
71
71
137860 normal example- usernm R 0:02 1 c5-59
72
72
```
@@ -93,7 +93,7 @@ hostname
93
93
Submit the job and monitor its status:
94
94
```bash
95
95
[NetID@log-1 ~]$ sbatch example-job.sh
96
-
[NetID@log-1 ~]$ squeue -u NetID
96
+
[NetID@log-1 ~]$ squeue --me
97
97
JOBID ACCOUNT NAME ST REASON START_TIME TIME TIME_LEFT NODES CPUS
Submit the job and wait for it to finish. Once it is has finished, check the log file.
157
157
```bash
158
158
[NetID@log-1 ~]$ sbatch example-job.sh
159
-
[NetID@log-1 ~]$ squeue -u NetID
159
+
[NetID@log-1 ~]$ squeue --me
160
160
cat slurm-38193.out
161
161
This job is running on: c1-14
162
162
slurmstepd: error: *** JOB 38193 ON gra533 CANCELLED AT 2017-07-02T16:35:48
@@ -169,7 +169,7 @@ Our job was killed for exceeding the amount of resources it requested. Although
169
169
Sometimes we’ll make a mistake and need to cancel a job. This can be done with the `scancel` command. Let’s submit a job and then cancel it using its job number (remember to change the walltime so that it runs long enough for you to cancel it before it is killed!).
170
170
```bash
171
171
[NetID@log-1 ~]$ sbatch example-job.sh
172
-
[NetID@log-1 ~]$ squeue -u NetID
172
+
[NetID@log-1 ~]$ squeue --me
173
173
Submitted batch job 38759
174
174
175
175
JOBID ACCOUNT NAME ST REASON TIME TIME_LEFT NODES CPUS
@@ -179,7 +179,7 @@ Now cancel the job with its job number (printed in your terminal). A clean retur
179
179
```bash
180
180
[NetID@log-1 ~]$ scancel 38759
181
181
# It might take a minute for the job to disappear from the queue...
182
-
[NetID@log-1 ~]$ squeue -u NetID
182
+
[NetID@log-1 ~]$ squeue --me
183
183
JOBID USER ACCOUNT NAME ST REASON START_TIME TIME TIME_LEFT NODES CPUS
184
184
```
185
185
@@ -227,7 +227,7 @@ def main():
227
227
help="Learning Rate")
228
228
args = parser.parse_args()
229
229
current_lr = args.lr
230
-
print(f"Starting training with learing rate: {current_lr}")
230
+
print(f"Starting training with learning rate: {current_lr}")
0 commit comments