From a7fa762ba7e474d257bf751f375d25555a9c05bc Mon Sep 17 00:00:00 2001 From: Sam Moors Date: Fri, 8 Dec 2023 10:08:37 +0100 Subject: [PATCH] Update source/jobs/job_advanced.rst Co-authored-by: Alex Domingo --- source/jobs/job_advanced.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/source/jobs/job_advanced.rst b/source/jobs/job_advanced.rst index 3c10d0bb2..26af47b99 100644 --- a/source/jobs/job_advanced.rst +++ b/source/jobs/job_advanced.rst @@ -178,11 +178,12 @@ is running on the node where you ran ``salloc`` (likely a login node). Contrary ``srun``, the shell is **not** running on the allocated resources. You can however run commands on the allocated resources via ``srun``. -**Note that in particular on clusters with multiple CPU architectures, you need to -understand Linux environments and the way they interact with Slurm very well as you -are now executing commands in two potentially incompatible sections of the cluster that -require different settings in the environment. So if you execute a command in the wrong -environment it may run inefficiently, or it may simply fail.** +**.. note:: + Note that in particular on clusters with multiple CPU architectures, you need to + understand Linux environments and the way they interact with Slurm very well as you + are now executing commands in two potentially incompatible sections of the cluster that + require different settings in the environment. So if you execute a command in the wrong + environment it may run inefficiently, or it may simply fail.** There is no problem with Vaughan though as on that cluster all CPUs are of the same generation.