Known Problems in CESM1.1
The purpose of the CESM1.1.0 (CESM1.1) release is to make available to the CESM user community model functionality and infrastructure improvements. It is to be used as a code base for new model developments that require this new infrastructure. This release contains no scientifically validated (i.e. supported) component sets. As such, it is not to be used for scientific simulations.
Component Sets (COMPSETS)
-glc_nec $GLC_NEC -co2_ppmv $CCSM_CO2_PPMV -co2_type $CLM_CO2_TYPE\old:
-glc_nec $GLC_NEC -co2_ppmv $CCSM_CO2_PPMV \
./xmlchange -file env_run.xml -id CICE_NAMELIST_OPTS -val "cam5=.true."
This problem also pertains to release CESM1.1.1, and development tags cesm1_2_beta01 and cesm1_2_beta02 and cesm1_2_beta03.
atmosphere/CAM
atmosphere/WACCM
land/CLM
ocean/POP2
ice/CICE
land-ice/CISM
Machines / scripts
mapping/
check_maps/ESMF_RegridWeightGenCheck
utility used by the check_map.sh
script assume you are building on bluefire, not yellowstone. On yellowstone, the needed environment variable ($ESMFMKFILE) is set automatically when you load the proper ESMF module. For example, run
$ module load esmf $ module load esmf-6.1.1-ncdfio-uni-ONote that this requires the intel module to be loaded already, and will build the executable using the serial (intel) compiler so you can run the utility from the yellowstone login node.
gen_mapping_files/gen_ESMF_mapping_file/create_ESMF_map.sh
point to a directory that does not exist. Replace that script with this version.