Skip to content
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

ctsm5.3.021: Standardize time metadata (we will mark this as the release tag for ctsm5.3) #2052

Merged
merged 39 commits into from
Jan 30, 2025

Updated ChangeLog/Sum

e67249f
Select commit
Loading
Failed to load commit list.
Merged

ctsm5.3.021: Standardize time metadata (we will mark this as the release tag for ctsm5.3) #2052

Updated ChangeLog/Sum
e67249f
Select commit
Loading
Failed to load commit list.
Task list completed / task-list-completed succeeded Jan 30, 2025 in 0s

19 / 19 tasks completed

All tasks have been completed

Details

Required Tasks

Task Status
This diff from the baseline comes from comparing the .rest files, and the restart comparison failed in the baseline. The test does not differ from the baseline when comparing the .base files. So the issue to resolve is not this failure but the restart comparison in the baseline. Incomplete
Also the restart comparison passed here, so the restart comparison failure in the baseline may not be critical to solve, as there is no sign of anything else being affected. Incomplete
Make the same or equivalent change as eeedbc6 to the corresponding rtm/mosart files. Completed
Bring Erik's bug-fix from ESCOMP/MOSART#112 also to rtm. Completed
Resolve mosart/cpl BASELINE DIFFs discussed initially here
by replacing the if-statement in commit 692d183 with a comment, as explained in ESCOMP/MOSART#103 (comment). Completed
All of the above will be done in the mosart1.1.08 and rtm1_0_85 tags Completed
Take this opportunity to update cime6.1.49 to cime6.1.56 to avoid the rpointercpl bug? Should be fixed with b4b-dev on 1/16. Completed
Erik: Bring in the whatsnew in ctsm5.3 PR on b4b-dev Completed
Make sure b4b-dev is brought in by this point, currently planned as ctsm5.3.020 Completed
Finalize the What'sNew in CTSM5.3 document listed below: Sam R completed this. Completed
Update WhatsNew as per this document: https://docs.google.com/document/d/12KS5eU6gIaicZ4hJhgZWmys8fLLl5IkxwC_Pi76FuHw/edit?tab=t.0 Completed
Erik and Sam L went over this list: https://github.com/ESCOMP/CTSM/wiki/Minor-Version-Update-Protocols Completed
Do some testing for mksurfdata_esmf to make sure it's still working and will be ready for ctsm5.4 when the CMIP7 datasets come down: Sam L did this. Completed
Decide who should review what part of changes from the ctsm5.3.0 tag: Erik and Sam L decided that past reviews of this work were sufficient. Completed
Would it make sense for us to include the one-line ccs_config update to enable f09_t232? Incomplete
Is it complicated to make a new ccs_config tag? I doubt that I have permission. Incomplete
Or is there a way around making a new ccs_config tag? Incomplete
Or should we wait for the fix to come in later? Incomplete
FAIL ERS_D_Ld30.f45_f45_mg37.I2000Clm50FatesCruRsGs.izumi_nag.clm-FatesColdPRT2 CREATE_NEWCASE
Submitted again but with ./create_test and ran out of wallclock, so resubmitted and ran out of wallclock again, so tried ./create_test ... --wallclock 04:00:00 and ran out of wallclock a third time, so now increase the test's wallclock in testlist_clm.xml BUT FAILED AGAIN. The email notification always says that walltime was 1 hour. Incomplete
"time" is now the middle of "time_bounds" Incomplete
the elimination of the 0th time step Incomplete
Update to ccs_config_cesm1.0.20 and rerun testing on derecho, comparing against the baselines that I generated last.
See new relevant checkboxes in the next post. Completed
Test mksurfdata_esmf Completed
Replicate NCAR/LMWG_dev#70 (or 69 or 68) using this new release tag and expect the same namelists, though expect answers to change due to dust; I see these diffs ( case 70 < > my case): Completed
aux_clm RXCROP IN PROG comparing to Sam R's baseline Completed
ctsm_sci RXCROP IN PROG; no f09 baseline worth comparing to
RXCROPMATURITY_Lm61.f09_g17.IHistClm60BgcCrop.derecho_intel.clm-cropMonthOutput.G.20250125_113640_woab7n Completed
aux_clm PET_P64x2_D.f10_f10_mg37.I1850Clm50BgcCrop.derecho_intel.clm-default--clm-matrixcnOn_ignore_warnings RUN
Last time this test passed, so I started it manually with ./create_test Completed
izumi testing
PASS tests_0128-174438iz ./run_sys_tests -s mosart --skip-generate -c mosart1.1.08-ctsm5.3.021
OK tests_0128-174610iz ./run_sys_tests -s fates --skip-generate -c fates-sci.1.80.4_api.37.0.0-ctsm5.3.021
OK tests_0128-140950iz ./run_sys_tests -s aux_clm --skip-generate -c ctsm5.3.021 Completed