CLM6_cesm30alpha08c_ne30pg3_CPLHIST_1850

[olyson]

Description:
Coupler history case to verify coupler history mode is still working correctly.
./create_newcase --case CLM6_cesm30alpha08c_ne30pg3_CPLHIST_1850 --compset 1850_DATM%CPLHIST_CLM60%BGC-CROP_SICE_SOCN_MOSART_SGLC_SWAV --res ne30pg3_ne30pg3_mg17 --project P93300041 --run-unsupported

---

Case directory:
Locally:
/glade/work/oleson/cesm3_0_alpha08c/cime/scripts/CLM6_cesm30alpha08c_ne30pg3_CPLHIST_1850

---

Sandbox:
Locally:
/glade/work/oleson/cesm3_0_alpha08c

---

user_nl_ changes:
user_nl_clm changes

hist_fincl1 = 'FSDSND','FSDSVD','FSDSNI','FSDSVI','RAIN_FROM_ATM','SNOW_FROM_ATM','FLDS_NOT_DOWNSCALED','ZBOT','Tair_from_atm','Thair_from_atm','QBOT_NOT_DOWNSCALED','PBOT_NOT_DOWNSCALED','Rho_from_atm','PCO2','UWIND','VWIND','BCPHIDRY','BCPHODRY','BCPHIWET','OCPHIDRY','OCPHODRY','OCPHIWET','DSTWET1','DSTDRY1','DSTWET2','DSTDRY2','DSTWET3','DSTDRY3','DSTWET4','DSTDRY4','ATM_TOPO'

user_nl_datm changes

flds_co2 = .true.

xml changes

./xmlchange DATM_CPLHIST_DIR=/glade/derecho/scratch/oleson/archive/CAM7CLM6_cesm30alpha08c_ne30pg3_1850/cpl/hist
./xmlchange DATM_CPLHIST_CASE=CAM7CLM6_cesm30alpha08c_ne30pg3_1850
./xmlchange DATM_YR_END=3
./xmlchange RUN_STARTDATE=0001-01-01
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=3
./xmlchange DATM_PRESNDEP=none
./xmlchange CCSM_BGC=CO2A
./xmlchange CLM_CO2_TYPE=diagnostic

---

SourceMods:
None

---

Diagnostics:
Diags (if available)

https://webext.cgd.ucar.edu/I1850/$CASE/lnd/

---

Output:
Output (if still available):
/glade/derecho/scratch/oleson/archive/CLM6_cesm30alpha08c_ne30pg3_CPLHIST_1850/

---

Contacts:
@olyson

---

Extra details:

[olyson]

@wwieder , these CPLHIST runs are complete. Can you compare this CPLHIST-driven run (/glade/derecho/scratch/oleson/archive/CLM6_cesm30alpha08c_ne30pg3_CPLHIST_1850/lnd/hist) with the CAMCLM run (#138 /glade/derecho/scratch/oleson/archive/CAM7CLM6_cesm30alpha08c_ne30pg3_1850) that produced the CPLHIST files? The forcing fields we are interested in are listed in this ADF issue: NCAR/ADF#436.
Not sure how easy it is to tweak min/max values on the contour plots, but the differences should be quite small. Here is an example of a past comparison for FLDS_NOT_DOWNSCALED:

https://webext.cgd.ucar.edu/F1850/ctsm51_cesm23a12c_ne30pg3g17_CPLHIST_1850_offsetm900_iradswm1_nextswday_sadens/lnd/ctsm51_cesm23a12c_ne30pg3g17_CPLHIST_1850.2_3-cam6ctsm51_cesm23a12c_ne30pg3g17_CPLHIST_1850.2_3/set2/set2_ANN_FLDS_NOT_DOWNSCALED.png

This can wait until next week when I'm back in the office.

[olyson]

I would do years 2-3 for climatology and years 1-3 for timeseries.

[wwieder]

Color pars on difference plots may need attention, but a spot check of a few variables looks encouraging. @olyson and @slevis-lmwg , please have a look

[olyson]

Thanks @wwieder ! This is looking promising. A few notes:

1. I do see a difference in Rho_from_atm in the timeseries plot, that I would expect after realizing that this issue in CTSM and CMEPS has not been resolved:

ESCOMP/CTSM#1982
ESCOMP/CMEPS#354

It was indicated in April 2023 that this was being deferred, maybe because differences are so small and it's not worth the work to fix this...

2. The units for Rho_from_atm in the timeseries plot are interesting. Does the "+1.139" mean that value should be added to the y-axis? I don't think there is a problem with the history files since the values appear normal in the contour plots.
3. Maybe it's not worth it to adjust the contour intervals, but can the min/max values on the difference plot be changed, perhaps to exponential notation? That way we can compare order of magnitude differences more readily to the previous coupler history validation.
4. DSTWET4 and DSTDRY4 were zero in CESM2, but I see values in the contour and timeseries plots. Presumably there has been some change to the aerosol model...

[wwieder]

Thanks for looking into this @olyson. A few thoughts

The units for Rho_from_atm in the timeseries plot are interesting. Does the "+1.139" mean that value should be added to the y-axis? I don't think there is a problem with the history files since the values appear normal in the contour plots.

I think that's what it's saying as the table lists for the global values of each case

Rho_from_atm | kg/m^3 | 1.139 | 1.14

min/max values on the difference plot be changed, perhaps to exponential notation?

Good idea, but I'm not sure how to do this in LDF, as controls over color bar ranges come in through a yaml file that I've been struggling with...

DSTWET4 and DSTDRY4

Good catch, I'll ask the chemists.

[ekluzek]

I'm really glad we've done this so we can feel confident that we'll be able to do this in a few weeks when we need to do it for real. So thanks for working on this @olyson

The only thing missing is ndep, but the forcing dataset would've needed to have it added.

Note on additional settings:

These need to be set to point to the forcing data:

    DATM_CPLHIST_CASE: CAM7CLM6_cesm30alpha08c_ne30pg3_1850
    DATM_CPLHIST_DIR: /glade/derecho/scratch/oleson/archive/CAM7CLM6_cesm30alpha08c_ne30pg3_1850/cpl/hist

For this case you could set these to "none":
DATM_PRESO3 (since Ozone isn't be used in CTSM)
DATM_TOPO (since CISM isn't active in the forcing case)

But, it doesn't hurt anything to have them on. And you would need DATM_TOPO for a case with CISM.

[olyson]

I'm really glad we've done this so we can feel confident that we'll be able to do this in a few weeks when we need to do it for real. So thanks for working on this @olyson

The only thing missing is ndep, but the forcing dataset would've needed to have it added.

Right, the PR for that was/is still outstanding. Plus, this issue needs to be taken care so that the data can be read in: ESCOMP/CDEPS#230, unless I'm misunderstanding something about ndep.

Note on additional settings:

These need to be set to point to the forcing data:

    DATM_CPLHIST_CASE: CAM7CLM6_cesm30alpha08c_ne30pg3_1850
    DATM_CPLHIST_DIR: /glade/derecho/scratch/oleson/archive/CAM7CLM6_cesm30alpha08c_ne30pg3_1850/cpl/hist

Right, I did make those changes, but forgot to document them above. I'll do that.

For this case you could set these to "none": DATM_PRESO3 (since Ozone isn't be used in CTSM) DATM_TOPO (since CISM isn't active in the forcing case)

But, it doesn't hurt anything to have them on. And you would need DATM_TOPO for a case with CISM.

Noted.

[ekluzek]

I'm really glad we've done this so we can feel confident that we'll be able to do this in a few weeks when we need to do it for real. So thanks for working on this @olyson
The only thing missing is ndep, but the forcing dataset would've needed to have it added.

Right, the PR for that was/is still outstanding. Plus, this issue needs to be taken care so that the data can be read in: ESCOMP/CDEPS#230, unless I'm misunderstanding something about ndep.

Yes, good point and you are correct. We need both of them taken care of to make it easy to do out of the box.