You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Common Batch Options to Slurm section in Andes, we talk about the -o and -e flags. That section seems to imply that if we don't use -o or -e, the output is automatically saved to a file with the filename <job_script>.o$SLURM_JOB_UID. This is actually not the case. By default both standard output and standard error are directed to a file of the name "slurm-%j.out", where the "%j" is replaced with the job allocation number.
Also, we should provide some guidance on using some commonly used filename patterns like %j for the -o and -e files (current documentation doesn't provide that information).
The text was updated successfully, but these errors were encountered:
In the Common Batch Options to Slurm section in Andes, we talk about the
-o
and-e
flags. That section seems to imply that if we don't use -o or -e, the output is automatically saved to a file with the filename<job_script>.o$SLURM_JOB_UID
. This is actually not the case. By default both standard output and standard error are directed to a file of the name "slurm-%j.out", where the "%j" is replaced with the job allocation number.Also, we should provide some guidance on using some commonly used filename patterns like
%j
for the -o and -e files (current documentation doesn't provide that information).The text was updated successfully, but these errors were encountered: