Skip to content

ctsm5.4.065: Move CTSM tests from gx grids to t233 grid - #4234

Open
slevis-lmwg wants to merge 26 commits into
ESCOMP:masterfrom
slevis-lmwg:mv_gx_tests_to_t233
Open

slevis-lmwg wants to merge 26 commits into
ESCOMP:masterfrom
slevis-lmwg:mv_gx_tests_to_t233

Conversation

@slevis-lmwg

@slevis-lmwg slevis-lmwg commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Description of changes

Similar to #4223 but for g16, g17, g37 grids

Specific notes

Contributors other than yourself, if any:

CTSM issues resolved or otherwise addressed, if any:
Contributes to #2540 (resolves?)

Testing planned or performed, if any:

  • aux_clm
    • derecho tests_1012-181808de
    • izumi

Requirements before merge:

  • The code in this PR branch builds with no errors.
  • The code in this PR branch runs with no errors. Briefly describe tested configuration(s):
  • This does not change answers for unchanged tests; tests going from gx grids to t233 run on the new grid and have their names updated, so the test-suites will not compare them to the baseline
  • This PR either (a) does not create a need to update the documentation or (b) includes required documentation updates (see guidelines for contributing documentation). Which?:

@slevis-lmwg slevis-lmwg self-assigned this Sep 30, 2026
@slevis-lmwg slevis-lmwg added the b4b bit-for-bit label Sep 30, 2026
@ekluzek ekluzek added the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Sep 30, 2026
@ekluzek

ekluzek commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

I'd call this as something that should go on master, because when compsets change you can't verify that things are b4b. And hence it could hide an accidental non-b4b change on the b4b-dev branch after this was merged.

@wwieder wwieder added testing additions or changes to tests and removed next this should get some attention in the next week or two. Normally each Thursday SE meeting. b4b bit-for-bit labels Oct 1, 2026
@wwieder wwieder added this to the ctsm6.0.0 (code freeze) milestone Oct 1, 2026
@slevis-lmwg
slevis-lmwg changed the base branch from b4b-dev to master October 2, 2026 14:49
Comment thread cime_config/testdefs/testlist_clm.xml Outdated
Comment thread cime_config/testdefs/testlist_clm.xml Outdated
Comment thread cime_config/testdefs/testlist_clm.xml Outdated
@slevis-lmwg slevis-lmwg changed the title Move CTSM tests from gx grids to t233 grid ctsm5.4.0xx: Move CTSM tests from gx grids to t233 grid Oct 5, 2026

@ekluzek ekluzek left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We went over this together. And I noted the thing about g37 grids should be t201 as the low resolution MOM grid. And we realized that MOSART and RTM (and ccs_config) also need to be updated similarly.

Comment thread cime_config/testdefs/ExpectedTestFails.xml Outdated
@slevis-lmwg slevis-lmwg added the blocked: dependency Wait to work on this until dependency is resolved label Oct 5, 2026
@slevis-lmwg

Copy link
Copy Markdown
Contributor Author

Marking "blocked" due to the checkbox above stating that we need to "add to ccs_config: ne30_t233, f19_t233_gris4 and make new tag"

ctsm5.4.063: Move CTSM tests from t232 to t233

Updating testlist_clm.xml, ExpectedTestFails.xml, config_compsets.xml, and documentation that needs updating.

NB: Moving tests from t232 to t233 but postpone the change for LII2 tests (issue ESCOMP#4245).

Changes answers relative to the baseline, only for cases with grids that changed to the t233 grid, and only due to the grid update.

PR ESCOMP#4223
Resolves issue ESCOMP#4238 by removing NorESM test
Contributes to ESCOMP#2540 Move testing from POP to MOM masks

slevis resolved conflicts:
cime_config/testdefs/testlist_clm.xml
Comment thread bld/namelist_files/namelist_defaults_ctsm.xml Outdated
Comment thread bld/namelist_files/namelist_defaults_overall.xml
@slevis-lmwg

slevis-lmwg commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor Author

I started ./run_sys_tests -s aux_clm -c ctsm5.4.063 -g ctsm5.4.064_PR4234 on derecho ONLY for now. If all goes well, then we could consider this PR for the next merge/tag ctsm5.4.064.

For reference: tests_1012-181808de

@slevis-lmwg

slevis-lmwg commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor Author

./cs.status.fails -c NLCOMP | grep -v 'TED FAILURE' | grep -v 'does not exist' failures to investigate:

FAIL SMS_D_Ld5_PS.f09_f09_mt233.I1850Clm60BgcCrop.derecho_gnu.clm-f09_ObscureStreamOpts BASELINE ctsm5.4.063: DIFF
FAIL LII2FINIDATAREAS_D_P256x2_Ld1.f09_t232.I1850Clm60BgcCrop.derecho_intel.clm-default--clm-matrixcnOn_ignore_warnings COMPARE_base_no_interp
FAIL LII2FINIDATAREAS_D_P256x2_Ld1.f09_t232.I1850Clm60BgcCrop.derecho_intel.clm-default COMPARE_base_no_interp
FAIL LII_D_Ld3_PS.f19_t233.I2000Clm50BgcCrop.derecho_intel.clm-default--clm-matrixcnOn RUN time=253
PEND LII_D_Ld3_PS.f19_t233.I2000Clm50BgcCrop.derecho_intel.clm-default--clm-matrixcnOn COMPARE_base_no_interp
FAIL LII_D_Ld3_PS.f19_t233.I2000Clm50BgcCrop.derecho_intel.clm-default RUN time=235
PEND LII_D_Ld3_PS.f19_t233.I2000Clm50BgcCrop.derecho_intel.clm-default COMPARE_base_no_interp
FAIL LVG_Ld5_D.f10_f10_mt201.I1850Clm60Bgc.derecho_intel.clm-no_vector_output COMPARE_base_more_virtual
FAIL PFS_Ld10_PS.f19_t233.I2000Clm50BgcCrop.derecho_intel.clm-default--clm-matrixcnOn RUN time=33
FAIL PFS_Ld10_PS.f19_t233.I2000Clm50BgcCrop.derecho_intel RUN time=38
FAIL SMS_D_Ld1.ne30pg3_t233.I1850Clm60BgcCropSpinup.derecho_intel.clm-crop BASELINE ctsm5.4.063: DIFF
FAIL SMS_D_Ld3_PS.f09_t233.I1850Clm60BgcNoAnthroRtm.derecho_intel.clm-decStart1851_noinitial--clm-matrixcnOn RUN
  • For now revert the LII_* tests to their previous grid, as we did in ctsm5.4.063: Move CTSM tests from t232 to t233 #4223 for the LII2 tests (Update LII_ + PFS tests from g17 to t233 grid when finalizing our ICs #4245).
  • I did not expect the LII2* tests to fail as they already point to the previous grid, but the LII2 tests with t232 now set use_init_interp = .true. and init_interp_method = 'use_finidat_areas', while running with the new grid now works!
  • I did not expect DIFFs from the baseline
    • SMS_D_Ld5_PS.f09_f09_mt233.I1850Clm60BgcCrop.derecho_gnu.clm-f09_ObscureStreamOpts has many and large DIFFs, while it passes in vanilla ctsm5.4.063; reverting my mods to namelist_defaults_overall.xml STILL fails; the test is missing use_init_interp = .true. and init_interp_method = 'general' WHICH MAY ALSO EXPLAIN SOME OF THE OTHER FAILURES. Claude suggests accepting this DIFF because this test now finds a finidat that does not require interpolation.
    • SMS_D_Ld1.ne30pg3_t233.I1850Clm60BgcCropSpinup.derecho_intel.clm-crop passes in vanilla ctsm5.4.063, and the test DIFF comes from a single field PCT_GLC_MEC; this test is also missing use_init_interp = .true. and init_interp_method = 'general', so ok to accept this DIFF as it now does not require interpolation.
  • LVG DIFF comes from a single field PCT_GLC_MEC, and I thought it might be a one-time DIFF due to the change in grid. I ran again, this time against the 064 baseline, but the test still fails in COMPARE_base_more_virtual, so I need to add it to Update LII_ + PFS tests from g17 to t233 grid when finalizing our ICs #4245.
  • PFS tests need to revert to their prev. grid, as they do not set use_init_interp to true.

@slevis-lmwg

slevis-lmwg commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor Author

@ekluzek in the above list of failures,
SMS_D_Ld3_PS.f09_t233.I1850Clm60BgcNoAnthroRtm.derecho_intel.clm-decStart1851_noinitial--clm-matrixcnOn

  • fails consistently with "floating invalid" in line 764 CNSoilMatrixMod.F90, not line 793 of the tests that pass by resubmitting
  • its old counterpart with f09_g17 passed in the baseline + again just now
  • in rtm's testlist we use f09_f09_mt233 ONLY, but the test still fails with that
  • in rtm's testlist we never test Bgc, how come? It's an omission, though we do in aux_clm, so ok
  • testing rtm with matrixcnOn seems unnecessary since we use the latter ONLY in spin-up (rivers off), and the test without matrixcnOn passed just now, so I updated this test accordingly (I have not rerun to generate its baseline)
  • document this failure in a ctsm issue for the benefit of paleo users
  • create issue that we want a new SSP matrixcn test that checks that cpl_hist spinup works with NoAnthro (with and without Rtm)

@slevis-lmwg

slevis-lmwg commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor Author

@billsacks I'm updating CTSM tests from the gx grids to t233. I want to ask you about this failure:
FAIL LVG_Ld5_D.f10_f10_mt201.I1850Clm60Bgc.derecho_intel.clm-no_vector_output COMPARE_base_more_virtual
I thought it might be a one-time failure, but rerunning against the new baseline failed the same way (path below). We will keep a short list of tests using the gx grids until we finalize initial conditions (#4245), and I now think that this test falls in that category. Do you agree?

/glade/derecho/scratch/slevis/LVG_Ld5_D.f10_f10_mt201.I1850Clm60Bgc.derecho_intel.clm-no_vector_output.C.20261013_183514_4298nm

@wwieder
wwieder requested a review from ekluzek October 15, 2026 16:07
@slevis-lmwg
slevis-lmwg marked this pull request as ready for review October 15, 2026 16:09
@slevis-lmwg slevis-lmwg changed the title ctsm5.4.0xx: Move CTSM tests from gx grids to t233 grid ctsm5.4.065: Move CTSM tests from gx grids to t233 grid Oct 15, 2026
@slevis-lmwg

slevis-lmwg commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor Author

Since updating submodules... Consider updating CIME for #4239 here?

From meeting with Erik: No, because this PR here is effectively an answer-changing PR.

@slevis-lmwg

slevis-lmwg commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor Author
  • FAIL... Regarding the LVG test, Erik suggested pointing the test to the finidat generated previously by the test itself to see if it passes; I pointed to the finidat found in the test's case2 (manually reintroducing use_init_interp and related settings as found in the original test, but exice is still different) and rerunning cs.status.20261016_182626_h14wtz
  • FAIL... Repeat with the finidat found in the test's case1 (manually reintroducing use_init_interp and related settings as found in the original test, but exice is still different) and rerunning cs.status.20261016_182626_h14wtz
  • PASS Confirm that LVG passes vanilla ctsm5.4.063: ./create_test LVG_Ld5_D.f10_f10_mg37.I1850Clm60Bgc.derecho_intel.clm-no_vector_output -c /glade/campaign/cgd/tss/ctsm_baselines/ctsm5.4.063 with cs.status.20261016_183745_cle1ai

@billsacks

Copy link
Copy Markdown
Member

Sorry that I didn't see the question about the LVG test earlier.

I do not expect changing finidat to resolve this.

I checked the test failure, and I see that the only field that differs is PCT_GLC_MEC. I think the right thing to do is to simply exclude this history field from the test, using hist_fexcl. You can do this via append_to_user_nl_files in lvg.py. (You can give a list of strings to append to the user_nl files; do this hist_fexcl for both case1 and case2.)

I think I understand why this is needed: There is a grid cell on the south tip of South America that has 0% glacier which must newly be present within the land mask (I haven't looked at the change in land mask, but I assume that's why it's a problem now). In the base case, this has 0% for each glacier column, but in the case with extra virtual glacier, it must fall within the Antarctica mask, and so it is given non-zero percentages in each column. This is a fine difference and should just be ignored.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked: dependency Wait to work on this until dependency is resolved testing additions or changes to tests

Projects

Status: In progress - master
Status: In Progress

Development

Successfully merging this pull request may close these issues.

5 participants