-
Notifications
You must be signed in to change notification settings - Fork 371
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
Fixes CNP Budget #6233
Fixes CNP Budget #6233
Conversation
Sets the values for three fluxes that are included in monthly CNP budgets. Fixes #6230 [BFB]
|
I did a test merge of this to next and received DIFF for |
@peterdschwartz we need this merged because it fixes month-long restart tests with the standard v3 F-case. Can't wait for it to work with FATES. |
Sets the values for three fluxes that are included in monthly CNP budgets. Fixes #6230 [BFB]
This caused ERP_Ld15.ne4pg2_ne4pg2.IELMFATES.chrysalis_intel.elm-fates_cold_allvars to diff. Expected? |
@rljacob Did you miss my comment above? |
Ah I missed that. Thanks. |
This fix allows SMS_Lm1.ne4pg2_oQU480.F2010 and SMS_Ly1.ne4pg2_oQU480.F2010 to run and pass. ERP_Lm3.ne4pg2_oQU480.F2010 and ERS_Ld31.ne4pg2_oQU480 no longer have runtime fails but do fail the restart test with "2 had differences in fill patterns" (for ERP) and "1 had differences in fill patterns" (for ERS). |
@rljacob Sorry, I'm not sure where to look for those tests on CDash |
They're in the gcp-12 report for extra-coverage: https://my.cdash.org/viewTest.php?onlyfailed&buildid=2502048 |
SMS_Ln9.ne4pg2_oQU480.F2010..eam-outfrq9s has diffs with baselines. |
Further investigation and discussion with @bishtgautam: any test that outputs an elm h0 file will have a diff like the above. So all prod-suite tests need to be blessed as well. |
@bishtgautam please update the PR description with your other changes. |
@rljacob I have updated the PR description. |
Hello, I was running E3SMv3.0.0 with a non-January starting month (e.g., 10), using the corresponding ELM restart file from a previous run (e.g., CASE.elm.r.0001-10-01.nc) as the initial dataset (finidat) for ELM. However, the CNPBudget fails its annual check for carbon state (net change in state >> time integrated flux) at the end of year, due to all annual beginning values being zeros.
Is there a way to fix this issue, or is it necessary to run the model starting from January? Thank you in advance for your help. |
was the previous run that made the restart file also from v3.0.0? |
Yes. It is a monthly restart file generated from a v3.0.0 run that starts from January. |
I am not sure how the time integrated flux is calculated for the annual budget check, but it seems that the annual beg values from finidat (no matter if it is specified by user or not) is not updated to the ELM restart files if the model does not start from month 01, causing the annual beg values being all zeros. |
@kchong75 Can you please share the commands to reproduce the error? It is quite possible that I had not considered the case when a simulation starts in the middle of the year instead of 1st-Jan. |
The following updates are made to fix the CNP budget in ELM.
Fixes #6230
[BFB] (except a new field is added in the ELM restart file)