Arbitrary Slurm options #12
Replies: 1 comment
-
Yes, it is recommended to use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Looking at the arguments to
crew_controller_slurm
, I notice that there is no argument likesbatch_options
for specifying arbitrary#SBATCH
options. I suspect this is needed because there are too manysbatch
flags to ever make an argument for each one (likeslurm_cpus_per_task
). It seems that luckilyscript_lines
are inserted just after the#SBATCH
lines, so it should be possible to inject more using this parameter. Is this the recommended approach? Or should there be a dedicated parameter for this? I think ansbatch_options
that takes a named character vector of options would be nice, and may even remove the need forslurm_cpus_per_task
and co.Beta Was this translation helpful? Give feedback.
All reactions