Error reading namelist when using WACCM in GHG mode

[swahl@geomar_de]

Dear all

Currently we get the following error when using WACCM in GHG mode

ERROR: chem_readnl: ERROR reading namelist

Our setup procedure is as follows:
./create_newcase -case CaseName -compset F55WCN ...
./cesm_setup
./xmlchange CAM_CONFIG_OPTS="-phys cam4 -chem waccm_ghg -nlev 66"
./CaseName.build

We are using CESM 1.2.0 on an IBM power6 (blizzard @ DKRZ Hamburg)

Do you have any idea why the generated namelist (see attachment) cannot be read (no user modifications are applied to the chemistry related namelists) ?
Thanks for your support.

Sebastian

 

[santos]

A namelist read error is often the result of having an "extra" variable in the namelist that's not recognized by the code. In your case, I believe that the spe file is the problem, since waccm_ghg (i.e. specified chemistry)  cases don't use the solar proton code. The reason that the namelist is inconsistent with the code is that you have changed the chemistry package, but you have not changed CAM_USE_CASE to match.My recommendation is the following:

1. Switch to CESM 1.2.2, since there are new compsets, use_cases, and bug fixes for specified chemistry cases in that version.
2. Use the new B55TRWSCCN compset for any 1955 transient coupled runs (this is the only specified chemistry case we support for this time period). For cases with data ocean, we don't support any compsets, but you can try doing what you've already tried, except also change the use_case to waccm_sc_1955-2005_cam4. This should give you a namelist that's appropriate for a 1955 SC-WACCM (GHG) case.

 

 

[swahl@geomar_de]

Deer Seanthanks for your support. I followed your suggestions (using CESM 1.2.2 instead of 1.2.0 etc). However when I try to run the B55TRWSCCN compset I do get an error reading the greenhouse gas loss rate file (last lines of the atm.log... file)chemini: after waccm_prate_inti on node  0
 -----------------------------------------
 mozart will NOT do nh4no3
 following species are missing
 1
 2
 3
 4
 5
 -----------------------------------------
 sox_inti: has_sox =  F
 chemini: after aurora_inti
 chemini: after wetdep_init
 chemini: finished on node  0
 boundarydata_read: Reading from: /work/bb0519/CESM/cesm1_2_2/inputdata/atm/cam/ggas/noaamisc.r8.nc
 (GETFIL): attempting to find local file noaamisc.r8.nc
 (GETFIL): using /work/bb0519/CESM/cesm1_2_2/inputdata/atm/cam/ggas/noaamisc.r8.nc
(shr_sys_abort) ERROR: Did not recognize a vertical coordinate variable
(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping

Looking at the source code (boundarydata.F90 app line 340) I see that the routine expects some kind of vertical coordinate information to be present in the file (PS, hyabi) which the file noaamisc.r8.nc doesn't have. I did check the inputdata server already whether there is a more recent version of this file. Tracking the error backwards I see that this only occurs if waccm_ghg is set. It therefore occurs in coupled and uncoupled mode. Do you have a suggestion what I have do to do get the WACCM_SC version going. Attached you'll find the atm_in namelist generated by the set up procedure. Nothing has been changed from the defaults.Thanks a lot for your help
Sebastian 

 

[santos]

I encountered this error earlier this week, and to be honest, I find it very confusing. It only occurs for me on the XLF compiler, and even then only when DEBUG is on. Are you running with those conditions? I need to take a closer look; it's not obvious to me why the compiler settings should trigger this error.

 

[santos]

I've tracked this down to a bug in the boundarydata module. Please see this notice.