This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
guides:slurm:passing-variables-from-command-line [29.10.2019 15:10] 127.0.0.1 external edit |
guides:slurm:passing-variables-from-command-line [14.03.2020 14:02] Teemu Kuulasmaa |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | #Passing variables from command line | + | # Passing variables from command line |
##Passing variables into a job at submission | ##Passing variables into a job at submission | ||
Line 16: | Line 16: | ||
The first example will replace the user's environment with a new environment containing only values for A and b and the SLURM_* environment variables. The second will add the values for A and b to the existing environment. | The first example will replace the user's environment with a new environment containing only values for A and b and the SLURM_* environment variables. The second will add the values for A and b to the existing environment. | ||
- | ##Using variables to set SLURM job name and output files | + | ## Using variables to set SLURM job name and output files |
SLURM does not support using variables in the #SBATCH lines within a job script. However, values passed from the command line have precedence over values defined in the job script. So the job name and output/ | SLURM does not support using variables in the #SBATCH lines within a job script. However, values passed from the command line have precedence over values defined in the job script. So the job name and output/ |