From 97cf9dd434e7f80b400dcb09dd0091d906d6489c Mon Sep 17 00:00:00 2001
From: Natalie Breidenbach <natalie.breidenbach@tu-dresden.de>
Date: Mon, 27 Nov 2023 21:09:29 +0100
Subject: [PATCH] Update building_software.md

---
 .../docs/software/building_software.md             | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/software/building_software.md b/doc.zih.tu-dresden.de/docs/software/building_software.md
index 73952b06e..e61a8a52d 100644
--- a/doc.zih.tu-dresden.de/docs/software/building_software.md
+++ b/doc.zih.tu-dresden.de/docs/software/building_software.md
@@ -3,9 +3,9 @@
 While it is possible to do short compilations on the login nodes, it is generally considered good
 practice to use a job for that, especially when using many parallel make processes. Since 2016,
 the `/projects` filesystem is mounted read-only on all compute
-nodes in order to prevent users from doing large I/O there (which is what the `/scratch` is for).
+nodes in order to prevent users from doing large I/O there (which is what the `/data/horse` is for).
 In consequence, you cannot compile in `/projects` within a job. If you wish to install
-software for your project group anyway, you can use a build directory in the `/scratch` filesystem
+software for your project group anyway, you can use a build directory in the `/data/horse` filesystem
 instead.
 
 Every sane build system should allow you to keep your source code tree and your build directory
@@ -19,11 +19,11 @@ For instance, when using CMake and keeping your source in `/projects`, you could
 # save path to your source directory:
 marie@login$ export SRCDIR=/projects/p_number_crunch/mysource
 
-# create a build directory in /scratch:
-marie@login$ mkdir /scratch/p_number_crunch/mysoftware_build
+# create a build directory in /data/horse:
+marie@login$ mkdir /data/horse/p_number_crunch/mysoftware_build
 
-# change to build directory within /scratch:
-marie@login$ cd /scratch/p_number_crunch/mysoftware_build
+# change to build directory within /data/horse:
+marie@login$ cd /data/horse/p_number_crunch/mysoftware_build
 
 # create Makefiles:
 marie@login$ cmake -DCMAKE_INSTALL_PREFIX=/projects/p_number_crunch/mysoftware $SRCDIR
@@ -35,5 +35,5 @@ marie@login$ srun --mem-per-cpu=1500 --cpus-per-task=12 --pty make -j 12
 marie@login$ make install
 ```
 
-As a bonus, your compilation should also be faster in the parallel `/scratch` filesystem than it
+As a bonus, your compilation should also be faster in the parallel `/data/horse` filesystem than it
 would be in the comparatively slow NFS-based `/projects` filesystem.
-- 
GitLab