...
Example:
Section |
---|
Column |
---|
|
Code Block |
---|
| &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 |
---|
| avgflag_pertape = 'A','A'
mfilt = 1,4
nhtfrq = 0,-6
/ |
|
Column |
---|
|
Tip |
---|
| A list of possible history file variables can be found here:CAM-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". |
|
|
...
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 |
---|
|
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' |
...