... | @@ -64,3 +64,21 @@ nohup Rscript myscript.R arg1 arg2 >& myscript_log.txt & |
... | @@ -64,3 +64,21 @@ nohup Rscript myscript.R arg1 arg2 >& myscript_log.txt & |
|
```
|
|
```
|
|
|
|
|
|
It should then be safe to log out and return later to check the status of the job. `tail -f myscript_log.txt` can be used to monitor the log file in real time.
|
|
It should then be safe to log out and return later to check the status of the job. `tail -f myscript_log.txt` can be used to monitor the log file in real time.
|
|
|
|
|
|
|
|
|
|
|
|
**SLURM tips**
|
|
|
|
---
|
|
|
|
|
|
|
|
To gather information of your runs in SLURM you can run the following command to store job statistics in a output file:
|
|
|
|
|
|
|
|
```
|
|
|
|
sacct --starttime <for-the-last-x-hours> -u <username> --format=User,JobID,Jobname,partition,state,time,start,end,elapsed,MaxRss,MaxVMSize,nnodes,ncpus,nodelist >> path_to_log_output/job_stats.out
|
|
|
|
```
|
|
|
|
|
|
|
|
The `starttime` should be in the following format: `2020-07-01T13:00:00`.
|
|
|
|
|
|
|
|
It is also possible to gather job statistics for specific job id's:
|
|
|
|
|
|
|
|
```
|
|
|
|
sacct -j <JOB_ID> --format=User,JobID,Jobname,partition,state,time,start,end,elapsed,MaxRss,MaxVMSize,nnodes,ncpus,nodelist >> path_to_log_output/job_stats.out
|
|
|
|
``` |
|
|
|
\ No newline at end of file |