-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow passing batch arguments through case.submit command line options #922
Labels
Comments
The original PR can be seen here. |
This seems like a good idea. |
ghost
assigned jgfouca
Feb 8, 2017
ghost
added
the
in progress
label
Feb 8, 2017
rljacob
pushed a commit
that referenced
this issue
Feb 8, 2017
This merge adds an interannual forcing G compset, named GMPAS_IAF. It also changes GMPAS to be GMPAS_NYF to avoid confusion. [BFB] * douglasjacobsen/scripts/change-mpas-g-cases: Add a GMPAS_IAF compset, and change GMPAS to GMPAS_NYF
rljacob
pushed a commit
that referenced
this issue
Feb 8, 2017
This merge adds an interannual forcing G compset, named GMPAS_IAF. It also changes GMPAS to be GMPAS_NYF to avoid confusion. [BFB] * douglasjacobsen/scripts/change-mpas-g-cases: Add a GMPAS_IAF compset, and change GMPAS to GMPAS_NYF
jgfouca
added a commit
that referenced
this issue
Feb 14, 2017
Test suite: code_checker, by-hand Test baseline: Test namelist changes: Test status: bit for bit Fixes #922 User interface changes?: -a option to case.submit Code review: @jedwards4b * jgfouca/allow_arbitrary_batch_args: Add support to case.submit for sending arbitrary arguments to the batch submission cmd
ghost
removed
the
in progress
label
Feb 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggested by @erichlf over on ACME.
If one wants to add arguments to the batch submit command, they have to edit env_batch.xml. For experimenting and trying something once, it would be easier to pass additional commands as an argument to case.submit like this:
case.submit --batchargs '--mail-user=user@server.com --mail-type=END'
The text was updated successfully, but these errors were encountered: