From 36aaf21146b77703e949cbeacb41f3f128602a6e Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Tue, 27 Sep 2022 15:29:27 +0200
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)
---
doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
index bc1ae160a..0872627f9 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
@@ -98,7 +98,7 @@ at runtime) which you can find via `squeue --me`. The id allows you to
'submit command mpirun -n $ranks ./app' and replace it with 'srun ./app'
??? warning "Issues with mpirun"
- Using `mpirun` on partitions alpha and ml leads to wrong resource distribution when more than
+ Using `mpirun` on partitions `alpha` and `ml` leads to wrong resource distribution when more than
one node is involved. This yields a strange distribution like e.g. `SLURM_NTASKS_PER_NODE=15,1`
even though `--tasks-per-node=8` was specified. Unless you really know what you're doing (e.g.
use rank pinning via perl script), avoid using mpirun.
--
GitLab