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
Interpolation into the command and job script is (mostly) handled through additional kwargs into the submit function, however, with the addition of advanced directives I can see this quickly getting out of hand, particularly when a keyword argument that influences directives also conflicts with something that should be interpolated into the job script proper (i.e. storage).
Suggest having explicit dictionaries for command / job script arguments, OR leaving the directives as a dictionary that can also be accessed via jinja (inside the job script).
For example:
job_id=client.submit("job.sh", cargs=dict(), jargs=dict())
# ....OR something like# assumed storage=["gdata/rp24", "scratch/rp23"]# Maintain both a rendered and unrendered versiondirectives["storage"] =storagedirectives_str=self._render_directives(directives)
# Add both to the interpolation contextcontext["directives"] =directivescontext["directives_str"] =directives_str
I'll just leave this issue here for something to think about.
The text was updated successfully, but these errors were encountered:
Interpolation into the command and job script is (mostly) handled through additional kwargs into the
submit
function, however, with the addition of advanced directives I can see this quickly getting out of hand, particularly when a keyword argument that influences directives also conflicts with something that should be interpolated into the job script proper (i.e. storage).Suggest having explicit dictionaries for command / job script arguments, OR leaving the directives as a dictionary that can also be accessed via jinja (inside the job script).
For example:
I'll just leave this issue here for something to think about.
The text was updated successfully, but these errors were encountered: