specified 'prescribed_aero_file' is not used in the model as given in cam.buildnml.cs

p { margin-bottom: 0.08in; } Dear CESM Team,
in order to prescribed aerosoles in the cam.buildnml.csh I write the following:


prescribed_aero_file = 'aero_1.9x2.5_L26_1960clim_c110503.nc'
prescribed_aero_specifier = 'sulf:SO4', 'bcar1:CB1', 'bcar2:CB2', 'ocar1:OC1', 'ocar2:OC2', 'sslt1:SSLT01', 'sslt2:SSLT02', 'sslt3:SSLT03', 'sslt4:SSLT04', 'dust1:DST01', 'dust2:DST02', 'dust3:DST03', 'dust4:DST04'
prescribed_aero_type = 'CYCLICAL'
prescribed_aero_ymd = 19600101


The file (prescribed_aero_file) exists at the proper location and contains all the needed variables, including the right date. Still the experiment fails with the following error:


aero is prescribed in :aero_1.9x2.5_L26_1960clim_c110503.nc
trcdata_init: data type: CYCLICAL file: aero_1.9x2.5_L26_1960clim_c110503.nc
(GETFIL): attempting to find local file aero_1.9x2.5_L26_1850-2005_c091112.nc
(GETFIL): using /*/inputdata/atm/cam/chem/trop_mozart_aero/aero/aero_1.9x2.5_L26_1850-2005_c091112.nc
open_trc_datafile: /*/inputdata/atm/cam/chem/trop_mozart_aero/aero/aero_1.9x2.5_L26_1850-2005_c091112.nc
open_trc_datafile: cycle year not found : 1960
ENDRUN:open_trc_datafile: cycle year not found


The error is “correct” because the file 'aero_1.9x2.5_L26_1850-2005_c091112.nc' does not contain the year 1960. The problem is that I never specified the file 'aero_1.9x2.5_L26_1850-2005_c091112.nc' anywhere.


It is not in cam.buildnml.csh, cam.input_data_list nor in any other *.csh file. It is also not in exerootdir/$case/run/atm.log.*.


It appears to me that everywhere the right file 'aero_1.9x2.5_L26_1960clim_c110503.nc' is specified, but still the 'aero_1.9x2.5_L26_1850-2005_c091112.nc' is used.


Can anyone tell me why the wrong file is used and how to permanently change the input file?
Thanks
 

eaton

CSEG and Liaisons
If you are trying to do a branch or a restart run from a previous run then you may be running into this problem because the name of the prescribed aero file was written to the restart file and is being read and overwriting the value that you've put in the cam.buildnml.csh file. If that's the case then you'll need to do a "hybrid" run. In the "hybrid" run configuration, CAM is started up like it would be in an initial run, so restart files are not read and the namelist values will not be overwritten.
 
Back
Top