Skip to content

Commit a8eab2f

Browse files
committed
squeue -u NetID -> squeue --me; typo fix
1 parent ef538c6 commit a8eab2f

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

docs/hpc/13_tutorial_intro_hpc/04_scheduler_fundamentals.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,9 @@ To submit this task to the scheduler, we use the `sbatch` command. This creates
6464
Submitted batch job 137860
6565
```
6666

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`.
6868
```bash
69-
[NetID@log-1 ~]$ squeue -u NetID
69+
[NetID@log-1 ~]$ squeue --me
7070
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
7171
137860 normal example- usernm R 0:02 1 c5-59
7272
```
@@ -93,7 +93,7 @@ hostname
9393
Submit the job and monitor its status:
9494
```bash
9595
[NetID@log-1 ~]$ sbatch example-job.sh
96-
[NetID@log-1 ~]$ squeue -u NetID
96+
[NetID@log-1 ~]$ squeue --me
9797
JOBID ACCOUNT NAME ST REASON START_TIME TIME TIME_LEFT NODES CPUS
9898
38191 yourAccount hello-wo PD Priority N/A 0:00 1:00:00 1 1
9999
```
@@ -156,7 +156,7 @@ hostname
156156
Submit the job and wait for it to finish. Once it is has finished, check the log file.
157157
```bash
158158
[NetID@log-1 ~]$ sbatch example-job.sh
159-
[NetID@log-1 ~]$ squeue -u NetID
159+
[NetID@log-1 ~]$ squeue --me
160160
cat slurm-38193.out
161161
This job is running on: c1-14
162162
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
169169
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!).
170170
```bash
171171
[NetID@log-1 ~]$ sbatch example-job.sh
172-
[NetID@log-1 ~]$ squeue -u NetID
172+
[NetID@log-1 ~]$ squeue --me
173173
Submitted batch job 38759
174174

175175
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
179179
```bash
180180
[NetID@log-1 ~]$ scancel 38759
181181
# 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
183183
JOBID USER ACCOUNT NAME ST REASON START_TIME TIME TIME_LEFT NODES CPUS
184184
```
185185

@@ -227,7 +227,7 @@ def main():
227227
help="Learning Rate")
228228
args = parser.parse_args()
229229
current_lr = args.lr
230-
print(f"Starting training with learing rate: {current_lr}")
230+
print(f"Starting training with learning rate: {current_lr}")
231231

232232
if __name__ == '__main__':
233233
main()

0 commit comments

Comments
 (0)