This page lists some common problems that users can have in trying to run CAM-chem.
(1) Build error - case name
There are several reasons this may occur:
- Check if you included “--mach cheyenne” option when you created the new case.
- Make sure your
$CASENAMEdoes not have a slash ("/") at the end of the full path.
(1a) Build error - output path name in clone case
The build fails after trying to build mct.
A cat of the mct.bldlog.* will show an error:
- Make sure your call to
<your_output_path>does not have a slash ("/") at the end of the full path.
(2) Build error - freezing
The build will hang on the command:
Cancel the build and try the command
and if the same freeze occurs then the problem is most likely within the namelist definition file (
user_nl_cam). Make sure all the commas and quote marks are there. Sometimes, if the
user_nl_cam file has been opened in Notepad or another text editor, auto-formatting can change the formatting of some symbols, such as quote marks (e.g. Word automatically changes straight quote marks to curly quote marks).
(3) Build error - coupling definition
During the model build the following error occurs:
This occurs when using Python 3 rather than Python 2. Module load python2.7.X and clean build.
(4) Submit error - files missing
Cloning and creating a branch is complete but the following error occurs:
a) Check all your paths for input and emissions definitions (e.g. make sure there a re no missing forward slashes).
b) [Clone only] Check your restart files have been copied to the output run folder, and that they are the same date as the RUN_REFDATE
c) [Clone only] Make sure initialization files are not defined in the
user_nl_clm files (i.e. remove those lines if they are there).
(5) Run error - model crash due to MPT error (not relevant anymore)
With a recent update to the MPT system on cheyenne during March 2019, the
specific.xml file needs to be updated. Otherwise you will be able to submit, but will find the simulation crashes with this error in the
To correct the error copy the file:
to your case directory, then reset and recompile.
(6) Run error - model crash due to dry deposition
This error occurs when you add a gas species and make it to be dry deposited by adding the species name into ‘drydep_list’ in ‘&drydep_inparm’, but you don’t modify seq_drydep_mod.F90. See instructions on https://wiki.ucar.edu/display/camchem/Updating+Gas-Phase+Chemistry
(7) Run error - model crash past 2016
To run past 2016 you will need to make sure the correct sea ice specification is called. Edit in
and of course ensure all your emissions and meteorology files cover the dates you require.
To use the latest 0.9 x 1.25 SSTICE file, edit env_run.xml:
Which repeats 2018 SSTs for 2019 and 2020.
(8) Run error - model crash due to rpointer.drv file check
This error occurs when your env_run.xml file has CONTINUE_RUN="TRUE" with RUN_TYPE="startup" or "hybrid" accidentally.
To correct it, change CONTINUE_RUN variable to "FALSE"
(9) Run error - model crash due to meteorology defintion issues
The model freezes after or during reading in the LBC file. The
atm.log.* file gives an error such as:
Make sure your meteorology nudging style is consistent - i.e. you are calling Specified Dynamics everywhere or Physics-based nudging everywhere. The specific error above occurred when creating a new case with the FCnudged compset, but changing CAM_CONFIG_OPTS=‘-phys cam6 -chem trop_strat_mam4_vbs -age_of_air_trcs -offline_dyn -nlev 32’. Instead, it should be left at: CAM_CONFIG_OPTS: -phys cam6 -chem trop_strat_mam4_vbs -age_of_air_trcs.
(10) NetCDF file version error (as of CESM2.2, may be solved in future versions)
If you provide emissions or any input files in NetCDF version 4 (either NetCDF4 or NetCDF4_classic), the model will crash.
If you are lucky, the model will raise an error something like this on the log file:
However, there is a good chance that you will have no error messages, so just keep in mind this when you provide new NetCDF files to CESM. To determine the versions of your NetCDF files, use ncdump with the option "-k"
Version 3 will be described as "classic". If your files are not version 3, in this case, you have to convert NetCDF4 files to NetCDF3 files using "nccopy" or "ncks" command. Any NetCDF3 file format should work fine (classic, 64bit_offset, 64bit_data, and cdf5), just pick one of these that you would like to use.