Closed HenrikBengtsson closed 2 years ago
Now qsub CLI option -d <path>
is only set when supported, cf. https://github.com/UCSF-Costello-Lab/LG3_Pipeline/commit/346c734e91160f794b7706dff939977639b13b64.
Turns out that this is sufficient to use C4's qsub
wrapper for Slurm.
So, I forgot that we have a
qsub
tool on C4 that emulates Torque/PBSqsub
. However, it does not support CLI option-d <path>
which set the working directory. The LG3 Pipeline uses it solely(*) asqsub -d ${PWD:?} ...
(see below).The reason for this is that Torque/PBS on TIPCC will launch jobs in the
$HOME
folder of the user unless-d <path>
is specified. In contrast,qsub
on C4 will launch jobs in the$PWD
working directory for all jobs (https://unix.stackexchange.com/a/207399/124078). So, if CLI option-d <path>
is the only thing preventing us from using the existing code as is on C4, we can probably work around it. I'm thinking of something like:(*) It also uses it as
qsub -d "$PBS_O_WORKDIR" ...
, but that should correspond toqsub -d ${PWD:?} ...
.(Manually curated to not show other CLI options named
-d
)