From c46d22bdaef536ac7f2444f262f2914d74a973da Mon Sep 17 00:00:00 2001
From: Noah Trumpik <noah.trumpik@tu-dresden.de>
Date: Wed, 17 Jul 2024 08:22:24 +0200
Subject: [PATCH] lint fix
---
doc.zih.tu-dresden.de/docs/software/pika.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc.zih.tu-dresden.de/docs/software/pika.md b/doc.zih.tu-dresden.de/docs/software/pika.md
index 5dfe7047e..38007fbf1 100644
--- a/doc.zih.tu-dresden.de/docs/software/pika.md
+++ b/doc.zih.tu-dresden.de/docs/software/pika.md
@@ -94,9 +94,11 @@ If the current partition supports simultaneous multithreading (SMT) the maximum
threads per physical core is displayed in the SMT column. The Slurm configuration on ZIH systems
disables SMT by default. Therefore, in the example below, only a maximum CPU usage of 0.5 can be
achieved, as PIKA determines the average value over two hardware threads per physical core.
-If you want to use SMT, you must set the Slurm environment variable `SLURM_HINT=multithread`. In this case, `srun` distributes the tasks to all available hardware threads, thus a CPU usage of 1 can be reached. However, the SMT
-configuration only refers to the `srun` command. For single node jobs without `srun` command the
-tasks are automatically distributed to all available hardware threads.
+If you want to use SMT, you must set the Slurm environment variable `SLURM_HINT=multithread`.
+In this case, `srun` distributes the tasks to all available hardware threads, thus a CPU usage of 1
+can be reached. However, the SMT configuration only refers to the `srun` command. For single node
+jobs without `srun` command the tasks are automatically distributed to all available hardware
+threads.
{: align="center"}
--
GitLab