From f786dc3a38e82305f3b967a21862badd94112e46 Mon Sep 17 00:00:00 2001
From: "ivan.kondov" <ivan.kondov@kit.edu>
Date: Thu, 5 Dec 2019 15:38:26 +0100
Subject: [PATCH] added text about batch system and workspace for launchdirs
---
docs/advanced.rst | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/docs/advanced.rst b/docs/advanced.rst
index 6108876..74acd91 100644
--- a/docs/advanced.rst
+++ b/docs/advanced.rst
@@ -38,14 +38,21 @@ for the queing systems MOAB and SLURM see the examples provided in the folder
In practical use cases, it is generally of advantage to separate the configuration
files, the workflow templates (i.e. the input) and the launches. This structure
-is used in the demo 6 in folder **demos/6_advanced**.
+is used in folder **demos/6_advanced**.
To submit a single fireworker batch job on bwUniCluster the ``qlaunch`` command
-is called like this::
+is called like this in the **launches** folder::
cd launches
qlaunch -q ../config/qadapter_uc1_vasp.yaml -w ../config/fworker_uc1_vasp.yaml singleshot
+The submitted batch jobs can be managed with the commands of your batch system.
+For example, for SLURM these are the ``squeue`` and the ``scontrol`` commands.
+The sample adapters are configured in such a way that all launch directories will
+be created there where the ``qlaunch`` command was executed. For large outputs
+and large temporary data the best place of **launches** and **config** folders
+is within a workspace of a high-throughput cluster file system.
+
Deal with failures and crashes
--
GitLab