From dfc230c481bcc87b42f93aab37e9c85fd85fd822 Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Mon, 7 Oct 2024 09:54:42 +0200
Subject: [PATCH] Update octave.md

---
 docs.it4i/software/numerical-languages/octave.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs.it4i/software/numerical-languages/octave.md b/docs.it4i/software/numerical-languages/octave.md
index 8564bd030..c82402afa 100644
--- a/docs.it4i/software/numerical-languages/octave.md
+++ b/docs.it4i/software/numerical-languages/octave.md
@@ -39,7 +39,7 @@ mkdir -p "$DIR"
 cd "$DIR" || exit
 
 # copy input file to scratch
-cp $PBS_O_WORKDIR/octcode.m .
+cp $SLURM_SUBMIT_DIR/octcode.m .
 
 # load octave module
 ml  Octave/6.3.0-intel-2020b-without-X11
@@ -54,7 +54,7 @@ cp output.out $SLURM_SUBMIT_DIR/.
 exit
 ```
 
-This script may be submitted directly to the PBS workload manager via the `salloc` command. The inputs are in the octcode.m file, outputs in the output.out file. See the single node jobscript example in the [Job execution section][1].
+This script may be submitted directly to Slurm via the `salloc` command. The inputs are in the octcode.m file, outputs in the output.out file. See the single node jobscript example in the [Job execution section][1].
 
 The Octave c compiler `mkoctfile` calls the GNU GCC 6.3.0 for compiling native C code. This is very useful for running native C subroutines in Octave environment.
 
-- 
GitLab