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)
- All B_RCP* component sets
- All B_1850-2000* component sets
- All F_AMIP* component sets
- All B_*BPRP* and B_*BDRD* component sets
- All B_1850_*WACCM* component sets
In your $CASEROOT/Buildconf/clm.buildnml.csh (and only there) modify the following line
-glc_nec $GLC_NEC -co2_ppmv $CCSM_CO2_PPMV -co2_type $CLM_CO2_TYPE\old:
-glc_nec $GLC_NEC -co2_ppmv $CCSM_CO2_PPMV \
The entry CICE_NAMELIST_OPTS in the env_run.xml file should have value cam5=.true. in cesm1_1, cesm1_1_1, and cesm1_2 beta01 through beta03. It does not. This results in an incorrect cice albedo setting. The workaround is to run the following command in your case directory:
./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.
BG1850CN at f09 resolution currently has initial conditions that are incompatible with the run configuration, for both CLM and CISM. Thus, this compset-resolution combination should only be used if you provide your own initial conditions for CLM and CISM.
- Download your own copy of CESM1.1 from the CESM website. The location where you download the code is called your $CCSMROOT directory. In what follows $DIN_LOC_ROOT refers your input data directory root.
- Create a new directory $DIN_LOC_ROOT/ocn/iaf.
- Download the interannual data (COREv2) from the GFDL website (http://data1.gfdl.noaa.gov/nomads/forms/mom4/COREv2.html) into $DIN_LOC_ROOT/ocn/iaf. You want to download the "un-Corrected" data. When using the CESM, corrections to the data are made within the data atmosphere, so please be sure to get the uncorrected data. To learn more about this data, see the GFDL website.
- Bug Fix for CESM1_1 - Modify $CCSMROOT/models/ice/dice/bld/namelist_files/namelist_defaults_dice.xml to have the following change:
We would like to bring your attention to a bug in the CESM1.1 release code concerning interannually-forced simulations (GIAF, CIAF, DIAF). The bug is in the runoff data stream definition. All CESM1.1 IAF users need to fix this bug. When creating the new code, the extended runoff data and information were inadvertently overlooked, and thus, the user must make three changes to the namelist_defaults_drof.xml file. This bug will be fixed in future model versions.BUG FIX for CESM1.1:
ALL CESM1.1 IAF USERS MUST MAKE THESE CHANGES. To fix the bug concerning the runoff data, please make the following three changes in $CCSMROOT/models/rof/drof/bld/namelist_files/namelist_defaults_drof.xml within your downloaded source code. You will need to do this before creating any new cases using this code base:
change line 104 from
change line 109 from
change line 111 from
search for the f25_f25 grid and change the value of OCN_GRID to "2.5x3.33". (note the extra 3 on the end).
Again, line 388 of scripts/ccsm_utils/Case.template/config_grid.xml, change
The fix is to change the following line in namelist_defaults_cam.xml
<dust_emis_fact dyn="homme" tms="1" phys="cam5">0.55D0</dust_emis_fact>
Some CAM5 cloud and aerosol processes have not been properly limited to prevent them from operating in the higher levels of WACCM, and this is most likely the source of the crash. This WACCM5 configuration is provided only as a preview of model development, and should not be relied upon for scientific runs.
This will be fixed in the next tag update. To around this problem for some resolutions, the user can set ROF_GRID in env_run.xml to "r05". However, not all CAM resolutions will work with this new setting to ROF_GRID.
This is due to a bug in the dynamics-physics coupling, and is known to affect cases with DEBUG = TRUE. Cases with DEBUG = FALSE may also be affected, but there are no known cases where this has occurred. WACCM-X cases should set NTHRDS_ATM to 1 in this CESM version.
See the bugzilla report for detailed information and a suggested work around.
This is fixed in the CESM 1.2 release. To fix the problem in CESM 1.1 or CESM 1.1.1, copy this version of io_netcdf.F90 into $CASEROOT/SourceMods/src.pop2/
This is fixed in the CESM 1.1.1 release. To fix this problem in the original 1.1 release, copy this version of build-namelist into $CASEROOT/SourceMods/src.pop2/
A fix to the CFC initialization process that went in to 1.1.1 and 1.2.0 only worked for hybrid runs, a second patch was needed to handle branch runs correctly and is included in CESM1.2.1.
The Bugzilla report contains detailed information regarding this bug and the fix.
Machines / scripts
The CESM 1.1 version of Machines did not have the "-fixed" flag in Intel's FIXEDFLAGS, and this prevents COSP from building, as it has some fixed-form source code.
This can be fixed by editing the Macros file for a case. However, this is fixed in CESM 1.1.1, which should be used instead of CESM 1.1 whenever possible anyway.
after several occurrences of the following error message during setup and build:
### Sandy Bridge nodes need mpt 2.06 or later Terminated: Command not found.
The MPI module used by CESM is incompatible with the Sandy Bridge nodes, and so this module has been disabled. You can work around this on a per-case basis by editing env_mach_specific to load the module for a newer version of mpi-sgi, and setting MPI_PATH in Macros to point to the same MPI version.
We have not seen this problem with the 12.4.0 compiler. You can change compiler versions in the env_mach_specific file in your case directory.
This bug also exists in the CESM 1.1.1 release. To fix this problem, copy this version of Makefile into $CASEROOT/Tools/
check_maps/ESMF_RegridWeightGenCheckutility used by the
check_map.shscript 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.shpoint to a directory that does not exist. Replace that script with this version.