In a fairly recent CAM run intended to generate coupler history forcing to force CTSM:
/glade/campaign/cesm/cesmdata/cseg/runs/cesm2_0/f.cam6_3_112.FLT1850.ne30.landspinup.001
which has a compset of:
1850_CAM%DEV%LT%GHGMAM4_CLM51%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV_SESP
the atmImp_Faxa_dstwet4 and atmImp_Faxa_dstdry4 fields in the *.cpl.hx.atm.24h.avrg.* have zero values.
I believe this is consistent with CESM2 results.
However, I see that in more recent versions of the model, these fields are non-zero.
E.g., I created a case with coupler history output using cesm3_0_alpha08c with this compset:
1850_CAM70%LT_CLM60%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_DGLC%NOEVOLVE_SWAV_SESP
and the coupler history fields generated for these dust bins, atmImp_Faxa_dstwet4 and atmImp_Faxa_dstdry4, are non-zero.
I'm curious to know if this is expected? Is this due to recent changes in CAM aerosols?
Thanks for any input!
/glade/campaign/cesm/cesmdata/cseg/runs/cesm2_0/f.cam6_3_112.FLT1850.ne30.landspinup.001
which has a compset of:
1850_CAM%DEV%LT%GHGMAM4_CLM51%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV_SESP
the atmImp_Faxa_dstwet4 and atmImp_Faxa_dstdry4 fields in the *.cpl.hx.atm.24h.avrg.* have zero values.
I believe this is consistent with CESM2 results.
However, I see that in more recent versions of the model, these fields are non-zero.
E.g., I created a case with coupler history output using cesm3_0_alpha08c with this compset:
1850_CAM70%LT_CLM60%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_DGLC%NOEVOLVE_SWAV_SESP
and the coupler history fields generated for these dust bins, atmImp_Faxa_dstwet4 and atmImp_Faxa_dstdry4, are non-zero.
I'm curious to know if this is expected? Is this due to recent changes in CAM aerosols?
Thanks for any input!