You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compiling CTSM with LILAC on a HPC other than Cheyenne, e.g. in Norway, the following error occurs: ERROR: ESMFMKFILE not found None
General bug information
CTSM version you are using: ctsm5.1.dev054
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: [?]
Details of bug
The offending line is found in WRF-CTSM/CTSM/components/cmeps/cime_config/buildnml.
There, the ESMF software version is checked by looking at the value of the environment variable ESMFMKFILE.
This variable is not set automatically when loading the ESMF module on the Norwegian cluster. ESMF_LIBDIR was set correctly in the corresponding config_compiler.xml created for the machine, e.g. <ESMF_LIBDIR>$(EBROOTESMF)/lib</ESMF_LIBDIR>. EBROOTESMF points to the installation directory of ESMF on that machine.
Workaround: Set ESMFMKFILE by hand before compiling.
Probable solution: The check in WRF-CTSM/CTSM/components/cmeps/cime_config/buildnml should instead check for ESMF_LIBDIR set in the config_compilers.xml.
The text was updated successfully, but these errors were encountered:
ESMF_LIBDIR is deprecated; the preferred method for specifying the path
to ESMF is now to use ESMFMKFILE. And the latter is needed for a check
in the CMEPS buildnml; see also
ESCOMP#1498
Brief summary of bug
When compiling CTSM with LILAC on a HPC other than Cheyenne, e.g. in Norway, the following error occurs:
ERROR: ESMFMKFILE not found None
General bug information
CTSM version you are using: ctsm5.1.dev054
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: [?]
Details of bug
The offending line is found in
WRF-CTSM/CTSM/components/cmeps/cime_config/buildnml
.There, the ESMF software version is checked by looking at the value of the environment variable
ESMFMKFILE
.This variable is not set automatically when loading the ESMF module on the Norwegian cluster.
ESMF_LIBDIR
was set correctly in the correspondingconfig_compiler.xml
created for the machine, e.g.<ESMF_LIBDIR>$(EBROOTESMF)/lib</ESMF_LIBDIR>
.EBROOTESMF
points to the installation directory of ESMF on that machine.Workaround: Set
ESMFMKFILE
by hand before compiling.Probable solution: The check in
WRF-CTSM/CTSM/components/cmeps/cime_config/buildnml
should instead check forESMF_LIBDIR
set in theconfig_compilers.xml
.The text was updated successfully, but these errors were encountered: