From 710c6f3894ee77a5d131beb3bb26d285ebcc1fa0 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Wed, 6 Mar 2024 09:41:15 +0100
Subject: [PATCH] Refer to `Power9` as cluster
---
doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md | 2 +-
.../docs/jobs_and_resources/slurm_examples.md | 2 +-
doc.zih.tu-dresden.de/docs/software/containers.md | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
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 f5c722791..4be982b9e 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 @@ can find it via `squeue --me`. The job ID allows you to
!!! warning "srun vs. mpirun"
On ZIH systems, `srun` is used to run your parallel application. The use of `mpirun` is provenly
- broken on partitions `power9` and `alpha` for jobs requiring more than one node. Especially when
+ broken on clusters `Power9` and `Alpha` for jobs requiring more than one node. Especially when
using code from github projects, double-check its configuration by looking for a line like
'submit command mpirun -n $ranks ./app' and replace it with 'srun ./app'.
diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md
index e1feca90f..b6e9e2408 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md
@@ -175,7 +175,7 @@ srun: error: Unable to allocate resources: Job violates accounting/QOS policy (j
### Running Multiple GPU Applications Simultaneously in a Batch Job
Our starting point is a (serial) program that needs a single GPU and four CPU cores to perform its
-task (e.g. TensorFlow). The following batch script shows how to run such a job on the partition `power9`.
+task (e.g. TensorFlow). The following batch script shows how to run such a job on the cluster `Power9`.
!!! example
diff --git a/doc.zih.tu-dresden.de/docs/software/containers.md b/doc.zih.tu-dresden.de/docs/software/containers.md
index 5046de4b8..f15caa5c8 100644
--- a/doc.zih.tu-dresden.de/docs/software/containers.md
+++ b/doc.zih.tu-dresden.de/docs/software/containers.md
@@ -10,9 +10,9 @@ used in an HPC environment and more efficient in many cases. Docker images can e
Singularity. Information about the use of Singularity on ZIH systems can be found on this page.
In some cases using Singularity requires a Linux machine with root privileges
-(e.g. using the partition `power9`), the same architecture and a compatible kernel.
+(e.g. using the cluster `Power9`), the same architecture and a compatible kernel.
For many reasons, users on ZIH systems cannot be granted root permissions.
-A solution is a Virtual Machine (VM) on the partition `power9` which allows users to gain
+A solution is a Virtual Machine (VM) on the cluster `Power9` which allows users to gain
root permissions in an isolated environment.
There are two main options on how to work with Virtual Machines on ZIH systems:
--
GitLab