ctsm5.4.000: Alpha ctsm5.4.cmip7 to master

[ekluzek]

Description of changes

This brings the ctsm5.4 alpha branch to master.

This updates ALL of the surface and landuse timeseries datasets to version ctsm5.4
It's backwards compatible with ctsm5.3 datasets though, so older ctsm5.3 files can be used
Future scenarios are done using the cmip6 ctsm5.3 surface datasets. The new XML variable
CLM_CMIP_ERA controls this.

A few other updates come in as well for clm6_0:
Initial Condition (IC) files
New parameter file
New crop calendar datasets
Changes to fire parameters
New population density file

Specific notes

Contributors other than yourself, if any: @slevis-lmwg @wwieder @olyson @samsrabin @lawrencepj1 @lifang0209
@slevis-lmwg did the great bulk of the work here

CTSM Issues Fixed (include github issue #):
A list of issues apply here

Are answers expected to change (and if so in what way)? Yes! New surface datasets means everything will be different

Any User Interface Changes (namelist or namelist defaults changes)? Yes defaults updates

All fsurdat and flanduse_timeseries files updated
Fire parameters update: (li2024gswp3, and li2024crujra fire_method):
- defo_fire_precip_thresh_bet
- cli_scale
- cropfire_a1
IC files: clm6_0 finidat files
IC Interpolation: use_init_interp and init_interp_attributes, init_interp_fill_missing_urban_with_HD==TRUE
Parameter file update, clm6_0
Crop Calendar files updated: stream_fldfilename_cultivar_gdds
Population density updated:

New XML variable added: CLM_CMIP_ERA (cmip6 or cmip7)

SSP Future scenarios can only be run with cmip6 surface/landuse.timeseries datasets

Does this create a need to change or add documentation? Did you do so? Yes Yes at least some updates

Testing performed, if any: Previous alpha tags have had the following test lists run:
aux_clm ctsm_sci mosart rtm fates

[slevis-lmwg]

Testing

NOTE: I see us possibly renaming the baselines. For now, I named them by the tag that ran them.

• derecho

OK ./build-namelist_test.pl
PASS make black and lint
PASS python -u and -s
OK ./run_sys_tests -s aux_clm -c ctsm5.3.085 -g alpha-ctsm5.4.CMIP7.21.ctsm5.3.085
OK ./run_sys_tests -s ctsm_sci -c ctsm_sci-alpha-ctsm5.4.CMIP7.19.ctsm5.3.082 -g ctsm_sci-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085
OK ./run_sys_tests -s fates -c fates-sci.1.88.0_api.42.0.0-ctsm5.3.083 -g fates-sci.1.88.0_api.42.0.0-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085    
OK ./run_sys_tests -s rtm -c rtm1_0_89-ctsm5.3.065 -g rtm1_0_89-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085
OK ./run_sys_tests -s mosart -c mosart1.1.12-ctsm5.3.066 -g mosart1.1.12-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085

I confused myself:
This seemed wrong COMP: paramfile = clm60_params.ctsm6_li2024.c250822.nc'
...but ctsm5.4 is not getting the final clm6 paramfile that appears in the post-5.4 branch!

Checking mosart with
./cs.status.fails | grep -v NLCOMP | grep -v 'me baseline files were mi' | grep -v '66: DI'

• izumi IN PROGRESS

./run_sys_tests -s aux_clm -c ctsm5.3.085 -g alpha-ctsm5.4.CMIP7.21.ctsm5.3.085
./run_sys_tests -s fates -c fates-sci.1.88.0_api.41.0.0-ctsm5.3.082 -g fates-sci.1.88.0_api.42.0.0-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085
OK ./run_sys_tests -s rtm -c rtm1_0_89-ctsm5.3.065 -g rtm1_0_89-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085
OK ./run_sys_tests -s mosart -c mosart1.1.12-ctsm5.3.066 -g mosart1.1.12-alpha-ctsm5.4.CMIP7.21.ctsm5.3.085