-
Notifications
You must be signed in to change notification settings - Fork 216
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 CHARGE_ACCOUNT to use subprojects and default to command line given project #2888
Conversation
While the documentation says the CHARGE_ACCOUNT falls back to PROJECT if it cannot be found in the user environment, user config, or machine config, it actually only fell back to the probed machine value and not the value set at the command line which should override the probed value. Now, CHARGE_ACCOUNT will actually fall back to the previously determined correct PROJECT value. Fixes #2676
This makes the help message for `--project` uniform for the three `create_*` scripts, and updates the CIME user config doccumentation to better describe PROJECT and CHARGE_ACCOUNT
@billsacks I updated a little of the documentation; what do you think of those updates? |
(i.e., you need a separate "Fixes" for each issue.) (My comment isn't enough to auto-close those: you'll need to edit your initial comment.) |
@billsacks Woops! You're right. Fixed my fixes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great - thanks a lot!
CHARGE_ACCOUNT was not falling back to the project value given on the command line in #2676 and was fixed in #2763 . However, #2763 no longer allowed for subprojects to be charged on OLCF machines. This reverts #2763 and fixes both #2676 and #2886.
Test suite: scripts_regression_tests.py on Titan
Test baseline: N/A
Test namelist changes: N/A
Test status: [bit for bit]
Fixes #2676
Fixes #2886
User interface changes?: None
Update gh-pages html (Y/N)?: Y
Code review: