From 0a0a5bac33418890315ac91605f1b0fe2b02b092 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Roman=20Sl=C3=ADva?= <roman.sliva@vsb.cz>
Date: Sat, 22 Jul 2023 09:37:39 +0200
Subject: [PATCH] Update slurm-job-submission-and-execution.md

---
 docs.it4i/general/slurm-job-submission-and-execution.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/docs.it4i/general/slurm-job-submission-and-execution.md b/docs.it4i/general/slurm-job-submission-and-execution.md
index 38578600d..d5717a50a 100644
--- a/docs.it4i/general/slurm-job-submission-and-execution.md
+++ b/docs.it4i/general/slurm-job-submission-and-execution.md
@@ -69,7 +69,7 @@ Batch jobs is the standard way of running jobs and utilizing HPC clusters.
 
 ### Job Script
 
-Create example batch script called script.sh with the following content:
+Create example job script called script.sh with the following content:
 
 ```shell
 #!/usr/bin/bash
@@ -92,18 +92,20 @@ Script will:
 * use project PROJECT-ID for job access and accounting
 * use partition/queue qcpu
 * use four nodes
-* use 36 tasks per node
+* use 36 tasks per node - value used by MPI
 * set job time limit to 12 hours
 
 * load appropriate module
 * run command, srun serves as Slurm's native way of executing MPI-enabled applications, hostname is used in the example just for sake of simplicity
 
+Submit directory will be used as working directory for submitted job, so there is no need to change directory in the job script.
+Alternatively you can specify job working directory using sbatch `--chdir` (or shortly `-D`) option.
+
 ### Job Submit
 
 Submit batch job:
 
 ```console
-### submit directory my_work_dir will be also used as working directory for submitted job
 $ cd my_work_dir
 $ sbatch script.sh
 ```
-- 
GitLab