Initial port of CTSM into RASM

[apcraig]

Description of changes

Initial port of CTSM into RASM.

Specific notes

• Rename the bld directory to bld.cime and implement a new bld directory for use in RASM. The current scripts leverage the RASM Makefile and have a hardwired lnd_in and input file list.
• Modify
  • src/cpl/mct/clm_cpl_indices.F90 comment out coupling fields that don't exist in RASM
  • src/cpl/mct/lnd_comp_mct.F90 update init/run/final interfaces to RASM standard, add back _ss arguments
  • src/cpl/mct/lnd_import_export.F90 comment out coupling fields that don't exist and make consistent with RASM
  • src/utils/clmfates_paraminterfaceMod.F90 rename module from CLMFatesParamInterfaceMod to CLMFates_ParamInterfaceMod to be consistent with filename for Dependency build
  • src/main/pftconMod.F90 change CLMFatesParamInterfaceMod to new module name
  • src/fates/main/FatesInterfaceMod.F90 change CLMFatesParamInterfaceMod to new module name
  • src/main/ncdio_pio.F90.in modifications needed for shr_pio_getioformat
• Add check for tiny negative precip values sent as coupling fields and set them to zero. These values seems to be creating problems for the CTSM soil model. Done in ctsm/src/cpl/mct/lnd_import_export.F90
• Add 50km input files and script support. lnd_in is currently hardwired and the buildexe and buildnml are simple scripts NOT leveraging the configure and build-namelist infrastructure.
• Update logz0 coupling
  • Calculate gridcell level momentum roughness length needed for WRF. Merge z0m_actual_patch update from ctsm master, (added to ctsm 7/6/20 from Bill Sacks lilac_cap branch from 1/25/20. Done via "git cherry-pick d1f8a1d31c7ede748"
  • Rename coupling field from z0m_grc to logz0m_grc
  • Convert p2g aggregation from z0m to log(z0m) to improve science consistent with VIC

Contributors other than yourself, if any:

CTSM Issues Fixed (include github issue #):

Are answers expected to change (and if so in what way)?

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

Testing performed, if any: Tested with RASM nna branch revision 2106, nna_03_trunkr2051 Tested on cheyenne Tested with NIR, NFR, RIR, RFR 50km configurations and others

PASS ERS.w5a_a94.X.cheyenne_intel.GC.nnat22 PASS ERS.f45_g37.A.cheyenne_intel.GC.nnat22 PASS ERS.f45_f45.F.cheyenne_intel.GC.nnat22 PASS ERS.f45_g37.BCN.cheyenne_intel.GC.nnat22 PASS ERS.T62_g16.G.cheyenne_intel.GC.nnat22 PASS ERS.T62_g16.GIAF.cheyenne_intel.GC.nnat22 PASS ERS.w5a_w5a.RI.cheyenne_intel.GC.nnat22 PASS ERS.w5a_a94.RIR.cheyenne_intel.GC.nnat22 PASS ERS.w2b_a94.RIRC.cheyenne_intel.GC.nnat22 PASS ERS.w5a_a94.RFR.cheyenne_intel.GC.nnat22 PASS SMS.f19_g17.NI_CLMG.cheyenne_intel.GC.nnat22 PASS ERS.f19_g17.NI_CLMG.cheyenne_intel.GC.nnat22 PASS SMS.w5a_w5a.NI.cheyenne_intel.GC.nnat22 PASS ERS.w5a_w5a.NI.cheyenne_intel.GC.nnat22 PASS SMS.w5a_a94.NIR.cheyenne_intel.GC.nnat22 PASS ERS.w5a_a94.NIR.cheyenne_intel.GC.nnat22 PASS SMS.w5a_a94.NFR.cheyenne_intel.GC.nnat22 PASS ERS.w5a_a94.NFR.cheyenne_intel.GC.nnat22

[apcraig]

There are a lot more changes showing up in the pull request than I expected. I really just moved the bld directory to bld.cime and added some new files to bld. I could try to create a new pull request that more clearly reflected that. My changes are much smaller than this PR suggests. Sorry about that.

[anewman89]

No worries on the number of changes. I wasn't sure what was going on, for a minute I was very impressed with the amount of work needed for the new build. :) I'm fine moving forward with this PR unless we really want to precisely document the actual changes for others.

[anewman89]

I think we could merge this PR now and move the radiation check to an issue.