Skip to content
Snippets Groups Projects
Commit 7d53aca3 authored by Jan Siwiec's avatar Jan Siwiec
Browse files

Update slurm-job-submission-and-execution.md

parent cec5bed7
Branches
Tags
No related merge requests found
Pipeline #36098 passed with warnings
# Job Submission and Execution
!!! warning
Don't use the `#SBATCH -- exclusive` parameter as it is already included in the SLURM configuration.<br><br>
Don't use the `#SBATCH --exclusive` parameter as it is already included in the SLURM configuration.<br><br>
Use the `#SBATCH --mem=` parameter **on `qfat` only**. On `cpu_` queues, whole nodes are allocated.
Accelerated nodes (`gpu_` queues) are divided each into eight parts with corresponding memory.
......@@ -81,7 +81,7 @@ Run interactive job, with X11 forwarding:
$ salloc -A PROJECT-ID -p qcpu_exp --x11
```
To finish the interactive job, you can either use the `exit` keyword, or Ctrl+D (`^D`) control sequence.
To finish the interactive job, use the Ctrl+D (`^D`) control sequence.
!!! warning
Do not use `srun` for initiating interactive jobs, subsequent `srun`, `mpirun` invocations would block forever.
......@@ -153,7 +153,7 @@ Example output of the job:
### Job Environment Variables
Slurm provides useful information to the job via environment variables.
Environment variables are available on all nodes allocated to job when accessed via Slurm supported means (srun, compatible mpirun).
Environment variables are available on all nodes allocated to job when accessed via Slurm supported means (`srun`, compatible `mpirun`).
See all Slurm variables
......@@ -321,7 +321,7 @@ Delete all my pending jobs for a project PROJECT-ID:
$ scancel --me -t pending -A PROJECT-ID
```
## Faq
## Troubleshooting
### Invalid Account
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment