Add option for CRUJRA2024 add some compsets for Clm60 for it as well as a corresponding compset for Clm5

[slevis-lmwg]

Description of changes

Change the default datm input from GSWP3v1 to CRUJRA2024 for Clm6.
Add a CRUJRA2024 compset for clm5.

See #1895 for definition of DONE.

Specific notes

Contributors other than yourself (I hope I didn't forget any):
@wwieder @adrifoster @swensosc @djk2120 @ekluzek @olyson

CTSM Issues Fixed (include github issue #):
Resolves #1895

Are answers expected to change (and if so in what way)?
No. We will make a separate answer-changing PR to address Clm6 tests that do not specify the datm input, so that they get CRUJRA2024 instead of GSWP3v1.

Any User Interface Changes (namelist or namelist defaults changes)?
Adding Crujra to compset names.
Adding 2 new tests that explicitly include Crujra in their compset names.
Clm60 tests that do not include a datm option in their compset will default to Crujra in a later PR.

Does this create a need to change or add documentation? Did you do so?
It does, and I did not, yet.

Testing performed, if any:
See relevant posts below.

[slevis-lmwg]

First attempt at testing:
./create_test ERP_P128x2_Ld30.f45_f45_mg37.I2000Clm60FatesSpCrujraRsGs.derecho_intel.clm-FatesColdSatPhen

[slevis-lmwg]

Second set of tests on derecho:

OK make black & lint (the latter gives two warnings)
PASS python
PASS ./build-namelist_test.pl
OK ./run_sys_tests -s aux_clm -c ctsm5.3.021 --skip-generate
OK? ./run_sys_tests -s aux_cdeps -c /glade/campaign/cesm/cesmdata/cseg/cesm_baselines/cdeps1.0.55 --skip-generate

Checked the last two suites with these commands:

./cs.status.fails | grep -v PASS | grep -v NLCOM | grep -v '21: DIF'
./cs.status.fails | grep -v NLCOMP

In aux_cdeps, this test fails here but also in vanilla ctsm5.3.021:

SMS_D_Ld3.f10_f10_ais8gris4_mg37.DATAMODELTEST.derecho_gnu
ERROR: Invalid compset name, DATAMODELTEST, all stub components generated

[slevis-lmwg]

3rd round to test the "clm5" changes

PASS ./build-namelist_test.pl
PASS ./create_test ERP_P128x2_Ld30.f45_f45_mg37.I1850Clm50BgcCropCrujra.derecho_intel.clm-default

[slevis-lmwg]

TODOs

• @wwieder suggests making t232 the default grid with the introduction of the CRUJRA compsets in this PR if it's "dead simple"):
  Erik suggests we use t232 just for the new CRUJRA compset tests for now, because we don't have all the grid aliases for the grids we need for CTSM testing; @slevis-lmwg checked the testlist, and we already have 10 ne30pg3_t232 tests, which may cover our needs, and I will confirm with Erik
• Go over with @ekluzek
• Update to latest on master here and in cdeps
• Submit tests

[ekluzek]

@slevis-lmwg and I met and we went over the things to do and there's a conversation for them.

Since, we aren't doing the answer changing part here -- this could be put onto b4b-dev. What do you think about that @slevis-lmwg?

[slevis-lmwg]

on izumi IN PROGRESS with the revisions only (did not update to ctsm5.3.024, yet)
./run_sys_tests -s aux_clm -c ctsm5.3.021 --skip-generate

UPDATE
Next revert my last cdeps commit, update to ctsm5.3.024 and share1.1.8, and start aux_clm + aux_cdeps again.

[slevis-lmwg]

derecho testing started before 0fad468 commit to my cdeps branch

OK ./run_sys_tests -s aux_cdeps -c /glade/campaign/cesm/cesmdata/cseg/cesm_baselines/cdeps1.0.55 --skip-generate
OK ./run_sys_tests -s aux_clm -c ctsm5.3.024 --skip-generate

derecho failures now resolved

    FAIL FUNITCTSM_P1x1.f10_f10_mg37.I2000Clm50Sp.derecho_intel RUN time=67
    FAIL SMS_D.f10_f10_mg37.I2000Clm60BgcCrop.derecho_nvhpc.clm-crop RUN time=29

The FUNIT test passes with vanilla 024; a subsequent commit fixes this failure.
The nvhpc test in 024 failed in the SHAREDLIB_BUILD phase, so I will ignore this failure.
Also cmip6 tests are DIFF because we agreed to change them to CRUJRA2024 (unless I misunderstood and should have waited for the answer-changing PR to be merged and tagged at a later time).

---

izumi testing started after last commit to my cdeps branch
OK ./run_sys_tests -s aux_clm -c ctsm5.3.024 --skip-generate
...other than the usual long list of "failed to init" and the two other tests that always require manual handling. I will not proceed with this busywork since I'm not generating a baseline right now.

---

derecho additional testing started after the changes to subset_data
PASS python, black, lint
PASS ./build-namelist_test.pl

[slevis-lmwg]

@jedwards4b I get this unexpected FAIL that I have attributed (after testing) to the share1.1.8 update:
FUNITCTSM_P1x1.f10_f10_mg37.I2000Clm50Sp.derecho_intel RUN

Compare the first (failing one) against the second (passing baseline) in /glade/derecho/scratch/slevis:
FUNITCTSM_P1x1.f10_f10_mg37.I2000Clm50Sp.derecho_intel.C.20250213_155030_houfdw
FUNITCTSM_P1x1.f10_f10_mg37.I2000Clm50Sp.derecho_intel.C.20250213_154606_o5ajm0

In run/funit.log this message may be the explanation:
ld: /glade/work/slevis/git/LMWG_dev8/share/src/shr_log_mod.F90:148: undefined reference to esmf_logerrmod_mp_esmf_logwrite_

Shall I let you resolve this?

[slevis-lmwg]

Change TODO to say "make this option available at the command line"

[slevis-lmwg]

Other TODOs

• Update .gitmodules when cdeps tag is ready
• Finish ChangeLog/Sum

[jedwards4b]

@slevis-lmwg It looks like this unit test is not currently linking esmf. I suggest you check with @billsacks

[slevis-lmwg]

@ekluzek did I jump the gun here and in other cmip compsets? Should I have waited to do this in the to-be-done-later answer-changing PR?

If so, make sure I have a reminder in the corresponding issue (#2961?)