SD-WACCM and ESMF

[s_guillas@ucl_ac_uk]

We are trying to build the compset F_SD_WACCM (FSDW), and it requires ESMF; with ESMF 5.2.0p2 I get this error:

/shared/ucl/apps/cesm/cesm1_0_4/models/csm_share/shr/shr_cal_mod.F90(48): error #7002: Error in opening the compiled module file
. Check INCLUDE paths. [ESMF_MOD]
use esmf_mod
-------^
/shared/ucl/apps/cesm/cesm1_0_4/models/csm_share/shr/shr_cal_mod.F90(194): error #6457: This derived type name has not been declared. [ESMF_TIME]
type(ESMF_time) :: ltime1,ltime2
--------^
/shared/ucl/apps/cesm/cesm1_0_4/models/csm_share/shr/shr_cal_mod.F90(253): error #6457: This derived type name has not been declared. [ESMF_TIME]
type(ESMF_time) :: ltime1,ltime2
--------^
/shared/ucl/apps/cesm/cesm1_0_4/models/csm_share/shr/shr_cal_mod.F90(393): error #6457: This derived type name has not been declared. [ESMF_TIME]
type(ESMF_Time) :: ltime
--------^
... (more cut)

while building csm_share.

Looking in the modules directory for ESMF, there is no esmf_mod.mod, only an esmf.mod.
(esmf_mod is part of version 3.x of ESMF.)

 

[santos]

Francis Vitt has mentioned that you can work around the ESMF requirement by using the NOLEAP calendar rather than Gregorian, while using solar_parms datasets without leap days in them. (There's a related known issue mentioned here: http://www.cesm.ucar.edu/models/cesm1.0/tags/cesm1_0_4/minor3.html )

Failing that, your best bet may be to fall back to a previous ESMF version. This will be fixed in 1.1, because CESM no longer depends on an external ESMF.