Welcome to the new DiscussCESM forum!
We are still working on the website migration, so you may experience downtime during this process.

Existing users, please reset your password before logging in here: https://xenforo.cgd.ucar.edu/cesm/index.php?lost-password/

trop_mozart_aero/emis inputdata error in CESM2.1.3 (CAM5) - F1850


Nicolas Cosentino
New Member
Hi! My objective is to run an F1850 simulation in CESM2.1.3 with CAM5 and an f09_g17 resolution, for which I configure CAM_CONFIG_OPTS='-phys cam5'. I get the following run error upon submission: inputdata/atm/cam/chem/trop_mozart_aero/emis/aerocom_mam3_dms_surf_2000_c120315.nc - cycle year not found: 1850. I found a suggestion to solve this issue in the last entry of this thread. However, that was suggested for a CAM6 run and I think it may not apply to my case, given that I do not see any fincl tag in .../model/components/cam/bld/namelist_files/use_cases/1850-2005_cam5.xml. I wonder if it is a problem of needing another .nc file given the mismatch in year, or if it has to do with the fact that this .nc file has a coarser resolution (2.5º-1.9º) than my simulation's resolution. I would appreciate any ideas on what may be the issue here!


Jesse Nusbaumer
CSEG and Liaisons
Staff member
Hi Nicolas,

Thanks for contacting me! I believe the error you are running into is due to the default aerosol files being for year 2000 conditions (hence "2000" in the file name), instead of year 1850 conditions, which is what your case is setup for. After digging around I found what I believe are the equivalent files for year 1850 conditions, although these may not be the most up-to-date versions (hopefully another forum user can correct me if that is the case).

In order to use these files, add the following lines to your user_nl_cam file:

 ext_frc_specifier              = 'SO2         -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so2_elev_1850_c090726.nc',
         'bc_a1       -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_bc_elev_1850_c090726.nc',
         'num_a1      -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_num_a1_elev_1850_c090726.nc',
         'num_a2      -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_num_a2_elev_1850_c090726.nc',
         'pom_a1      -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so4_a1_elev_1850_c090726.nc',
         'so4_a1      -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so4_a1_elev_1850_c090726.nc',
         'so4_a2      -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so4_a2_elev_1850_c090726.nc'
 srf_emis_specifier             = 'DMS       -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/aerocom_mam3_dms_surf_1849-2100_c140822.nc',
         'SO2       -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so2_surf_1850_c090726.nc',
         'SOAG      -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_soag_1.5_surf_1850_c130423.nc',
         'bc_a1     -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_bc_surf_1850_c090726.nc',
         'num_a1    -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_num_a1_surf_1850_c090726.nc',
         'num_a2    -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_num_a2_surf_1850_c090726.nc',
         'pom_a1    -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_pom_surf_1850_c130423.nc',
         'so4_a1    -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so4_a1_surf_1850_c090726.nc',
         'so4_a2    -> /glade/p/cesmdata/cseg/inputdata/atm/cam/chem/trop_mozart_aero/emis/ar5_mam3_so4_a2_surf_1850_c090726.nc'

Please note that the paths used /glade/p/cesmdata/cseg/inputdata/atm/cam/XXX are specific to NCAR's Cheyenne supercomputer. If you are running on a different machine then you should find the equivalent paths by looking for these entries in the atm_in file, which should be present in your run directory. Please note too that the files may need to be downloaded using the check_input_data script, which should be present in your case directory.

Finally, if another forum member recommends a better set of files then you will just need to change the file names in the user_nl_cam namelist block shown above in order to use them.

Anyways, I hope that helps, and good luck with your simulation!