Merge b4b-dev

Some fixes for run_neon that came up in ctsm5.1.dev172.
Small bug fix for units of vector format hillslope hydrology.
Start adding PLUMBER2 users-mods (NOT functional)

Update submodule tags to pass runoff from cism to rof

- Update MOSART, CMEPS, and CISM so CISM runoff goes to ROF rather than CTSM
- Update RTM with fix needed for Paleo LGM work

Contributors:
@mvertens, @jedwards4b, @billsacks, @Katetc, @ekluzek, @slevis-lmwg

 Fixes ESCOMP#2590 Update CMEPS/MOSART/CISM/RTM tags
 Fixes ESCOMP/RTM#50 Likely wrong RTM river flux to MOM6 within cesm2_3_beta17

 Differences in namelist 'mosart_inparm':
  missing variable: 'do_rtmflood'
  missing variable: 'finidat_rtm'
  missing variable: 'frivinp_rtm'
  missing variable: 'rtmhist_fexcl1'
  missing variable: 'rtmhist_fexcl2'
  missing variable: 'rtmhist_fexcl3'
  missing variable: 'rtmhist_fincl1'
  missing variable: 'rtmhist_fincl2'
  missing variable: 'rtmhist_fincl3'
  missing variable: 'rtmhist_mfilt'
  missing variable: 'rtmhist_ndens'
  missing variable: 'rtmhist_nhtfrq'
  found extra variable: 'budget_frq'
  found extra variable: 'fexcl1'
  found extra variable: 'fexcl2'
  found extra variable: 'fexcl3'
  found extra variable: 'fincl1'
  found extra variable: 'fincl2'
  found extra variable: 'fincl3'
  found extra variable: 'finidat'
  found extra variable: 'frivinp'
  found extra variable: 'mfilt'
  found extra variable: 'mosart_euler_calc'
  found extra variable: 'mosart_tracers'
  found extra variable: 'ndens'
  found extra variable: 'nhtfrq'
  found extra variable: 'use_halo_option'

Changes answers
- what code configurations: mosart and rtm
- what platforms/compilers: all
- nature of change: mosart roundoff; rtm larger than roundoff due to bug fix; the latter also affects bgc variables

 We are ignoring strange diffs from baseline in two tests in variable
 FATES_TRANSITION_MATRIX_LULU as explained in issue ESCOMP#2656.

Same as mksrf_GlacierRegion_10x10min_nomask_cd5_c220131.nc but with
GLACIER_REGION=1 (Points outside Greenland itself but which might become
ice-covered in an evolving Greenland simulation) merged into
GLACIER_REGION 0, then 2 changed to 1 and 3 changed to 2. We are
removing the old GLACIER_REGION=1 even though this means we cannot
generate SMB in areas outside the initial CISM Greenland ice mask,
because it created problematic non-physical behavior. See
ESCOMP#423 for details.

We are removing the old second region (in CISM's Greenland domain but
outside Greenland itself). So updating the namelist defaults to align
with this removal.

We realized that the renumbering of regions could cause silent wrong
behavior if a user was using an old user_nl_clm file that specified
behaviors for the old 4 regions. So instead, we're keeping the old
numbering for the Greenland and Antarctica regions and keeping
GLACIER_REGION=1 unused for now.

- Weaken the consistency checks between icemask and glc_behavior: We no
  longer require has_virtual_columns and melt_replaced_by_ice - we now
  only require that we do NOT have (melt_replaced_by_ice_grc
  .and. .not. has_virtual_columns_grc).

- Prevent users from setting the combination of
  glacier_region_melt_behavior = "replaced_by_ice" with
  glacier_region_ice_runoff_behavior = "melted". (While there is nothing
  fundamentally wrong with this combination, it can result in
  problematic, non-physical fluxes - particularly, a large positive
  sensible heat flux during glacial melt in regions where the icesheet
  is not fully dynamic and two-way-coupled; see
  ESCOMP#423 for details.)

- Only update glacier areas and topo values where the glacier region
  behavior is 'virtual', because that's the only region where we are
  guaranteed to have all of the elevation classes we need in order to
  remain in sync. (Note that, for conservation purposes, it's important
  that we update areas in all regions where we're fully-two-way-coupled
  to the icesheet and we're computing SMB; this requirement is checked
  in check_glc2lnd_icemask.) This change is needed now that we no longer
  require grid cells within the ice mask to have the 'virtual' behavior.

- Ensure that glc_dyn_runoff_routing is 0 wherever we're not computing
  SMB. This change isn't strictly necessary with the current code,
  because it appears that glc_dyn_runoff_routing is only used within the
  do_smb filter. However, this change makes the code more robust to
  future changes. This change is needed now that we no longer require
  grid cells within the ice mask to have the melt_replaced_by_ice
  behavior.

Also fixes / adds unit tests covering these behavior changes

We should use the maximum existing index, without regards for the
relative coverage of the different indices.

Fix regridding of glacier region

Turn on explicit AC, Leung_2023, and excess ice for clm6

Namelist defaults now turn on excess ice, explicit AC, Leung_2023 in
clm6; they also pick up new finidat files for clm6. We use a f09 1850
finidat for all clm6 cases because that's all that we have generated
for now.

…tlai

…nt number to surface datasets

Bring b4b-dev branch to main CTSM development.

- PLUMBER2 for ctsm5.2 datasets
- Last bit of PPE changes for namelist and parameter file settings
- Update run_sys_tests on Derecho for compiler jobs to run using 16 tasks
- Bring in a fix for dust emissions for coupling with CAM

Update cs.status parsing script to make expected BASELINE fails more obvious

Fix some issues with finding IC files for certain lnd_tuning_modes: all for cam7,
   clm5_0_cam6.0, and clm6_0_cam6.0

…aset

Remove the error messaging that talks about
old/incompatible surface dataset because we
now are checking for the surface dataset compatability.

Add some notes that dataset version is only
updated when the new datasets will NOT be
backwards compatible with the previous
version.

Same list of finidats that I updated in this PR:
https://github.com/ESCOMP/CTSM/pull/2724/files

…heck, fix version guessing inside it, fix spelling error, respond to rest of the review conversations

Add version to srf datasets

Update default fire_emis_factors_file

FATES history flushing update

This updates the way in which FATES history output is flushed during
model initialization
utilizing a new FATES-side subroutine, flush_all_hvars.  This update
also makes corrections
to a subset of FATES testmods as well as expands the FATES test list by
duplicating two
existing tests to run on different compilers for better coverage.  The
FATES submodule tag
has been updated to the latest scientific tag as well.

…rawpftlai

Resolves ESCOMP#2744

Fix mapping of soil texture

…t unit testter works

Update hillslope testing fsurdat to 5.3

… defaults and user-mods fixing ESCOMP#2752

…f_in_namelist_defaults

Update surface datasets in namelist defaults

…the part that changes from ctsm5.2.028

…og_readme_update

Enable li2024crujra fire_method

…stmods for Sp compsets turn fire-emissions off by pointing to nofireemis testmod

…esolution tests as we aren't going to do that

…rawpftlai

 Conflicts:
	cime_config/testdefs/testmods_dirs/clm/smallville_dynlakes_monthly/user_nl_clm
	cime_config/testdefs/testmods_dirs/clm/smallville_dynurban_monthly/user_nl_clm

…with 78 pft fire emission files in ESCOMP#2759

…esmf

…s guide

…t fire emission factors datasets

…le and just use the local n_pfts variable that matches the name on the dataset

Fix some issues in finidat settings.

For clm6_0 use phys rather than lnd_tuning_mode for 1850 and 2000.
Pointing to the spunup f09 1850 for f09/f19 1850 and 2000.

Some lines for 2003 and 2013 were incorrect in the surrounding code block.

…rawpftlai

…6.0 and clm6_0_cam7.0, unit tests work, there's likely some tests that would have failed without this

Remove mkprocdata_map

…rawpftlai