Re: [slurm-users] Job error when using --job-name=`basename $PWD`

Hi Fabio, SLURM does not support usual shell expression evaluation or arbitrary variable substitution within #SBATCH arguments. If the option parser comes across options it does not understand, it tends to abort and assumes default settings for all mandatory unset options. This can be nasty f

[slurm-users] Changing node core count

Hi, I want to change the number of cores of a node. In sview, I right click on "update available features" and in the text box, I write "cpu=12". However, it seems that it is not correct as it writes an error in the bottom of sview window. Any guide? Regards, Mahmood

Re: [slurm-users] Job error when using --job-name=`basename $PWD`

Yeah, you can't do that in that fashion. If you want to do that, I'd suggest you put the option in the sbatch command you use to submit the script so: sbatch --job-name=`basename $PWD` /path/to/script.sh Brian Andrus On 7/28/2019 10:51 PM, Verzelloni Fabio wrote: Hi Everyone, I'm experien

Re: [slurm-users] Job error when using --job-name=`basename $PWD`

Dear Sven, thanks for the clarification. Fabio On 29.07.19, 11:44, "slurm-users on behalf of Sven Hansen" wrote: Hi Fabio, SLURM does not support usual shell expression evaluation or arbitrary variable substitution within #SBATCH arguments. If the option parser comes ac