-
Notifications
You must be signed in to change notification settings - Fork 146
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
ndep changes are causing failures in CESM testing #790
Labels
bug
Something isn't working correctly
Comments
I will add the fix to PR #761. modified code:
|
Looks good, thank you. |
jtruesdal
added a commit
that referenced
this issue
Apr 28, 2023
cam6_3_109: Science and infrastructure changes to improve energy/mass budget reporting and closure. Add inline energy/mass budgets support. (#519) Science changes are included that help close the mass and energy budgets of physics and the SE/MPAS dycores (#521) as well as adding all water constituents to atmospheric mass (pressure) (#520). Lastly a small fix for issue #790. We've been testing with an interim CTSM branch that has MPAS land boundary condition files. There is a parallel PR ESCOMP/CTSM#1501 to get these updated MPAS files into the land repo. As of this PR energy/mass budgets have been added for physics and the SE and MPAS dycores. The work of budget improvement, expansion to other supported dycores, and refactor of the logging infrastructure will continue in future PRs. Most functional regression testing are passing and baselines are expected to fail due to the climate changing science updates. Similar to amwg_diagnostic functionality, energy/mass budget diagnostic fields will be added to a history file via the thermo_budget_histfile_num namelist parameter. Globally averaged energy budget summaries are also calculated and written to the atm log file every time the budget history tape is written to. The period over which energy and mass budgets are averaged is the same as the averaging period of the history budget file. Thus history budgets can be output/averaged at time step, hour, or month resolutions using the nhtfrq variable specific to the budget history file identified by (.false.) The default is .false. (no budgeting) because of the global gathers needed to create the budgets. closes #790 closes #519 closes #520 closes #521 closes #789
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
According to @fischer-ncar the following two tests failed regression testing:
The fix according to @jedwards4b:
@brian-eaton suggested the following check:
While we're at it we should check the iostat return from the open command. That would have immediately pointed Chris to the culprit.
What are the steps to reproduce the bug?
Run the reported regression test
What CAM tag were you using?
cam6_3_106
What machine were you running CAM on?
CISL machine (e.g. cheyenne)
What compiler were you using?
Intel
Path to a case directory, if applicable
No response
Will you be addressing this bug yourself?
Any CAM SE can do this
Extra info
No response
The text was updated successfully, but these errors were encountered: