The job script is currently rendered by interpolating a multi-line string in the source code. It would be cleaner to use a Jinja template which is loaded from the data directory and interpolate from there.
Jinja will also enable "in-template" conditional statements, allowing us to alter the rendering routing to remove things like $PROJECT flags.
The other benefit is that using Jinja will enable us to abstract many of the shell commands into template strings, opening opportunities to completely change the subprocess commands down the track if needed.
Following discussions with @ccarouge yesterday...
The job script is currently rendered by interpolating a multi-line string in the source code. It would be cleaner to use a Jinja template which is loaded from the data directory and interpolate from there.
Jinja will also enable "in-template" conditional statements, allowing us to alter the rendering routing to remove things like
$PROJECTflags.The other benefit is that using Jinja will enable us to abstract many of the shell commands into template strings, opening opportunities to completely change the subprocess commands down the track if needed.