Jon Wolfe

Testing shows: * new test ERS_Ld5.TL319_oQU240wLI_gis20.MPAS_LISIO_JRA1p5.chrysalis_intel.mpaso-ocn_glc_tf_coupling ran successfully * ERS.ne30_g16_rx1.A.chrysalis_intel showed NML and regular DIFF, as expected * ERP_Ld3.ne30pg2_r05_IcoswISC30E3r5.WCYCL1850.chrysalis_intel.allactive-pioroot1 showed NML DIFF, as expected The last test also reported "BASELINE...

merged to next

@rljacob -- you're right about it being X-cases. The A-case was non-BFB due to the new field but not a baseline DIFF. I changed that in the PR description just...

removed from next -- @rljacob force-pushed next to clear. Re-working to minimize impact on the coupler

@matthewhoffman -- I'm not sure if this is intentional, but testing shows non-BFB behavior when MALI is active. It's apparently due to the change in the default setting for config_front_mass_bal_grounded.

Testing with e3sm_developer showed expected NML DIFFs but also a run failure for: * ERS_Ld5.TL319_oQU240wLI_ais8to30.MPAS_LISIO_JRA1p5.chrysalis_intel.mpaso-ocn_glcshelf

Updated cime_comp_mod.F90 so that ocn_c2_glcshelf and ocn_c2_glctf are set correctly by mpaso. Previously ocn_c2_glcshelf was being overwritten and ocn_c2_glctf was not being retrieved from infodata. Now the test that had...

Re-testing with e3sm_developer on chrysalis after latest commit now shows: * expected NML DIFFs for all tests * expected DIFFs for: ERS.f09_g16_g.MALISIA.chrysalis_intel ERS_Ld5.TL319_oQU240wLI_ais8to30.MPAS_LISIO_JRA1p5.chrysalis_intel.mpaso-ocn_glcshelf

@matthewhoffman -- my last commit changed some settings, but I think to the expected values. However, I would appreciate you making sure before this gets merged

Passes: * PET.f19_g16.X.chrysalis_intel.allactive-mach-pet * SMS_D_Ld1.ne30pg2_r05_IcoswISC30E3r5.WCYCL1850.chrysalis_intel.allactive-wcprod with expected NML DIFFs. Merged to next