Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update info about sathist_mfilt

The history files (those that contain model output) can be defined in the user_nl_cam file under the finclX namelist variable, where X may be 1, 2, 3 etc. up to 9. Each 'finclX' will tell the model to write a new file that includes the specified variables. Recommended procedure is to keep fincl1 as the default, because this tells the model to write out month average values of all species that are needed for the automated diagnostics. Therefore, best practice is to write your own history files beginning with fincl2 onwards. 

More information is available in the CAM documentation.

Example:

Section


Column
width80%60%


Adding the following species to user_nl_cam will write out files with a h1 suffix.

Code Block
languagetext
&cam_history_nl
fincl2              = 'PS','OH','H2O','H2O2','HO2','O3','NO3','NO','NO2','CO','ISOP','PHIS','CH2O','T','PAN','PM25','PDELDRY','AODDUST','AODVISdn','Z3'

Adding the following species to user_nl_cam will write out files with a h1 suffix.

The temporal resolution of the output files is also specified via the user_nl_cam:

Code Block
languagetext
avgflag_pertape     = 'A','A'
mfilt               = 1,4
nhtfrq              = 0,-6
/



Column
width20%40%


Tip
titleTip for New Users:

A list of all possible history file variables can be found here: https://www.cesm.ucar.edu/models/cesm2/atmosphere/docs/ug6/hist_flds_fv_cam4_waccm.htmlCAM-chem History Fields

You can find the possible history fields for your own model build by looking in a log file for your setup simulation and searching for "MASTER FIELD LIST".



Where columns correspond to finclX in order. The namelist variables define:

...

It is possible to save output along a time-varying track to match aircraft or satellite observations using the 'sathist' namelist variables.  The user must create a netcdf file with the time, latitude and longitude of the desired track and the model profile is saved for the closest locations for the closest timestep(s).  If sathistIf sathist_ntimestep and sathistand sathist_nclosest are set to 1 only the closest profile in time and space will be saved.  If values greater than 1 are used, the user can interpolate the output to the actual observation location.  As many variables as desired can be specified in the 'fincl'; when the file gets too largeto the value specified in 'sathist_mfilt', a new file will be automatically started.  NOTE: the aircraft output file is NOT automatically copied to your 'archive' directory at the completion of the run. 

Code Block
languagetext
 sathist_track_infile = '/glade/p/acom/MUSICA/flight_tracks/aircraft_profilelist_20180724_20190905_wecan-firexaq_togamrg_c20210316.nc'
 sathist_ntimestep = 2
 sathist_nclosest = 4
 sathist_mfilt = 100000
 sathist_hfilename_spec = '%c.cam.aircraft_togamrg_4closest2tstep.%y-%m-%d-%s.nc'
 sathist_fincl = 'PS', 'PMID', 'Z3', 'M_dens', 'T', 'U', 'V', 'Q', 'H2O', 'RELHUM', 
                 'O3', 'O3S', 'NO', 'NO2', 'CO', 'O3_Prod','O3_Loss'

...

Code Block
languagetext
avgflag_pertape     = 'L','L'
mfilt               = 12, 30
nhtfrq              = 0, -24
lcltod_start        = 36800, 47600
lcltod_stop         = 38800, 49600


Saving IC files

You can save Initial Conditions (IC) files at any frequency for use in new cases.  The default is 'YEARLY'. Other choices include: '6-HOURLY', 'DAILY', 'MONTHLY', 'ENDOFRUN'.

Code Block
languagetext
inithist = 'MONTHLY'