...
If you don't find an answer here, there may be some guidance on the CAM-chem forum, where you can also ask a question: https://bb.cgd.ucar.edu/cesm/forums/cam-chem.154/
(1) Build error - case name
| Code Block | ||
|---|---|---|
| ||
ERROR: No default value found for 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.
| Code Block | ||
|---|---|---|
| ||
ERROR: *buildlib.mct FAILED |
A cat of the mct.bldlog.* will show an error:
| Code Block | ||
|---|---|---|
| ||
ERROR: cat: Filepath: No such file or directory |
- Make sure your call to
--cime-output-root<your_output_path>does not have a slash ("/") at the end of the full path.
(2) Build error - freezing
...
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).
...
c) [Clone only] Make sure initialization files are not defined in the user_nl_cam or user_nl_clm files (i.e. remove those lines if they are there).
...
With a recent update to the MPT system on cheyenne during March 2019, the env_mach_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 cesm.log.XXX file:
| Code Block | ||
|---|---|---|
| ||
MPT ERROR: invalid option -p
(HPE MPT 2.19 12/07/18 05:32:16 |
To correct the error copy the file:
/gpfs/u/home/tilmes/code/cesm2/fix_mpt/env_mach_specific.xml
...
| Code Block | ||
|---|---|---|
| ||
>./case.setup --reset >./case.build --clean >./case.build |
(7) Run error - model crash due to dry deposition
| Code Block | ||
|---|---|---|
| ||
(seq_drydep_read) Read in drydep_inparm namelist from: drv_flds_in ERROR: (seq_drydep_read) ERROR: encountered end-of-file on namelist read |
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
...
To run past 2016 you will need to make sure the correct sea ice specification is called. Edit in env_run.xml:
| Code Block | ||
|---|---|---|
| ||
<entry id="SSTICE_DATA_FILENAME" value="/gpfs/fs1/work/tilmes/inputdata/sst/sst_HadOIBl_bc_0.9x1.25_1850_2018_c170928.nc"> <entry id="SSTICE_YEAR_END" value="2018"> |
...
To use the latest 0.9 x 1.25 SSTICE file, edit env_run.xml:
| Code Block | ||
|---|---|---|
| ||
<entry id="SSTICE_DATA_FILENAME" value="/glade/work/tilmes/inputdata/sst/sst_HadOIBl_bc_0.9x1.25_1850_2020_c200104.nc"> <entry id="SSTICE_YEAR_END" value="2020"> |
...
This error occurs when your env_run.xml file has CONTINUE_RUN="TRUE" with RUN_TYPE="startup" or "hybrid" accidentally.
...
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.
(
...
11) Run error - model crash in "shr_reprosum_calc"
The model crashed with an error in the atm.log.* such as:
| Code Block | ||
|---|---|---|
| ||
Global flash freq (/s), lightning NOx (TgN/y) = 267.0744 13.8985
SHR_REPROSUM_CALC: Input contains 0.96000E+02 NaNs and 0.00000E+00 INFs on process 0
ERROR: shr_reprosum_calc ERROR: NaNs or INFs in input |
Check which meteorology file the the model was most recently using, then perform an ncdump on the U, V and T variables to check whether there are missing values. The meteorology file will likely need to be reprocessed.
(12) 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.
...
| Code Block | ||
|---|---|---|
| ||
ncks --fl_fmt=classic oldfile newfile # netCDF3 classic ncks --fl_fmt=64bit_offset oldfile newfile # netCDF3 64bit-offset ncks --fl_fmt=64bit_data oldfile newfile # netCDF3 64bit-data ncks --fl_fmt=cdf5 oldfile newfile # netCDF3 64bit-data or use nccopy (sometimes this method doesn't work, try "ncks" in that case): nccopy -k cdf5 oldfile newfile |
(13) Output Error: SST gridding inconsistency
Temperature and specific humidity present too low in output, and was tracked to incorrect SST values. The ocean grid definition needs to the the same as the ocean mesh. Specifically, the default data file is 1x1 and grid file is 1x1, but when changing to a different SST file, need to also change the grid file.
| Code Block | ||
|---|---|---|
| ||
for CESM3beta versions:
./xmlchange SSTICE_DATA_FILENAME='/glade/campaign/cgd/cas/asphilli/cam_input_data/sst_COBE-SST2_bc_0.9x1.25_1850_2024_c250627.nc'
./xmlchange SSTICE_YEAR_END=2024
./xmlchange SSTICE_MESH_FILENAME=/glade/campaign/cesm/cesmdata/inputdata/share/meshes/fv0.9x1.25_141008_polemod_ESMFmesh.nc |