From 2630bbef170ca67d0fced54b53c17ad53001d6ac Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Wed, 31 Aug 2022 13:09:59 +0200
Subject: [PATCH] Fix heading of example
---
doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
index 56f209a46..242996d96 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
@@ -213,13 +213,13 @@ There are three typical options for the use of workspaces:
### Per-Job Storage
A batch job needs a directory for temporary data. This can be deleted afterwards.
-To help you to write your own SBatch file, suited to your own needs, we came up with
+To help you to write your own (Slurm) job file, suited to your own needs, we came up with
the following example (which works [for the program g16](../software/nanoscale_simulations.md)).
You will probably want to adjust it in a few places (e.g. what software you want to
[load](../software/modules.md), inserting the path to your input file and actually
calling the actual software to do your computation).
-!!! example "Using temporary Workspaces for I/O intensive tasks"
+!!! example "Using temporary workspaces for I/O intensive tasks"
#!/bin/bash
#SBATCH --partition=haswell
@@ -256,7 +256,7 @@ calling the actual software to do your computation).
bzip2 --compress --stdout -4 "${WORKSPACE_DIR}" > $HOME/gaussian_job-$SLURM_JOB_ID.bz2
RETURN_CODE=$?
COMPRESSION_SUCCESS="$(if test $RETURN_CODE -eq 0; then echo 'TRUE'; else echo 'FALSE'; fi)"
-
+
if [ "TRUE" = $COMPRESSION_SUCCESS ]; then
test -d $WORKSPACE_DIR && rm -rf $WORKSPACE_DIR/*
# Reduces grace period to 1 day!
--
GitLab