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
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
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
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
Hi Fabio,
are you sure that command substition works in the #SBATCH part of the
jobscript? I don't think that slurm actally evaluates that, though I
might be wrong.
It seems like the #SBATCH after the --job-name line are not evaluated
anymore, therefore you can't start srun with two tasks (since
