Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
public:usage:fuchs [2020/02/06 12:40] – [Your First Job Script] geier | public:usage:fuchs [2020/05/15 10:51] – [Job Monitoring] geier |
---|
on the command line. The job's output streams (''stdout'' and ''stderr'') will be joined and saved to ''slurm-ID.out'', where ''ID'' is a SLURM job ID, which is assigned automatically. You can change this behavior by adding an ''%%--%%output'' and/or ''%%--%%error'' argument to the SLURM options. | on the command line. The job's output streams (''stdout'' and ''stderr'') will be joined and saved to ''slurm-ID.out'', where ''ID'' is a SLURM job ID, which is assigned automatically. You can change this behavior by adding an ''%%--%%output'' and/or ''%%--%%error'' argument to the SLURM options. |
| |
For job monitoring (to check the current state of your jobs) you can use the ''squeue'' command. Depending on the current cluster utilization (and other factors), your job(s) may take a while to start. | ==== Job Monitoring ==== |
| |
| For job monitoring (to check the current state of your jobs) you can use the ''squeue'' command. Depending on the current cluster utilization (and other factors), your job(s) may take a while to start. You can list the current queuing times by running ''sqtimes'' on the command line. |
| |
If you need to cancel a job, you can use the ''scancel'' command (please see the ''manpage'', ''man scancel'', for further details). | If you need to cancel a job, you can use the ''scancel'' command (please see the ''manpage'', ''man scancel'', for further details). |