GEOS-Chem v10-01 Online User's Guide
Previous | Next | Printable View (no frames)
5. Run Directories
This chapter describes the contents of GEOS-Chem run directories. Each run directory is customized for a unique combination of simulation, horizontal resolution, and met field type, and contains the various input files with which you select options for your GEOS-Chem simulation. For information on simulation, met field, and horizontal resolution options available, please see Appendix 1, Appendix 2, and Appendix 4, respectively.
Several run directories are available for download via Git. Please see Chapter 2.3 for instructions on how to download run directories. We recommend that you create a different run directory for each of your GEOS-Chem simulations to avoid overwriting output with subsequent model runs.
Note that run directories compatible with previous versions of GEOS-Chem will not work with v10-01.
Below is a table listing GEOS-Chem input files that reside in the run directory.
GEOS-Chem user input files | |
---|---|
input.geos |
File containing all GEOS-Chem user options. In this file, you may specify the following options:
|
HEMCO_Config.rc | Specifies emission inventories that you want to include in GEOS-Chem via HEMCO. |
Planeflight.dat | Specifies flight tracks for which you want to save out specific tracers, chemical species, or met field quantities. |
GEOS-Chem chemistry mechanism files | |
chemga.dat | File containing some aerosol parameters for SMVGEAR II or KPP. |
globchem.dat |
File that defines the GEOS-Chem NOx-Ox-hydrocarbon-aerosol chemical mechanism. This file contains the list of chemical species and reactions used by the chemical solver (SMVGEAR II or KPP). At present, you may pick from a few different chemistry mechanisms:
|
mglob.dat |
Setup file for SMVGEAR II, containing convergence criteria and other parameters. |
GEOS-Chem photolysis mechanism files | |
FJX_spec.dat |
Contains cross-section and quantum yields for FAST-JX photolysis species. |
FJX_j2j.dat |
Links "GEOS-Chem species" to "FAST-JX" species. FAST-JX photolysis species are defined in the data file FJX_spec.dat, GEOS-Chem species in globchem.dat. |
jv_spec_mie.dat | Contains aerosol optical properties at 5 wavelengths. |
dust.dat | Contains aerosol optical properties for dust at multiple wavelengths for use in Fast-JX and the RRTMG radiatiaive transfer model (if enabled). |
org.dat | Contains aerosol optical properties for organic carbon at multiple wavelengths for use in Fast-JX and the RRTMG radiatiaive transfer model (if enabled). |
so4.dat | Contains aerosol optical properties for sulfate at multiple wavelengths for use in Fast-JX and the RRTMG radiatiaive transfer model (if enabled). |
soot.dat | Contains aerosol optical properties for black carbon at multiple wavelengths for use in Fast-JX and the RRTMG radiatiaive transfer model (if enabled). |
ssa.dat | Contains aerosol optical properties for accumulation mode sea salt aerosol at multiple wavelengths for use in Fast-JX and the RRTMG radiatiaive transfer model (if enabled). |
ssc.dat | Contains aerosol optical properties for coarse mode sea salt aerosol at multiple wavelengths for use in Fast-JX and the RRTMG radiatiaive transfer model (if enabled). |
NOTE: GEOS-Chem v10-01 uses the Fast-JX v7.0 photolysis mechanism, while GEOS-Chem v9-02 and earlier versions used the older FAST-J photolysis mechanism with updated cross-section inputs from FAST-JX v6.2.
Details about each input file listed above are described in subsequent sections of this chapter. For convenience, here are quick links to additional information per file or group of files that appear later in this chapter:
The input configuration file input.geos organized configuration information into menus. Quick links to details about individual menus in this chapter are as follows:
5.2 GEOS-Chem user input files
You must modify these files to customize your GEOS-Chem simulation. These files contain definitions of tracers, starting and ending times, diagnostics, and other relevant quantities. You should make it a habit of thoroughly checking these files before submitting a long GEOS-Chem run.
GEOS-Chem combines all the input options and switches into a single input file, input.geos. All user-defined input switches and settings which customize GEOS-Chem output options are now defined within this file.
An input.geos file ships with each GEOS-Chem run directory. We invite you to create the run directory for the simulation(s) that you are interested in and view the corresponding input.geos file.
Note that the input.geos file is grouped into menus. Each menu controls the options for a particular aspect of a GEOS-Chem simulation. Here is a list of menus and the options which they control. You can click on the name of a menu for more information.
Simulation Menus | |
---|---|
Specifies the start & stop times of the run, the restart file names, and the directory path information |
|
Specifies information about each tracer, including name, molecular weight, and, for family tracers, individual constituent species |
|
Operations Menus | |
Specifies options for TPCORE transport |
|
Specifies options for cloud convection and PBL mixing |
|
Specifies options for emissions and boundary conditions NOTE: This menu is now mostly obsolete because of HEMCO. We now use the HEMCO_Config.rc file to set the emission inventories. |
|
Future Menu |
Specifies options for future emissions scenarios for GCAP simulations NOTE: This menu is now mostly obsolete because of HEMCO. We now use the HEMCO_Config.rc file to set the emission inventories. |
Specifies options for emissions and chemistry of sulfate, carbon, secondary organic, dust, and sea salt aerosols |
|
Specifies options for both dry deposition and wet deposition. |
|
Specifies options for chemistry |
|
Specifies options for radiation |
|
CO2 Menu | Specifies options for the CO2 simulation |
Mercury Menu |
Specifies options for the mercury simulation, with or without the Global Terrestrial Mercury Model |
CH4 Menu |
Specifies options for the methane simulation |
POPs Menu |
Specifies options for the persistent organic pollutants (POPs) simulation |
Diagnostic Menus | |
Specifies dates on which diagnostic output will be saved to the binary punch file |
|
GAMAP Menu | Specifies the path names for the GAMAP diaginfo.dat and tracerinfo.dat files, both of which are now written by GEOS-Chem |
Specifies which binary punch file diagnostics to turn on, and which tracers to save to disk |
|
Specifies the names of the files for the ND40 plane flight diagnostic |
|
Specifies options for the ND48 station timeseries diagnostic |
|
Specifies options for the ND49 instantaneous timeseries diagnostic |
|
Specifies options for the ND50 24-hour average timeseries diagnostic |
|
Specifies options for the ND51 "satellite" timeseries diagnostic |
|
ND51b Menu | Specifies options for the ND51b "satellite" timeseries diagnostic. |
ND63 Menu | Specifies options for the ND63 ship timeseries diagnostic |
Specifies options for the ND65 (chemical prod & loss) and ND20 (save PO3, LO3 to disk for tagged Ox simulation) diagnostics |
|
Specifies options for the benchmark diagnostic |
|
Other Menus | |
Specifies options for the nested grid simulations |
|
Specifies Unix commands which are used for unzipping data on the fly |
The menus must occur in this order:
For each of the menus in input.geos, we shall describe the options and switches that you must set in order to perform a NOx-Ox-Hydrocarbon-aerosol simulation with the UCX chemistry mechanism (a.k.a. "UCX simulation"). Menus that are optional shall be noted as such.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% SIMULATION MENU %%% : 02: Start YYYYMMDD, HHMMSS : 20130701 000000 03: End YYYYMMDD, HHMMSS : 20130801 000000 04: Run directory : ./ 05: Input restart file : initial_trac_rst.geosfp_4x5_fullchem 06: Make new restart file? : T 07: Output restart file(s) : trac_rst.geosfp_4x5_fullchem.YYYYMMDDhhmm 08: Root data directory : /as/data/geos/ExtData 09: => GCAP subdir : AGRID/YYYY/MM/ 10: => GEOS-4 subdir : GEOS_4_v4/YYYY/MM/ 11: => GEOS-5 subdir : GEOS_5/YYYY/MM/ 12: => GEOS-FP subdir : GEOS_FP/YYYY/MM/ 13: => MERRA subdir : MERRA/YYYY/MM/ 14: Dir w/ 1x1 emissions etc: /as/data/geos/ExtData/GEOS_NATIVE/ 15: Temporary directory : ./ 16: Unzip met fields? : F 17: Wait for met fields? : F 18: Use variable tropopause?: T 19: Global offsets I0, J0 : 0 0
Line | Description |
---|---|
1 |
Header line |
2 |
Specify the starting date and time of the GEOS-Chem simulation. The date must be in YYYYMMDD format (4-digit year, month, and day). The time must be in hhmmss format (hour, minute, and seconds). Note that since the GEOS-Chem dynamic timestep (see Transport Menu) is usually 10, 15, or 30 minutes, you can always set the seconds to zero. |
3 |
Specify the ending date (YYYYMMDD format) and time (hhmmss format) of the GEOS-Chem simulation. |
4 |
Specify the name of the GEOS-Chem run directory (e.g. where the executable file and input files reside). |
5 |
Specify the name of the restart file, which contains the instantaneous concentrations of the transported tracers specified in the Tracer Menu. This file is used to initialize tracer concentrations at the start of your simulation. You can change the name of the restart file to match the file that you have. If you just specify the file name, GEOS-Chem will look for the restart file in the run directory. You may also specify an entire directory path. Also, you may include the following tokens in the file name:
NOTE: Using YYYYMMDDhhmm in the restart file names allow for test simulations of less than one hour to be performed. |
6 |
If you want to create new restart files then set this to T. A new restart file will be saved at the same time when diagnostics are saved to the binary punch file. See Output Menu for more information. |
7 |
Specify the name or file path for the output restart file(s). As described above, GEOS-Chem will replace the YYYY, MM, DD, hh, mm, ss tokens in the file name with the appropriate date or time values. |
8 |
Specify DATA_DIR (stored in Input_Opt%DATA_DIR). DATA_DIR is the root-level data directory path. The various shared data inputs (e.g. emissions, offline OH, offline dust & aerosol concentrations, etc). are stored in subdirectories of DATA_DIR. The met fields are also stored in subdirectories of DATA_DIR. For more information, please see our Setting up the ExtData directory wiki page. |
9 |
Specify the directory path where GCAP met fields are stored. You may include the YYYY and MM tokens as described above. This is stored in the variable Input_Opt%GCAP_DIR. |
10 |
Specify the directory path where GEOS-4 met fields are stored. You may include the YYYY and MM tokens as described above. This is stored in the variable Input_Opt%GEOS_4_DIR. |
11 |
Specify the directory path where GEOS-5 met fields are stored. You may include the YYYY and MM tokens as described above. This is stored in the variable Input_Opt%GEOS_5_DIR. |
12 |
Specify the directory path where GEOS-FP met fields are stored. You may include the YYYY and MM tokens as described above. This is stored in the variable Input_Opt%GEOS_FP_DIR. |
13 | Specify the directory path where MERRA met fields are stored. You may include the YYYY and MM tokens as described above. This is stored in the variable Input_Opt%MERRA_DIR. |
14 |
Specify DATA_DIR_1x1 (stored in Input_Opt%DATA_DIR_1x1). DATA_DIR_1x1 is the root-level data directory path where emission files on the GMAO 1° x 1°, generic 1° x 1°, and native grids are stored. NOTE: This directory is obsolete in GEOS-Chem v10-01 and later versions. We now read emissions data on their native grids from the HEMCO data directories. |
15 |
Specify TEMP_DIR (stored in Input_Opt%TEMP_DIR). TEMP_DIR is the path of a temporary directory into which met field files will be unzipped. NOTE: You only need to specify this if you are unzipping met fields on the fly. This was usually done with GEOS-3 met fields, which are now obsolete. |
16 |
Specify LUNZIP (stored in Input_Opt%LUNZIP). LUNZIP determines whether GEOS-Chem will unzip met field files on the fly. If you have stored your met fields in gzipped format in order to save space, then you must set LUNZIP to T. If you have stored your met fields as unzipped, then set LUNZIP to F. NOTE: You only need to specify this if you are unzipping met fields on the fly. This was usually done with GEOS-3 met fields, which are now obsolete. |
17 |
Specify LWAIT (stored in Input_Opt%LWAIT). If you are unzipping met field files on the fly (i.e. if LUNZIP is set to T), then you may also specify if you want GEOS-Chem to wait until the met field files are completely unzipped before proceeding. It may be necessary to set LWAIT to T if you are using a simulation such as Radon or Tagged Ox where the chemistry takes less time than it does to unzip the met fields. NOTE: You only need to specify this if you are unzipping met fields on the fly. This was usually done with GEOS-3 met fields, which are now obsolete. |
18 | Specify if you want to use the variable tropopause option (stored in Input_Opt%LVARTROP). This should always be set to T if you are using GEOS-4, GEOS-5, or GEOS-FP met fields. |
19 |
Specify the global offsets I0 and J0 (stored in Input_Opt%IO, Input_Opt%JO). For a global run, I0 and J0 must both be set to zero. However, for nested grid runs, we must set I0 and J0 to the appropriate offsets. See our Setting up GEOS-Chem nested grid simulations wiki page for more information. |
Line numbers are not part of the input.geos
file, but have been included for reference.
See Appendix 1 for the list of tracers for the different "full-chemistry" options.
01: %%% TRACER MENU %%% : 02: Type of simulation : 3 03: Number of Tracers : 66 04: Tracer Entries -------> : TR# Name g/mole Tracer Members; () = emitted 05: Tracer #1 : 1 NO 46.0 (NO) 06: Tracer #2 : 2 O3 48.0 (O3) 07: Tracer #3 : 3 PAN 121.0 08: Tracer #4 : 4 CO 28.0 (CO) 09: Tracer #5 : 5 ALK4 12.0 (4C) 10: Tracer #6 : 6 ISOP 12.0 (5C) 11: Tracer #7 : 7 HNO3 63.0 (HNO3) 12: Tracer #8 : 8 H2O2 34.0 13: Tracer #9 : 9 ACET 12.0 (3C) 14: Tracer #10 : 10 MEK 12.0 (4C) 15: Tracer #11 : 11 ALD2 12.0 (2C) 16: Tracer #12 : 12 RCHO 58.0 17: Tracer #13 : 13 MVK 70.0 18: Tracer #14 : 14 MACR 70.0 19: Tracer #15 : 15 PMN 147.0 20: Tracer #16 : 16 PPN 135.0 21: Tracer #17 : 17 R4N2 119.0 22: Tracer #18 : 18 PRPE 12.0 (3C) 23: Tracer #19 : 19 C3H8 12.0 (3C) 24: Tracer #20 : 20 CH2O 30.0 (CH2O) 25: Tracer #21 : 21 C2H6 12.0 (2C) 26: Tracer #22 : 22 N2O5 105.0 27: Tracer #23 : 23 HNO4 79.0 28: Tracer #24 : 24 MP 48.0 29: Tracer #25 : 25 DMS 62.0 30: Tracer #26 : 26 SO2 64.0 31: Tracer #27 : 27 SO4 96.0 32: Tracer #28 : 28 SO4s 96.0 33: Tracer #29 : 29 MSA 96.0 34: Tracer #30 : 30 NH3 17.0 35: Tracer #31 : 31 NH4 18.0 36: Tracer #32 : 32 NIT 62.0 37: Tracer #33 : 33 NITs 62.0 38: Tracer #34 : 34 BCPI 12.0 39: Tracer #35 : 35 OCPI 12.0 40: Tracer #36 : 36 BCPO 12.0 41: Tracer #37 : 37 OCPO 12.0 42: Tracer #38 : 38 DST1 29.0 43: Tracer #39 : 39 DST2 29.0 44: Tracer #40 : 40 DST3 29.0 45: Tracer #41 : 41 DST4 29.0 46: Tracer #42 : 42 SALA 31.4 47: Tracer #43 : 43 SALC 31.4 48: Tracer #44 : 44 Br2 160.0 (Br2) 49: Tracer #45 : 45 Br 80.0 50: Tracer #46 : 46 BrO 96.0 51: Tracer #47 : 47 HOBr 97.0 52: Tracer #48 : 48 HBr 81.0 53: Tracer #49 : 49 BrNO2 126.0 54: Tracer #50 : 50 BrNO3 142.0 55: Tracer #51 : 51 CHBr3 253.0 (CHBr3) 56: Tracer #52 : 52 CH2Br2 174.0 (CH2Br2) 57: Tracer #53 : 53 CH3Br 95.0 58: Tracer #54 : 54 MPN 93.0 59: Tracer #55 : 55 ISOPN 147.0 ISOPND ISOPNB 60: Tracer #56 : 56 MOBA 114.0 61: Tracer #57 : 57 PROPNN 119.0 PROPNN 62: Tracer #58 : 58 HAC 74.0 63: Tracer #59 : 59 GLYC 60.0 64: Tracer #60 : 60 MMN 149.0 MVKN MACRN 65: Tracer #61 : 61 RIP 118.0 66: Tracer #62 : 62 IEPOX 118.0 67: Tracer #63 : 63 MAP 76.0 68: Tracer #64 : 64 NO2 46.0 69: Tracer #65 : 65 NO3 62.0 70: Tracer #66 : 66 HNO2 47.0
Line | Description |
---|---|
1 | Header line |
2 |
Specify the type of GEOS-Chem simulation that you wish to perform. The choices are:
NOTE: In this example, the TRACER MENU is set up for a NOx-Ox-Hydrocarbon-aerosol (or "full chemistry") simulation. |
3 |
Specify N_TRACERS (stored in Input_Opt%N_TRACERS). N_TRACERS is the number of tracers that will be included in the GEOS-Chem simulation. NOTE: If you are performing a "full-chemistry" simulation:
|
4 | Header line |
5 |
Entry for the NO tracer. You must list the following information:
For most types of simulations this is all you need to list. However, for the NOx-Ox-Hydrocarbon-aerosol simulation (a.k.a. "full chemistry") simulation, you must also list the following information, which will be passed to the SMVGEAR chemistry solver routines:
|
6 |
Entry for the O3 tracer. As with NO, you must list the tracer number, name, and molecular weight. O3 has an emission reaction defined in the SMVGEAR chemical mechanism, so you need to list (O3) in parenthesis after the molecular weight in g/mole. |
7 |
Entry for the PAN tracer: As with NO, you must list the tracer number, name, and molecular weight. However, PAN is not a family tracer and it does not have an emission reaction defined in the SMVGEAR chemical mechanism, so this is all the information you need to give. |
8 |
Entry for the CO tracer: As with NO you must list the tracer number, name, and molecular weight. CO has an emission reaction defined in the SMVGEAR chemical mechanism, so you need to list (CO) in parentheses after the molecular weight in g/mole. |
9 |
Entry for the ALK4 (C4 lumped alkanes) tracer: As with NO you must list the tracer number, name, and molecular weight. In GEOS-Chem, several of the hydrocarbon tracers are not carried in molecules of tracer, but in equivalent atoms of carbon. ALK4 is one of these types of hydrocarbon tracers. You can therefore denote this by placing (4C) after the molecular weight in g/mole. The 4C denotes that ALK4 consists of 4 carbon atoms, and the parentheses denote that ALK4 has an emission reaction in the SMVGEAR chemistry mechanism. |
10 |
Entry for the ISOP (isoprene) tracer. This is a hydrocarbon tracer which consists of 5 carbon atoms and has an emission reaction defined in the SMVGEAR chemical mechanism. |
11-12 |
Entries for HNO3 and H2O2 tracers |
13-15 |
Entries for hydrocarbon tracers: ACET (3 carbons), MEK (4 carbons), ALD2 (2 carbons) |
16-21 |
Entries for RCHO, MVK, MACR, PMN, PPN, R4N2. |
22-23 |
Entries for they hydrocarbon tracers PRPE (C3 lumped alkenes—3 carbons) and C3H8 (3 carbons). |
24 |
Entry for CH2O (formaldehyde). This has an emission reaction defined in the SMVGEAR chemistry mechanism so we must list its name in parentheses after the molecular weight. |
25 |
Entry for hydrocarbon tracer C2H6 (2 carbons). |
26-45 |
Entries for the GEOS-Chem aerosol tracers. |
46-47 |
Entries for the GEOS-Chem sea salt tracers. NOTE: The molecular weight of 31.4 g/mole is consistent with actual average composition of sea salt, and international guidelines from the IAPWS. You may use the molecular weight of any individual constituent of interest. |
48-57 |
Entries for the GEOS-Chem bromine tracers.
|
58 |
Entry for the MPN tracer. |
59-67 |
Entries for the GEOS-Chem isoprene tracers.
|
68-70 |
Entries for NO2, NO3, HNO2. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% TRANSPORT MENU %%% : 02: Turn on Transport : T 03: => Fill Negative Values: T 04: => IORD, JORD, KORD : 3 3 7 05: Transport Timestep [min]: 30
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LTRAN (stored in Input_Opt%LTRAN). Set LTRAN to T to turn on TPCORE transport, or set to F to turn off TPCORE transport. |
3 |
Specify LFILL (located in source code file Input_Opt%LFILL). Setting LFILL to T will cause TPCORE to fill negative values with zeroes. |
4 |
Specify the IORD, JORD, KORD transport options for TPCORE (stored in Input_Opt%TPCORE_IORD, Input_Opt%TPCORE_JORD, Input_Opt%TPCORE_KORD). These settings determine how TPCORE performs transport in the E/W, N/S, and vertical directions. Recommended values are 3, 3, 7. |
5 |
Specify the transport timestep (TS_DYN, stored in Input_Opt%TS_DYN) in minutes. Recommended values: 30 min (4° x 5°), 15 min (2° x 2.5°), 10 min (0.5° x 0.666°), or 5 min (0.25° x 0.3125°). The transport timestep should be the smallest timestep used. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% CONVECTION MENU %%% : 02: Turn on Cloud Conv? : T 03: Turn on PBL Mixing? : T 04: => Use non-local PBL? : T 05: Convect Timestep (min) : 30
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LCONV (stored in Input_Opt%LCONV). Set LCONV to T to turn on cloud convection. |
3 |
Specify LTURB (stored in Input_Opt%LTURB). Set LTURB to T to turn on PBL mixing. |
4 |
Specify LNLPBL (stored in Input_Opt%LNLPBL). The options are as follows:
NOTE: If LTURB (Line 3) is set to F, then neither PBL mixing option will be executed, regardless of the setting of LNLPBL. |
5 |
Specify the convection timestep (TS_CONV, stored in Input_Opt%TS_CONV) in minutes. The convection timestep should equal the the transport timestep (i.e. TS_CONV = TS_DYN). This is required for the central chemistry timestep algorithm. |
NOTE: This menu is now mostly obsolete because of HEMCO. We now use the HEMCO_Config.rc file to specify the the emission inventories (as well as some important non-emissions data) to be read by GEOS-Chem.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %% EMISSIONS MENU %%% : 02: Turn on emissions? : T 03: Emiss timestep (min) : 60 04: HEMCO Input file : HEMCO_Config.rc 05: => 1ppt MBL BRO Sim.? : F 06: Switches for UCX :--- 07: => Use CH4 emissions? : F 08: => Turn on surface BCs :--- 09: => CH4? : T 10: => OCS? : T 11: => CFCs? : T 12: => Cl species? : T 13: => Br species? : F 14: => N2O? : T 15: => Set initial glob MRs:--- 16: => strat. H2O? : T 17: => CH4? : T 18: => OCS? : T 19: => CFCs? : T 20: => Cl species? : T 21: => strat Bry (GCCM)?: T 22: => Br species? : F 23: => strat. Br? : F 24: => strat. NOx/HNO3? : T 25: => N2O? : T 26: => strat. SO4? : T 27: => CFC emission year : 0
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LEMIS (stored in Input_Opt%LEMIS). Set LEMIS to T to turn on emissions in a GEOS-Chem simulation. Set LEMIS to F to turn off all emissions in a GEOS-Chem simulation. |
3 |
Specify the emission timestep (TS_EMIS, stored in Input_Opt%TS_EMIS) in minutes. The emissions timestep should be the same as the chemistry time step (i.e. TS_EMIS = TS_CHEM). This is required for the central chemistry timestep algorithm. |
4 |
Specify the name of the HEMCO configuration file (stored in Input_Opt%HcoConfigFile). The emission inventories that your simulation will use are set in this file. |
5 |
Specify LFIX_PBL_BrO (stored in Input_Opt%LFIX_PBL_BrO). Set LFIX_PBL_BrO to T to set Bro concentrations in the PBL equal to 1 ppt during the day. |
6 | Header line |
7 | Specify LCH4EMIS (stored in Input_Opt%LCH4EMIS). Set LCH4EMIS to T to use online methane emissions. |
8 | Header line |
9 | Specify LCH4SBC (stored in Input_Opt%LCH4SBC). Set LCH4SBC to T to fix surface mixing ratio of methane. |
10 | Specify LOCSEMIS (stored in Input_Opt%LOCSEMIS). Set LOCSEMIS to T to fix surface mixing ratios of OCS. |
11 | Specify LCFCEMIS (stored in Input_Opt%LCFCEMIS). Set LCFCEMIS to T to fix surface mixing ratios of CFCs, HCFCs, and halons to match WMO projections under the Montreal Protocol. |
12 | Specify LCLEMIS (stored in Input_Opt%LCLEMIS). Set LCLEMIS to T to fix surface mixing ratios of other chlorinated carbon and inorganic chlorine species to match WMO projections under the Montreal Protocol. |
13 | Specify LBREMIS (stored in Input_Opt%LBREMIS). Set LBREMIS to T to fix surface mixing ratios of bromine species. Not recommended if other bromine emissions are enabled. |
14 | Specify LN2OEMIS (stored in Input_Opt%LN2OEMIS). Set LN2OEMIS to T to fix surface mixing ratios of N2O. |
15 | Header line |
16 | Specify LSETH2O (stored in Input_Opt%LSETH2O). Set LSETH2O to T to initialize stratospheric H2O mixing ratios based on meteorology data for the first timestep, overriding any restart file values. |
17 | Specify LSETCH4 (stored in Input_Opt%LSETH2O). Set LSETCH4 to T to initialize CH4 from the default GEOS-Chem climatology for the first timestep, overriding any restart file values. |
18 | Specify LSETOCS (stored in Input_Opt%LSETOCS). Set LSETOCS to T to initialize OCS distribution based on zonal means from a 2D model. |
19 | Specify LSETCFC (stored in Input_Opt%LSETCFC). Set LSETCFC to T to initialize CFCs, HCFCs, and halocarbons based on zonal means from a 2D model. |
20 | Specify LSETCL (stored in Input_Opt%LSETCL). Set LSETCL to T to initialize other chlorinated carbon and inoragnic chlorine species based on zonal means from a 2D model. |
21 | Specify LSETBRGCCM (stored in Input_Opt%LSETBRGCCM). Set LSETBRGCCM to T to initialize stratospheric bromine species to GCCM baseline. |
22 | Specify LSETBR (stored in Input_Opt%LSETBR). Set LSETBR to T to initialize bromine species based on zonal means from a 2D model. |
23 | Specify LSETBRSTRAT (stored in Input_Opt%LSETBRSTRAT). Set LSETBRSTRAT to T to initialize stratospheric bromine species based on zonal means from a 2D model. |
24 | Specify LSETNOYSTRAT (stored in Input_Opt%LSETNOYSTRAT). Set LSETNOYSTRAT to T to initialize stratospheric NOx and HNO3 based on zonal means from a 2D model. |
25 | Specify LSETN2O (stored in Input_Opt%LSETN2O). Set LSETN2O to T to initialize N2O distribution based on zonal means from a 2D model. |
26 | Specify LSETH2SO4 (stored in Input_Opt%LSETH2SO4). Set LSETH2SO4 to T to initialize stratospheric sulfates based on zonal means from a 2D model. |
27 | Specify the starting year for CFC emissions (stored in Input_Opt%CFCYEAR) |
NOTE: This menu is now mostly obsolete because of HEMCO. We now use the HEMCO_Config.rc file to set the emission inventories. At present, this menu controls options that only affect simulations with GCAP met fields.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% FUTURE MENU %%% : 02: Use future emissions? : F 03: Which IPCC future year? : 2050 04: Which IPCC scenario? : A1
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LFUTURE (stored in Input_Opt%LFUTURE). Set LFUTURE to T to scale present-day emissions to one of the IPCC future scenarios, or F otherwise. |
3 |
Specify FUTURE_YEAR (stored in Input_Opt%FUTURE_YEAR), which is the year to which the current emissions will be scaled. Current options are 2030 and 2050. |
4 |
Specify FUTURE_SCEN (stored in Input_Opt%FUTURE_SCEN), which is the IPCC scenario to be used. Current options are: A1, B1. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% AEROSOL MENU %%% : 02: Online SULFATE AEROSOLS : T 03: Online CRYST/AQ AEROSOLS: F 04: Online CARBON AEROSOLS : T 05: Online 2dy ORG AEROSOLS : F 06: => Semivolatile POA? : F 07: Online DUST AEROSOLS : T 08: Online SEASALT AEROSOLS : T 09: => SALA radius bin [um]: 0.01 0.5 10: => SALC radius bin [um]: 0.5 8.0 11: Online dicarb. chem. : F 12: Settle strat. aerosols : F 13: Online PSC AEROSOLS : F 14: Allow homogeneous NAT? : F 15: NAT supercooling req.(K): 3.0 16: Ice supersaturation req.: 1.2 17: Perform PSC het. chem.? : F 18: Calc. strat. aero. OD? : F
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LSULF (stored in Input_Opt%LSULF). Set LSULF to T to turn on chemistry for sulfate aerosols (DMS, SO2, SO4, MSA, NH3, NH4, NIT). |
3 |
Specify LCRYST (stored in Input_Opt%LCRYST). Set LCRYST to T to turn on chemistry for crystalline sulfur and aqueous aerosols (AS, AHS, LET, SO4aq, NH4aq). NOTE: This feature has not been implemented in GEOS-Chem v10-01. For the time being, set LCRYST to F. |
4 |
Specify LCARB (stored in Input_Opt%LCARB). Set LCARB to T to turn on chemistry for carbonaceous aerosols (BCPI, BCPO, OCPI, OCPO). |
5 |
Specify LSOA (stored in Input_Opt%LSOA). Set LSOA to T to turn on chemistry for secondary organic aerosols. Turning on the secondary organic aerosols will add 27 tracers to the simulation. |
6 |
Specify LSVPOA (stored in Input_Opt%LSVPOA). Set LSVPOA to T to use the semivolatile POA option. |
7 |
Specify LDUST (stored in Input_Opt%LDUST). Set LDUST to T to turn on chemistry for mineral dust aerosol tracers (DST1, DST2, DST3, DST4). |
8 |
Specify LSSALT (stored in Input_Opt%LSSALT). Set LSSALT to T to turn on chemistry for sea salt aerosols (SALA, SALC). |
9 |
Specify the edges which denote accumulation mode sea salt tracer in microns (stored in variable Input_Opt%SALA_REDGE_um). Recommended setting: 0.01 to 0.5 microns. |
10 |
Specify the edges which denote coarse mode sea salt tracer in microns (stored in Input_Opt%SALC_REDGE_um). Recommended setting: 0.5 to 8 microns. |
11 | Specify LDICARB (stored in Input_Opt%LDICARB). Set LDICARB to T if you are using the dicarbonyl chemistry simulations (108 tracers), to F otherwise. |
12 | Specify LGRAVSTRAT (stored in Input_Opt%LGRAVSTRAT). Set LGRAVSTRAT to T to apply gravitational settling to stratospheric solid particulate aerosols (SPA, trapezoidal scheme) and stratospheric liquid aerosols (SLA, corrected Stokes' Law). This switch applies to the UCX simulation only. |
13 | Specify LSOLIDPSC (stored in Input_Opt%LSOLIDPSC). Set LSOLIDPSC to T to use solid polar stratospheric clouds (PSCs). This switch applies to the UCX simulation only. |
14 | Specify LHOMNUCNAT (stored in Input_Opt%LHOMNUCNAT). Set LHOMNUCNAT to T to allow NAT to form homogeneously from freezing of HNO3. This switch applies to the UCX simulation only. |
15 | Specify T_NAT_SUPERCOOL, the degrees Kelvin of cooling required for homogeneous NAT nucleation (stored in Input_Opt%T_NAT_SUPERCOOL). This value applies to the UCX simulation only. |
16 | Specify P_ICE_SUPERSAT, the supersaturation factor required for ice nucleation (stored in Input_Opt%P_ICE_SUPERSAT). The recommended value is 1.2 for coarse grids and 1.5 for fine grids. These values apply to the UCX simulation only. |
17 | Specify LPSCCHEM (stored in Input_Opt%LPSCCHEM). Set LPSCCHEM to T to allow heterogeneous chemistry on stratospheric aerosols. This switch applies to the UCX simulation only. |
18 | Specify LSTRATOD (stored in Input_Opt%LSTRATOD). Set LSTRATOD to T to include online stratospheric aerosols in extinction calculations for photolysis. This switch applies to the UCX simulation only. |
NOTES:
You may define the limits of the accumulation and coarse mode sea salt aerosol radius bins (in variables SALA_REDGE_um and SALC_REDGE_um) as you wish. However, the recommended values of 0.01-0.5 and 0.5-8 microns, respectively, were chosen in order to conform to the cross-sections and other optical settings as defined in the FAST-JX input files ssa.dat and ssc.dat. Therefore, unless you use the recommended values, you will not be able to archive aerosol optical depths for these aerosol types with the ND21, ND48, ND49, ND50, and ND51 diagnostics.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% DEPOSITION MENU %%% : 02: Turn on Dry Deposition? : T 03: Turn on Wet Deposition? : T
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LDRYD (stored in Input_Opt%LDRYD). Set LDRYD to T to turn on dry deposition, or F to turn off dry deposition. |
3 |
Specify LWETD (stored in Input_Opt%LWETD). Set LWETD to T to turn on wet deposition, or F to turn off wet deposition. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% CHEMISTRY MENU %%% : 02: Turn on Chemistry? : T 03: Use linear. strat. chem?: T 04: => Use Linoz for O3? : T 05: Use UCX strat. chem? : F 06: Online CH4 chemistry? : F 07: Active strat. H2O? : F 08: Chemistry Timestep [min]: 60 09: Read and save CSPEC_FULL: T 10: => CSPEC rst filename? : spec_rst.geosfp_4x5_UCX.YYYYMMDDhh 11: Use solver coded by KPP : T 12: Online O3 for FAST-JX? : T 13: Gamma HO2 : 0.2
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LCHEM (stored in Input_Opt%LCHEM). Set LCHEM to T to turn on chemistry, or F to turn off chemistry. |
3 |
Specify LSCHEM (stored in Input_Opt%LSCHEM). Set LSCHEM to T to turn on linearized stratospheric chemistry, or F to turn off stratospheric chemistry. NOTE: If the UCX chemistry mechanism is used (LUCX=T), then linearized chemistry is applied in the mesosphere. |
4 |
Specify LLINOZ (stored in Input_Opt%LLINOZ). Set LLINOZ to T to use Linoz for O3 chemistry in the stratosphere, otherwise Synoz will be used. NOTE: If the UCX chemistry mechanism is used (LUCX=T), then Linoz is applied in the mesosphere. |
5 | Specify LUCX (stored in Input_Opt%LUCX). Set LUCX to T to use the UCX tropospheric-stratospheric chemistry mechanism, otherwise online chemistry will only be applied in the troposphere. To use this option you must compile GEOS-Chem with UCX=yes. |
6 | Specify LCH4CHEM (stored in Input_Opt%LCH4CHEM). Set LCH4CHEM to T to use online methane chemistry. |
7 | Specify LACTIVEH2O (stored in Input_Opt%LACTIVEH2O). Set LACTIVEH2O to T to allow the stratospheric H2O tracer to influence specific humidity and relative humidity. To use this option, you must also set LUCX to T. |
8 |
Specify the chemistry timestep (TS_CHEM, stored in Input_Opt%TS_CHEM) in minutes. We suggest using a chemistry timestep double the transport time step (this is known as Strang operator splitting). Typical chemistry timesteps are 60 min (4° x 5°), 30 min (2° x 2.5°), 20 min (0.5° x 0.666°), or 10 min (0.25° x 0.3125°). In all cases, the chemistry timestep should be a multiple of the transport timestep (i.e. TS_CHEM = X * TS_DYN, where X is an integer). See our Centrailzed chemistry timestep wiki page for more information. |
9 |
Specify LSVCSPEC (stored in Input_Opt%LSVCSPEC). Set LSVCSPEC to T to save concentrations (stored in the CSPEC_FULL array) of all chemical species listed in the globchem.dat file to a CSPEC restart file, or to F otherwise. The CSPEC restart file is saved in addition to the standard restart file, which saves only concentrations of transported tracers. If LSVCSPEC is F or if GEOS-Chem can't find a CSPEC restart file at the beginning of a simulation, then the chemical species will be initialized with the default concentrations specified in globchem.dat. If the option Make new restart file is set to F in the Simulation Menu, then no CSPEC restart file will be saved regardless of the value of LSVCSPEC. NOTE: If you are going to be running a very long GEOS-Chem simulation, and must split the job into several stages (i.e. in order to stay within the computational time limts of your system), then you should set LSVCSPEC to T. This will make sure that the chemical species concentrations are preserved when the next run stage starts. Otherwise, GEOS-Chem will start each simulation using the default species concentrations specified in globchem.dat. |
10 |
Specify the name of the CSPEC restart file, which contains initial species concentrations. If you just specify the filename, GEOS-Chem will look for the CSPEC restart file in the run directory. You may also sepcify an entire directory path. Also, you may include the following tokens in the file name:
NOTE: Since the typical GEOS-Chem simulations start and end at the top of the hour, using YYYYMMDDhh in the CSPEC restart file name should suffice for most applications. |
11 | Specify LKPP (stored in Input_Opt%LKPP).
Set LKPP to T to use a chemistry solver coded by the KPP pre-processor. If set to F, the chemistry solver SMVGEAR II is used.
NOTE: When using the UCX mechanism, we recommend setting LKPP to T. SMVGEAR can be used with UCX, but it has been found to be extremely slow. |
12 | Specify LO3FJX (stored in Input_Opt%LO3_FJX). Set LO3FJX to T to use online O3 from GEOS-Chem in the extinction calculations for FAST-JX photolysis. |
13 | Specify GAMMA_HO2 (stored in Input_Opt%GAMMA_HO2). The recommended setting is 0.2. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% RADIATION MENU %%% : 02: AOD Wavelength (nm) : 550 03: Turn on RRTMG? : F 04: Calculate LW fluxes? : F 05: Calculate SW fluxes? : F 06: Clear-sky flux? : F 07: All-sky flux? : F 08: Radiation Timestep [min]: 180 09: Species fluxes : 0 0 0 0 0 0 0 0 0 1 10: ---[O3,ME,SU,NI,AM,BC,OA,SS,DU,PM]
Line | Description |
---|---|
1 |
Header line |
2 |
Specify wavelength(s) for the aerosol optical properties. Up to three wavelengths can be output. The wavelengths should be entered in nm with a space between each entry. The specified wavelengths are used for the Fast-JX photolysis mechanism, regardless of whether the RRTMG radiative transfer model is used. |
3 |
Specify LRAD (stored in Input_Opt%LRAD). Set LRAD to T to turn on online radiative transfer using RRTMG, or F to turn off RRTMG. |
4 |
Specify LLWRAD (stored in Input_Opt%LLWRAD). Set LLWRAD to T to turn on longwave radiation calculation. |
5 |
Specify LSWRAD (stored in Input_Opt%LSWRAD). Set LSWRAD to T to turn on shortwave radiation calculation. |
6 | Specify LSKYRAD(1) (stored in Input_Opt%LSYKRAD(1)). Set LSKYRAD(1) to T to turn turn on calculation for clear-sky fluxes. This option will perform radiative calculations without clouds. |
7 | Specify LSKYRAD(2) (stored in Input_Opt%LSYKRAD(2)). Set LSKYRAD(2) to T to turn turn on calculation for all-sky fluxes. This option will perform radiative with clouds. Both clear sky and all-sky options can be turned on without signigicant increase to run time. |
8 | Specify the radiation timestep (TS_RAD, stored in Input_Opt%TS_RAD) in minutes. In all cases, the radiation timesetp should be a multiple of the transport timestep. The RRTMG calculation is instantaneous (i.e. not averaged over the period selected) and is set to occur at half the radiation timestep. We recommend using a radiation timestep of 180 min (producing RRTMG calls at 01:30, 4:30, etc.). |
9 |
Specify the species for which radiative fluxes will be calculated. Set a value to 1 to calculate the radiative effect for that species, or 0 to turn off radiative calculations for that species. The first RRTMG call (the "baseline") contains all species switched on and each requested species calls RRTMG again with that species omitted, so that the difference can be calculated. The number of calls to RRTMG will be equal to the total sum of this line plus one (for the first "baseline" call), so this can substantially increase model run time. If you are using the UCX chemistry mechanism, then you will need to add an additional entry (0 or 1) at the end of this line for stratospheric aerosols for a total of 11 possible species. |
10 |
This line lists species available for output from the flux calculations. This line is here for reference and is not actually read by GEOS-Chem. Available species are:
|
This menu only controls options for the CO2 and tagged CO2 simulations. This is an optional menu and may be omitted from input.geos if you are not concerned with these simulations.
For more information, please see:
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% CO2 SIM MENU %%% : 02: Fossil Fuel Emissions :--- 03: Generic FF emissions : F 04: Annual FF emissions : F 05: Monthly FF emissions : T 06: 3-D Chemical Oxid Source: F 07: Terrestrial Exchange :--- 08: CASA daily avg NEP : F 09: CASA diurnal cycle NEP: T 10: Net Ter Ex original : F 11: Net Ter Ex climatology: T 12: Ocean Exchange :--- 13: Takahashi 1997 : F 14: Takahashi 2009 annual : F 15: Takahashi 2009 monthly: T 16: Ship & Plane Emissions :--- 17: EDGAR ship emissions : F 18: ICOADS ship emissions : T 19: Aviation emissions : T 20: Tagged CO2 runs :--- 21: Save Fossil CO2 Bkgrd : F 22: Tag Bios/Ocean CO2 reg: F 23: Tag Land FF CO2 reg : F 24: Tag Global Ship CO2 : F 25: Tag Global Plane CO2 : F
Line | Description |
---|---|
1 | Header line |
2 | Fossil Fuel sub-header line (select only one option in this section). |
3 | Annually averaged fossil fuel emissions for 1995 from CDIAC [Andres et al., 1996]. This is stored in the variable Input_Opt%LGENFF. NOTE: The choice of fossil fuel emissions in the CO2 Menu must be consistent with the choice in the HEMCO_Config.rc file. |
4 | Year-specific annually averaged fossil fuel emissions from CDIAC [Andres et al., 1996], with 2007-2009 scaled based on [Boden et al., 2009; LeQuere, 2009]. This is stored in the variable Input_Opt%LANNFF. NOTE: The choice of fossil fuel emissions in the CO2 Menu must be consistent with the choice in the HEMCO_Config.rc file. |
5 | Month and year-specific monthly averaged fossil fuel emissions from CDIAC [Andres et al., 1996], with 2007-2009 scaled based on [Boden et al., 2009; LeQuere, 2009]. This is stored in the variable Input_Opt%LMONFF. NOTE: The choice of fossil fuel emissions in the CO2 Menu must be consistent with the choice in the HEMCO_Config.rc file. |
6 | 3-D CO2 chemical source from oxidation of CO, CH4 and NMHCs based on Suntharalingam et al. [2005], with appropriate surface emission corrections. This is stored in the variable Input_Opt%LCHEMCO2. |
7 | Terrestrial Exchange sub-header line (select one balanced biosphere option and one Net Terrestrial Exchange option). |
8 | CASA model daily average Net Ecosystem Production (balanced – no net annual flux) [Potter et al., 1993; Olsen and Randerson, 2004]. This is stored in the variable Input_Opt%LBIODAILY. |
9 | CASA model 3-hourly Net Ecosystem Production (balanced – no net annual flux) [Potter et al., 1993; Olsen and Randerson, 2004]. This is stored in the variable Input_Opt%LBIODIURNAL. |
10 | Net Terrestrial Exchange (original) of -1.01 PgC/yr. This is stored in the variable Input_Opt%LBIONETORIG. |
11 | Net Terrestrial Exchange (climatology) of -5.29 PgC/yr [Baker et al., 2006] adjusted for biomass/biofuel burning. This is stored in the variable Input_Opt%LBIONETCLIM. |
12 | Ocean Exchange sub-header line (select only one option in this section). |
13 | Annual ocean flux climatology of non-El Niño years from Takahashi et al. [1997]. This is stored in the variable Input_Opt%LOCN1997. |
14 | Annual ocean flux climatology of non-El Niño years from Takahashi et al. [2009]. This is stored in the variable Input_Opt%LOCN2009ANN. |
15 | Monthly ocean flux climatology of non-El Niño years from Takahashi et al. [2009]. This is stored in the variable Input_Opt%LOCN2009MON. |
16 | Ship and Plane sub-header (select no more than one ship option and one aviation option). |
17 | International ship CO2 emissions (annually-averaged) with simplified distribution from EDGAR scaled to scaled to annual values for 1985-2006 [Endresen et al. 2007]. This is stored in the variable Input_Opt%LSHIPEDG. NOTE: The choice of ship emissions in the CO2 Menu must be consistent with the choice in the HEMCO_Config.rc file. |
18 | International ship CO2 emissions based on the International Comprehensive Ocean Atmosphere Data Set (ICOADS) with monthly variability [Corbett & Koehler, 2003, 2004; Wang et al., 2008] scaled to annual values for 1985-2006 [Endresen et al. 2007]. This is stored in the variable Input_Opt%LSHIPICO. NOTE: The choice of ship emissions in the CO2 Menu must be consistent with the choice in the HEMCO_Config.rc file. |
19 | Aviation emission 3-D distribution from fuel burn (GEOS-Chem sulfate aerosol simulation) scaled to annual CO2 values for 1985-2002 [Sausen & Schumann, 2000; Kim et al., 2005; 2007; Wilkerson et al., 2010] and estimates for 2002-2009. An associated surface correction automatically removes domestic aviation emissions from the main fossil fuel source in continental size regions. This is stored in the variable Input_Opt%LPLANE. NOTE: The choice of aircraft emissions in the CO2 Menu must be consistent with the choice in the HEMCO_Config.rc file. |
20 | Tagged CO2 sub-header line (select all that apply). |
21 | Save CO2 background. This is stored in the variable Input_Opt%LFFBKGRD. |
22 | Tag biosphere regions (28), ocean regions (11) and the Rest of the World (ROW) as specified in the Regions_land.dat and Regions_ocean.dat files. This is stored in the variable Input_Opt%LBIOSPHTAG. NOTE: Tagged tracers should be customized by each user and the present configuration will not work for resolutions other than 2x2.5. |
23 | Tag fossil fuel regions (28) as specified in the Regions_land.dat file and ROW. This is stored in the variable Input_Opt%LFOSSILTAG. NOTE: Tagged tracers should be customized by each user and the present configuration will not work for resolutions other than 2x2.5. |
24 | Tag global ship emissions as a single tracer. This is stored in the variable Input_Opt%LSHIPTAG. NOTE: Tagged tracers should be customized by each user and the present configuration will not work for resolutions other than 2x2.5. |
25 | Tag global aviation emissions as a single tracer. This is stored in the variable Input_Opt%LPLANETAG. NOTE: Tagged tracers should be customized by each user and the present configuration will not work for resolutions other than 2x2.5. |
This menu only controls options for the mercury simulation (with or without the Global Terrestrial Mercury Model). This is an optional menu and may be omitted from input.geos if you are not concerned with this simulation.
For more information, please see:
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% MERCURY MENU %%% : 02: Use anthro Hg emiss for : 2006 03: Use future emissions? : PRESENT 04: Error check tag/tot Hg? : F 05: Use dynamic ocean Hg? : T 06: Preindustrial sim? : F 07: Ocean Hg restart file : ocean_rst.geosfp_4x5_Hg.YYYYMMDDhhmm 08: Use GTMM soil model? : F 09: GTMM Hg restart file : GTM.totHg.YYYYMMDDhh
Line | Description |
---|---|
1 | Header line |
2 | Specify ANTHRO_Hg_YEAR (stored in Input_Opt%ANTHRO_Hg_YEAR), which is the baseline year of the anthropogenic mercury emissions that are used in the tagged mercury simulation. Current options are either 2006 or 2050. |
3 | Specify Hg_SCENARIO (stored in Input_Opt%Hg_SCENARIO). Future emissions are based on the four IPCC SRES scenarios. Current options are PRESENT, A1B, A2, B1, or B2. |
4 | Specify USE_CHECKS (stored in Input_Opt%USE_CHECKS). Set USE_CHECKS to T to stop with an error message if the sum of tagged tracers does not equal the total tracer, or F otherwise. This is useful for debugging. |
5 | Specify LDYNOCEAN (stored in Input_Opt%LDYNOCEAN). Set LDYNOCEAN to T to use the online ocean mercury model (in source code file ocean_mercury_mod.F) or F to read ocean mercury concentrations from monthly mean files on disk. |
6 | Specify LPREINDHG (stored
in Input_Opt%LPREINDHG). Set to T if you want to run a
preindustrial simulation (turn off anthropogenic emissions), to F
otherwise. |
7 | If you have set LDYNOCEAN to T (i.e. you are using the online ocean mercury model), then you can specify the name of the ocean mercury restart file. This file saves the concentrations of oceanic mercury tracers for continuing the run at a later stage. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
8 | Specify LGTMM (stored in Input_Opt%LGTMM). Set to T if you want to run GTMM online in GEOS-Chem. Note, that to use GTMM online, you need to first run GTMM offline up to equilibrium and to compile GEOS-Chem with GTMM enabled. For more information, please refer to this document. |
9 | If you are using the GTMM online, then you can specify the name of the GTMM mercury restart file. This file saves the monthly depositions of mercury tracers for continuing the run at a later stage. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
NOTES:
NOTE: This menu controls options for the POPs specialty simulation only. This is an optional menu and may be omitted from input.geos if you are not concerned with this simulation.
For more information, please see:
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% POPS MENU %%% : 02: POP type [PHE,PYR,BAP] : PHE 03: Chemistry proceesing on?: T 04: POP_XMW : 178d-3 05: POP_KOA : 4.37d7 06: POP_KBC : 1d10 07: POP_K_POPG_OH : 2.70d-11 08: POP_K_POPG_O3A : 5d-4 09: POP_K_POPG_O3B : 2.15d15 10: POP_HSTAR : 2.35d1 11: POP_DEL_H : -74d3 12: POP_DEL_Hw : -5.65d3
Line |
Description |
---|---|
1 | Header line |
2 | Specify POP_TYPE (stored in Input_Opt%POP_TYPE). Current options are PHE (phenanthrene), PYR (pyrene), or BAP (benzo[a]pyrene). |
3 | Specify CHEM_PROCESS (stored in Input_Opt%CHEM_PROCESS). Set CHEM_PROCESS to T to use POPs chemistry. |
4 | Specify molecular weight of POP_TYPE in kg/mol (stored in Input_Opt%POP_XMW). |
5 | Specify the POP octanol-water partition coefficient (stored in Input_Opt%POP_KOA). |
6 | Specify the POP black carbon-air partition coefficient (stored in Input_Opt%POP_KBC). |
7 | Specify the POP reaction rate constant for reaction of gas phase POP with hydroxyl radical in cm3/molec/s (stored in Input_Opt%POP_K_POPG_OH). |
8 | Specify the POP reaction rate constant for reaction of particle phase POP with ozone in s-1 (stored in Input_Opt%POP_K_POPP_O3A). |
9 | Specify the POP reaction rate constant for reaction of particle phase POP with ozone in molec/cm3 (stored in Input_Opt%POP_K_POPP_O3B). |
10 | Specify the Henry's Law constant for POP_TYPE (stored in Input_Opt%POP_HSTAR). |
11 | Specify the enthalpy of air-water exchange in J/mol (stored in Input_Opt%POP_DEL_H). |
12 | Specify the enthalpy of phase transfer from gas phase to particle phase (stored in Input_Opt%POP_DEL_Hw). |
5.2.1.14 The CH4 MENU (a.k.a. methane menu)
NOTE: This menu controls options for the tagged CH4 simulation only. This is an optional menu and may be omitted from input.geos if you are not concerned with this simulation.
For more information, please see:
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% CH4 MENU %%% : 02: Compute CH4 budget? : F 03: Use Gas & Oil emis? : T 04: Use Coal Mine emis? : T 05: Use Livestock emis? : T 06: Use Waste emis? : T 07: Use Biofuel emis? : T 08: Use Rice emis? : T 09: Use Ot. Anthro emis? : T 10: Use Biomass emis? : T 11: Use Wetlands emis? : T 12: Use Soil Absorption? : T 13: Use Ot. Natural emis? : T
Line |
Description |
---|---|
1 | Header line |
2 | Specify LCH4BUD (stored in Input_Opt%LCH4BUD). Set LCH4BUD to T to calculate a monthly budget for CH4. The CH4 budget is not working well, we recommend setting LCH4BUD to F. |
3 | Specify LGAO (stored in Input_Opt%LGAO). Set LGAO to F to turn off CH4 emissions from gas and oil. |
4 | Specify LCOL (stored in Input_Opt%LCOL). Set LCOL to F to turn off CH4 emissions from coal. |
5 | Specify LLIV (stored in Input_Opt%LLIV). Set LLIV to F to turn off CH4 emissions from livestock. |
6 | Specify LWAST (stored in Input_Opt%LWAST). Set LWAST to F to turn off CH4 emissions from waste. |
7 | Specify LBFCH4 (stored in Input_Opt%LBFCH4). Set LBFCH4 to F to turn off CH4 emissions from biofuels. |
8 | Specify LRICE (stored in Input_Opt%LRICE). Set LRICE to F to turn off CH4 emissions from rice fields. |
9 | Specify LOTANT (stored in Input_Opt%LOTANT). Set LOTANT to F to turn off other CH4 anthropogenic emissions. |
10 | Specify LBMCH4 (stored in Input_Opt%LBMCH4). Set LBMCH4 to F to turn off CH4 emissions from biomass burning. |
11 | Specify LWETL (stored in Input_Opt%LWETL). Set LWETL to F to turn off CH4 emissions from wetlands |
12 | Specify LSOABS (stored in Input_Opt%LSOABS). Set LSOABS to F to turn off CH4 absorption by soils. |
13 | Specify LOTNAT (stored in Input_Opt%LOTNAT). Set LOTNAT to F to turn off other CH4 natural emissions. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% OUTPUT MENU %%% : 123456789.123456789.123456789.1--1=ZERO+2=BPCH 02: Schedule output for JAN : 3000000000000000000000000000000 03: Schedule output for FEB : 30000000000000000000000000000 04: Schedule output for MAR : 3000000000000000000000000000000 05: Schedule output for APR : 300000000000000000000000000000 06: Schedule output for MAY : 3000000000000000000000000000000 07: Schedule output for JUN : 300000000000000000000000000000 08: Schedule output for JUL : 3000000000000000000000000000000 09: Schedule output for AUG : 3000000000000000000000000000000 10: Schedule output for SEP : 300000000000000000000000000000 11: Schedule output for OCT : 3000000000000000000000000000000 12: Schedule output for NOV : 300000000000000000000000000000 13: Schedule output for DEC : 3000000000000000000000000000000
Line | Description |
---|---|
1 |
Header line |
2 |
Schedule diagnostic output for JANUARY. Place a 3 in the column corresponding to the day of the month (1-31) on which you want diagnostic output saved to the binary punch file. In the example above, the columns which indicate January 1st and February 1st both have a 3 listed there. This will cause GEOS-Chem to archive diagnostic data for the entire month of January and then save it to disk at 0 GMT on February 1st. (GEOS-Chem is smart enough not to write anything to disk at 0 GMT on January 1st, since this is the starting time of the simulation.) If you would like to save daily diagnostic output to the binary punch file, put a 3 for each day of each month. NOTE: You must place a 3 in the location corresponding to the simulation end date. Otherwise, the GEOS-Chem simulation will crash immediately with the error No output scheduled on last day of run! |
3 |
Schedule diagnostic output for FEBRUARY |
4 |
Schedule diagnostic output for MARCH |
5 |
Schedule diagnostic output for APRIL |
6 |
Schedule diagnostic output for MAY |
7 |
Schedule diagnostic output for JUNE |
8 |
Schedule diagnostic output for JULY |
9 |
Schedule diagnostic output for AUGUST |
10 |
Schedule diagnostic output for SEPTEMBER |
11 |
Schedule diagnostic output for OCTOBER |
12 |
Schedule diagnostic output for NOVEMBER |
13 |
Schedule diagnostic output for DECEMBER |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% GAMAP MENU %%% : 02: diaginfo.dat path : diaginfo.dat 03: tracerinfo.dat path : tracerinfo.dat
Line | Description |
---|---|
1 |
Header line |
2 |
Path name of the diaginfo.dat file for GAMAP. GEOS-Chem will create this file, which will be customized to the particular simulation that is being done. This may be either a relative path name (i.e. diaginfo.dat) or an absolute path name (i.e. /home/bmy/T/run.v9-01-03/diaginfo.dat). |
3 |
Path name of the tracerinfo.dat file for GAMAP. GEOS-Chem will create this file, which will be customized to the particular simulation that is being done. This may be either a relative path name (i.e. tracerinfo.dat) or an absolute path name (i.e. /home/bmy/T/run.v9-01-03/tracerinfo.dat). |
Line numbers are not part of the input.geos file, but have been included for reference.
For more information about GEOS-Chem diagnostics, please see Appendix 5.
01: %% DIAGNOSTIC MENU %%% : 02: Binary punch file name : trac_avg.geosfp_4x5_UCX.YYYYMMDDhh 03: Diagnostic Entries ---> : L Tracers to print out for each diagnostic 04: ND01: Rn/Pb/Be source : 0 all 05: ND02: Rn/Pb/Be decay : 0 all 06: ND03: Hg emissions, P/L : 0 all 07: ND04: CO2 Sources : 0 all 08: ND05: Sulfate prod/loss : 47 all 09: ND06: Dust aer source : 1 all 10: ND07: Carbon aer source : 47 all 11: ND08: Seasalt aer source: 1 all 12: ND09: - : 0 all 13: ND10: - : 0 all 14: ND11: Acetone sources : 1 all 15: ND12: BL fraction : 0 all 16: ND13: Sulfur sources : 47 all 17: ND14: Cld conv mass flx : 0 all 18: ND15: BL mix mass flx : 0 all 19: ND16: LS/Conv prec frac : 0 all 20: ND17: Rainout fraction : 0 all 21: ND18: Washout fraction : 0 all 22: ND19: CH4 loss : 0 all 23: ND21: Optical depths : 47 all 24: ND22: J-Values : 47 1 2 7 8 9 11 13 14 20 44 46 47 49 50 51 58 59 64 65 25: => JV time range : 11 13 26: ND24: E/W transpt flx : 0 all 27: ND25: N/S transpt flx : 0 all 28: ND26: U/D transpt flx : 0 all 29: ND27: Strat NOx,Ox,HNO3 : 0 1 2 7 30: ND28: Biomass emissions : 1 1 4 5 9 10 11 18 19 20 21 26 30 34 35 69 31: ND29: CO sources : 1 all 32: ND30: Land Map : 0 all 33: ND31: Surface pressure : 0 all 34: ND32: NOx sources : 1 all 35: ND33: Column tracer : 0 all 36: ND34: Biofuel emissions : 1 1 4 5 9 10 11 18 19 20 21 37: ND35: Tracers at 500 mb : 0 all 38: ND36: Anthro emissions : 1 1 2 4 5 7 9 10 11 18 19 20 21 69 39: ND37: Updraft scav frac : 47 all 40: ND38: Cld Conv scav loss: 47 all 41: ND39: Wetdep scav loss : 47 all 42: ND41: Afternoon PBL ht : 0 all 43: ND42: SOA concentrations: 0 all 44: ND43: Chem OH, HO2 : 47 all 45: ==> OH/HO2 time range : 0 24 46: ND44: Drydep flx/vel : 1 2 3 7 8 9 11 13 14 15 16 17 20 22 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 47 48 50 55 57 58 59 60 61 62 63 64 47: ND45: Tracer Conc's : 47 all 48: ==> ND45 Time range : 0 24 49: ND46: Biogenic emissions: 1 all 50: ND47: 24-h avg trc conc : 0 all 51: ND52: GAMMA HO2 : 0 all 52: ND53: POPs Emissions : 0 all 53: ND54: Time in t'sphere : 0 all 54: ND55: Tropopause height : 0 all 55: ND56: Lightning flashes : 0 all 56: ND57: Potential T : 0 all 57: ND58: CH4 Emissions : 0 all 58: ND59: TOMAS aerosol emis: 0 all 59: ND60: Wetland Frac : 0 all 60: ND61: TOMAS 3D rate : 0 all 61: ND62: Inst column maps : 0 all 62: ND64: Radiative flux : 0 all 63: ND66: DAO 3-D fields : 0 all 64: ND67: DAO 2-D fields : 0 all 65: ND68: Airmass/Boxheight : 0 all 66: ND69: Surface area : 0 all 67: ND70: Debug output : 0 all 68: ND71: Hourly max ppbv : 0 2 69: ND72: Radiative output : 0 all
For all diagnostics, the column labeled L can be used to turn the diagnostic on or off. Specifying a value other than 0 tells GEOS-Chem the number of levels to save for that diagnostic. For example:
Note that the code is smart enough to prevent you from saving out more vertical levels than there are present for a given diagnostic.
The last column (labeled Tracers to print out for each diagnostic) is where you will specify the tracers to save out for each diagnostic. It is recommended to save out all tracers for a given diagnostic (i.e. specify all in this column), unless you need to save disk space. To specify individual tracers, use the tracer numbers from the Tracer Menu separated by spaces.
Line | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
Header line |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |
Specify the name of the binary punch file. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |
Header line |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |
ND01 (Rn-Pb-Be source) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
ND02 (Rn-Pb-Be decay) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 |
ND03 (Mercury emissions, production & loss) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 |
ND04 (CO2 prod/loss) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |
ND05 (sulfate prod & loss) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 |
ND06 (mineral dust emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 |
ND07 (carbonaceous aerosol emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 |
ND08 (sea salt aerosol emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12 |
ND09 (HCN/CH3CN sources) diagnostic settings NOTE: This diagnostic is more or less obsolete. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
13 |
ND10 (sources, production and loss of H2 and HD) diagnostic settings NOTE: This diagnostic is more or less obsolete. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
14 |
ND11 (sea salt aerosol emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
15 |
ND12 (fraction of each layer in the PBL fraction) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
16 |
ND13 (sulfate aerosol emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
17 |
ND14 (mass flux from cloud convection) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
18 |
ND15 (mass flux from PBL mixing) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
19 |
ND16 (fraction of grid box undergoing large scale & convective precip) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
20 |
ND17 (fraction of soluble tracer lost to rainout) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 |
ND18 (fraction of soluble tracer lost to washout) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
22 |
ND19 (CH4 loss) diagnostic settings for the CH4 simulation only |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
23 |
ND21 (optical depths of cloud, dust, and aerosols) diagnsotic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
24 |
ND22 (J-value photolysis rates) diagnostic settings NOTE: The only tracers that have J-values defined are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
25 |
Specify the averaging period (in local time) for the ND22 diagnostic. In the example above, J-value data from grid boxes where it is between 11:00 and 13:00 local time will be averaged and then saved to disk. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
26 |
ND24 (E/W transport mass fluxes) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
27 |
ND25 (N/S transport mass fluxes) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
28 |
ND26 (vertical transport mass fluxes) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 |
ND27 (flux of tracer from the stratosphere) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
30 |
ND28 (biomass burning emissions) diagnostic settings NOTE: the only tracers that have biomass burning emissions defined are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
31 |
ND29 (sources of CO) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
32 |
ND30 (surface map) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
33 |
ND31 (surface pressure) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
34 |
ND32 (sources of NOx) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
35 |
ND33 (column tracer) diagnostic settings NOTE: This diagnostic is more or less obsolete. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
36 |
ND34 (biofuel emissions) diagnostic settings NOTE: the only tracers that have biofuel emissions defined are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
37 |
ND35 (500 hPa tracers) diagnostic settings NOTE: This is more or less obsolete now. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
38 |
ND36 (anthropogenic emissions) diagnostic settings NOTE: the only tracers that have anthropogenic emissions defined are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
39 |
ND37 (fraction of soluble tracer scavenged in updrafts in cloud convection) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
40 |
ND38 (rainout loss of soluble tracer in convective updrafts) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
41 |
ND39 (washout loss of soluble tracer in convective updrafts) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
42 |
ND41 (afternoon PBL height) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
43 |
ND42 (secondary organic aerosol concentration) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
44 |
ND43 (chemically produced quantities) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
45 |
Specify the averaging period (in local time) for OH and HO2 in the ND43 diagnostic. It is recommended to average OH and HO2 from 00:00 to 24:00 hours local time (i.e. all day long). This is shown in the example above. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
46 |
ND44 (dry deposition fluxes & velocities) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
47 |
ND45 (tracer concentrations) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
48 |
Specify the averaging period (in local time) for tracers in the ND45 diagnostic. It is recommended to average tracers from 00:00 to 24:00 hours local time (i.e. all day long). This is shown in the example above. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
49 |
ND46 (biogenic emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
50 |
ND47 (24-hour tracer concentrations) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
51 |
ND52 (gamma(HO2) for the HO2 uptake by aerosols) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
52 |
ND53 (POPs emissions) diagnostic settings for POPs simulation only |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
53 |
ND54 diagnostic settings (computes the time that a given grid box spends in the troposphere) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
54 |
ND55 (tropopause height) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
55 |
ND56 (lightning flashes) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
56 |
ND57 (Potential temperature) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
57 |
ND58 (CH4 Emissions) diagnostic settings for CH4 and UCX simulations only |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
58 |
ND59 (TOMAS aerosol emissions) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
59 |
ND60 (Wetland Frac) diagnotic settings for CH4 simulation only |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
60 |
ND61 (TOMAS 3D rate) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
61 |
ND62 (instantaneous column maps) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
62 |
ND64 (Radiative flux) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
63 |
ND66 (3-D met fields) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
64 |
ND67 (2-D met fields) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
65 |
ND68 (boxheight & air mass) diagnostic setting. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
66 |
ND69 (grid box surface area) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
67 |
ND70 (turn on debug output) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
68 |
ND71 (Hourly maximum mixing ratio) diagnostic settings |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
69 |
ND72 (Radiative output) diagnostic settings |
We have IDL codes that can create a Planeflight.dat file from the DC8 and P3B navigation files from ARCTAS, ICARTT, and other aircraft missions. Click here for more information.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% PLANEFLIGHT MENU %%%: 02: Turn on plane flt diag? : F 03: Flight track info file : Planeflight.dat.YYYYMMDD 04: Output file name : plane.log.YYYYMMDD
Line | Description |
---|---|
1 |
Header line |
2 |
Set this to T to turn on the plane flight following diagnostic (a.k.a. ND40 diagnostic). Set this switch to F to turn off the plane flight diagnostic. |
3 |
Specify the name of the input file (usually called Planeflight.dat.YYYYMMDD) for the plane flight diagnostic. This file is described below. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. If the plane flight diagnostic is turned on, then GEOS-Chem will look for a new Planeflight.dat.YYYYMMDD file for each YYYYMMDD date. Then it will save out various quantities along the flight track(s) defined within the Planeflight.dat.YYYYMMDD file. |
4 |
Specify the name of the output file (usually called plane.log) for the plane flight diagnostic. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
Note: This diagnostic is somewhat obsolete. We recommend using the ND49 diagnostic to save GEOS-Chem output for a region encompassing your stations, then post-process the output to get the quantities at each station's location.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% ND48 MENU %%% : 02: Turn on ND48 stations : T 03: Station Timeseries file : stations.YYYYMMDD 04: Frequency [min] : 60 05: Number of stations : 3 06: Station #1 (I,J,Lmax,N) : 23 34 1 1 07: Station #2 (I,J,Lmax,N) : 23 34 1 97 08: Station #3 (I,J,Lmax,N) : 23 34 1 98
Line | Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
Header line |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |
Set this to T to turn on the ND48 station timeseries diagnostic. This allows you to save timeseries data of various quantities at specific grid boxes. Set this to F to turn off the ND48 station timeseries diagnostic. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |
Specify the name of the file which will contain output from the ND48 station timeseries diagnostic. This file will be in binary punch format and can be read by GAMAP. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |
Specify the frequency in minutes at which data will be archived by the ND48 station timeseries diagnostic. Recommended values: 60 minutes or 120 minutes. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
Specify the number of ND48 stations at which timeseries data will be saved to disk. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6-8 |
For each ND48 station, you must provide the following information (separated by spaces):
|
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% ND49 MENU %%% : 02: Turn on ND49 diagnostic : T 03: Inst 3-D timeser. file : tsYYYYMMDD.bpch 04: Tracers to include : 94 05: Frequency [min] : 120 06: IMIN, IMAX of region : 70 30 07: JMIN, JMAX of region : 23 46 08: LMIN, LMAX of region : 1 20
Line | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
Header line |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |
Set this to T to turn on the ND49 instantaneous 3D timeseries diagnostic. This allows you to archive instantaneous timeseries data for various quantities from a 3D region of the globe. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |
Specify the name of the file which will contain output from the ND49 station timeseries diagnostic. This file will be in binary punch format and can be read by GAMAP. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |
Specify the ND49 diagnostic quantities to save to disk. Separate each number with a space.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
Specify the frequency (in minutes) at which ND49 will save data for a 3D region of the globe data to disk. Recommended value: 180 min (3 hours). You may save data at a higher temporal resolution (e.g. every 60 min) but this will create HUGE data files! |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 |
Specify IMIN and IMAX, the indices which determine the longitude extent of the 3D region of the globe. Note that these are indices and not actual longitude values. To specify all 360 degrees of longitude, type the following:
Also, note you can wrap around the date line. In the example shown above, IMIN=70 and IMAX=30. This will create a 3D region (assuming 4x5 grid) which starts at 165° E longitude and extends across the date line to 35° W longitude. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 |
Specify JMIN and JMAX, the indices which determine the latitude extent of the 3D region of the globe. Note that these are indices and not actual latitude values. To specify all 180 degrees of latitude, type the following:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |
Specify LMIN and LMAX, the indices which determine the vertical extent of the 3D region of the globe. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% ND50 MENU %%% : 02: Turn on ND50 diagnostic : T 03: 24-hr avg timeser. file : ts_24h_avg.YYYYMMDD.bpch 04: Output as HDF5? : F 05: Tracers to include : 94 06: IMIN, IMAX of region : 1 72 07: JMIN, JMAX of region : 1 46 08: LMIN, LMAX of region : 1 20
Line | Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
Header line |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |
Set this to T to turn on the ND50 24-hour 3D timeseries diagnostic. This allows you save to archive 24-hour averaged data from a 3D region of the globe. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |
Specify the name of the file which will contain output from the ND49 station timeseries diagnostic. This file will be in binary punch format and can be read by GAMAP. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |
To output the ND50 diagnostic quantities in HDF5 format. Note: HDF5 must be installed on
your system for using this option. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
Specify the ND50 diagnostic quantities to save to disk. Separate each number with a space.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 |
Specify IMIN and IMAX, the indices which determine the longitude extent of the 3D region of the globe. Note that these are indices and not actual longitude values. To specify all 360 degrees of longitude, type the following:
Also, note you can wrap around the date line. In the example shown above, IMIN=70 and IMAX=30. This will create a 3D region (assuming 4x5 grid) which starts at 165° E longitude and extends across the date line to 35° W longitude. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 |
Specify JMIN and JMAX, the indices which determine the latitude extent of the 3D region of the globe. Note that these are indices and not actual latitude values. To specify all 180 degrees of latitude, type the following:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |
Specify LMIN and LMAX, the indices which determine the vertical extent of the 3D region of the globe. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% ND51 MENU %%% : 02: Turn on ND51 diagnostic : T 03: LT avg timeseries file : ts_satellite.YYYYMMDD.bpch 04: Output as HDF5? : F 05: Tracers to include : 94 06: GMT Hour for disk write : 0 07: Avg Period [LT hours] : 10 12 08: IMIN, IMAX of region : 1 72 09: JMIN, JMAX of region : 23 46 10: LMIN, LMAX of region : 1 1
Line | Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
Header line |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |
Set this to T to turn on the ND51 "satellite" 3D timeseries diagnostic. ND51 allows you to archive 3D data blocks for various quantities which have been time-averaged between 2 local times. This is useful for comparing model data to sun-synchronous satellites such as GOME or MOPITT which have morning overpass times. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |
Specify the name of the file which will contain output from the ND51 station timeseries diagnostic. This file will be in binary punch format and can be read by GAMAP. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |
To output the ND50 diagnostic quantities in HDF format. Note: HDF5 must be installed on
your system for using this option. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
Specify the ND51 diagnostic quantities to save to disk. Separate each number with a space.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 |
Specify the time of day (in GMT hours) at which the ND51 timeseries file will be written to disk. Recommended value: 0 GMT each day. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 |
Specify the ND51 time averaging window (in local time hours). Only data from grid boxes where the local time falls within this window will be included in the diagnostic averaging process. Recommended values: 10:00 to 12:00 LT. This will cover both GOME and MOPITT overpasses. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |
Specify IMIN and IMAX, the indices which determine the longitude extent of the 3D region of the globe. Note that these are indices and not actual longitude values. To specify all 360 degrees of longitude, type the following:
Also, note you can wrap around the date line. In the example shown above, IMIN=70 and IMAX=30. This will create a 3D region (assuming 4x5 grid) which starts at 165° E longitude and extends across the date line to 35° W longitude. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 |
Specify JMIN and JMAX, the indices which determine the latitude extent of the 3D region of the globe. Note that these are indices and not actual latitude values. To specify all 180 degrees of latitude, type the following:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 |
Specify LMIN and LMAX, the indices which determine the vertical extent of the 3D region of the globe. |
ND51b allows you to output quantities along a second satellite path. ND51b setup is identical to ND51 setup.
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% ND63 MENU %%% : 02: Turn on ND63 diagnostic : T 03: LT avg timeseries file : paranox_ts.YYYYMMDD.bpch 04: Tracers to include : 1 05: Frequency [min] : 120 06: IMIN, IMAX of region : 70 30 07: JMIN, JMAX of region : 23 46
Line | Description | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Header line |
||||||||||||||||||
2 | Set this to T to turn on the ND63 ship timeseries diagnostic. |
||||||||||||||||||
3 | Specify the name of the file which will contain output from the ND63 timeseries diagnostic. This file will be in binary punch format and can be read by GAMAP. You may use date & time tokens YYYY, MM, DD, hh, mm, ss and GEOS-Chem will replace these with the appropriate values. |
||||||||||||||||||
4 | Specify the ND63 diagnostic quantities to save to disk.
|
||||||||||||||||||
5 |
Specify the frequency (in minutes) at which the ND63 timeseries file will be written to disk. |
||||||||||||||||||
6 | Specify IMIN and IMAX, the indices which determine the longitude extent of the 3D region of the globe. Note that these are indices and not actual longitude values. To specify all 360 degrees of longitude, type the following:
Also, note you can wrap around the date line. In the example shown above, IMIN=70 and IMAX=30. This will create a 3D region (assuming 4x5 grid) which starts at 165° E longitude and extends across the date line to 35° W longitude. |
||||||||||||||||||
7 | Specify JMIN and JMAX, the indices which determine the latitude extent of the 3D region of the globe. Note that these are indices and not actual latitude values. To specify all 180 degrees of latitude, type the following:
|
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% PROD & LOSS MENU %%%: 02: Turn on P/L (ND65) diag?: F 03: # of levels for ND65 : 47 04: Save O3 P/L (ND20)? : F 05: Number of P/L families : 7 06: 1st chemical family : POX: O3 NO2 2NO3 PAN PMN PPN HNO4 3N2O5 HNO3 BrO HOBr BrNO2 2BrNO3 MPN 07: 2nd chemical family : LOX: O3 NO2 2NO3 PAN PMN PPN HNO4 3N2O5 HNO3 BrO HOBr BrNO2 2BrNO3 MPN 08: 3rd chemical family : PCO: CO 09: 4th chemical family : LCO: CO 10: 5th chemical family : PBrOx: Br BrO 11: 6th chemical family : PBry: 2Br2 Br BrO HOBr HBr BrNO2 BrNO3 12: 7th chemical family : LBry: 2Br2 Br BrO HOBr HBr BrNO2 BrNO3
Line | Description |
---|---|
1 |
Header line |
2 |
Set this switch to T if you wish to save out chemical production for family tracers (a.k.a. the ND65 diagnostic), or F otherwise. NOTE: The chemical family production & loss diagnostic must be turned off when using the KPP chemical solver. |
3 | Specify the number of levels to save for the chemical
family production & loss diagnostic.
If you are performing a full-chemistry simulation, then you may only archive production and loss data within the troposphere. This is because SMVGEAR does not do chemistry in the stratosphere. For other types of simulations (e.g. tagged Ox, tagged CO), you may archive production and loss data from all levels. |
4 |
Set this switch to T if you wish to archive P(Ox) and L(Ox) rates from a full chemistry simulation into binary punch format, so that these rates can be used to drive a future tagged Ox simulation (a.k.a. ND20 diagnostic). |
5 |
Specify the number of production and loss families to archive. You must list each family below. |
6 |
Entry for the POx chemical production family (assuming we are performing a full-chemistry simulation). The family name comes first and must be followed by a colon. Then you must list the individual species which constitute the POx family. A number in front of a species name is the coefficient by which that species will be multiplied. (You do not have to list the coefficient if it is 1.) Since the family name POx begins with a P, it is interpreted to be a chemical production family. |
7 |
Entry for the LOx chemical production family (assuming we are performing a full-chemistry simulation). You may proceed as described above. Since the family name LOx begins with an L, it is interpreted to be a chemical loss family. |
8 |
Entry for the PCO chemical production family. |
9 |
Entry for the LCO chemical production family. |
10 |
Entry for the PBrOx chemical production family. |
11 |
Entry for the PBry chemical production family. |
12 |
Entry for the LBry chemical production family. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% BENCHMARK MENU %%% : 02: Save benchmark output? : F 03: File w/ initial Ox : Ox.mass.initial 04: File w/ final Ox : Ox.mass.final
Line | Description |
---|---|
1 | Header line |
2 | Set this switch to T if you wish to save out benchmark diagnostics, or F otherwise. This option will save out initial and final tracer masses needed for the 1-month benchmark simulation plotting routines. |
3 | Specify name of file that will contain initial tracer mass. |
4 | Specify name of file that will contain final tracer mass. |
NOTE: This menu controls options for the various GEOS-Chem nested grid simulations. This is an optional menu and may be omitted from input.geos if you are not concerned with these simulations.
For more information, please see:
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% NESTED GRID MENU %%%: 02: Save TPCORE BC's : F 03: Input BCs at 2x2.5? : F 04: Over North America? : F 05: TPCORE NA BC directory : BC_4x5_NA/ 06: Over Europe? : F 07: TPCORE EU BC directory : BC_4x5_EU/ 08: Over China? : F 09: TPCORE CH BC directory : BC_4x5_CH/ 10: Over SE Asia region? : F 11: TPCORE SE BC directory : BC_4x5_SE/ 12: Over Custom Region? : F 13: TPCORE BC directory : BC_4x5/ 14: BC timestep [min] : 180 15: LL box of BC region : 9 26 16: UR box of BC region : 29 41 17: I0_W, J0_W, I0_E, J0_E : 3 3 3 3
Line | Description |
---|---|
1 |
Header line |
2 |
Specify LWINDO (stored in Input_Opt%LWINDO). Set LWINDO to T if you wish to save out boundary conditions from a GEOS-Chem simulation, or F otherwise. Before you run at the nested-grid resolution, you must first save out boundary conditions from a global GEOS-Chem simulation (usually 2° x 2.5°). |
3 | Specify LWINDO2x25 (stored in Input_Opt%LWINDO2x25):
|
4 | Specify LWINDO_NA (stored in Input_Opt%LWINDO_NA). Set LWINDO_NA to T if you wish to perform a GEOS-Chem nested grid simulation over the 0.5° x 0.666 ° or 0.25° x 0.3125° North American domain. |
5 |
Specify TPBC_DIR_NA (stored in Input_Opt%TPBC_DIR_NA). TPBC_DIR_NA is the directory path where you have stored the boundary conditions for your North American nested-grid simulation. |
6 | Specify LWINDO_EU stored in Input_Opt%LWINDO_EU). Set LWINDO_EU to T if you wish to perform a GEOS-Chem nested grid simulation over the 0.5° x 0.666 ° or 0.25° x 0.3125° European domain. |
7 | Specify TPBC_DIR_EU (stored in Input_Opt%TPBC_DIR_EU). TPBC_DIR_EU is the directory path where you have stored the boundary conditions for your European nested-grid simulation. |
8 | Specify LWINDO_CH (stored in Input_Opt%LWINDO_CH). Set LWINDO_CH to T if you wish to perform a GEOS-Chem nested grid simulation over the 0.5° x 0.666 ° or 0.25° x 0.3125° China/SE Asia domain. |
9 | Specify TPBC_DIR_CH (stored in Input_Opt%TPBC_DIR_CH). TPBC_DIR_CH is the directory path where you have stored the boundary conditions for your China/SE Asia nested-grid simulation. |
10 | Specify LWINDO_SE (stored in Input_Opt%LWINDO_SE). Set LWINDO_SE to T if you wish to perform a GEOS-Chem nested grid simulation over the 0.25° x 0.3125° SE Asia region. |
11 | Specify TPBC_DIR_SE (stored in Input_Opt%TPBC_DIR_SE). TPBC_DIR_SE is the directory path where you have stored the boundary conditions for your SE Asia nested-grid simulation. |
12 | Specify LWINDO_CU (stored in Input_Opt%LWINDO_CU). Set LWINDO_CU to T if you wish to perform a GEOS-Chem nested grid simulation a domain that you have customized yourself. |
13 | Specify TPBC_DIR_CU (stored in Input_Opt%TPBC_DIR_CU). TPBC_DIR_CU is the directory path where you have stored the boundary conditions for your custom-domain nested-grid simulation. |
14 |
Specify the frequency in minutes at which the 2° x 2.5° or 4° x 5° boundary conditions will be saved to disk. Recommended value: 180 min (3 hours). |
15 |
Specify I1_BC and J1_BC (stored in tpcore_bc_mod.F). I1_BC and J1_BC are the longitude and latitude indices of the grid box at the LOWER LEFT CORNER of the region in which 4° x 5° boundary conditions are being saved. In the example listed above, I1_BC=51 and J1_BC=21 denotes the grid box (70°E, 10°S). |
16 |
Specify I2_BC and J2_BC (stored in tpcore_bc_mod.F). I2_BC and J2_BC are the longitude and latitude indices of the grid box at the UPPER RIGHT CORNER of the 4° x 5° window region in which boundary conditions are being saved. In the example listed above, I2_BC=67 and J2_BC=37 denotes the grid box (150°E, 54°N). |
17 |
Specify I0_W, J0_W, I0_E, and J0_E (located in source code file tpcore_bc_mod.F). I0_W and J0_W are the nested grid longitude and latitude offsets (in # of boxes) of the which are used to define an inner window reion in which transport is actually done. The region in which transport is done in the window is smaller than the actual size of them nested grid met fields in order to account for the boundary conditions. Please see the comments to the source code file tpcore_bc_mod.F for more information. Recommended values: I0_W=3 and J0_W=3. We have set I0_E=3 and J0_E=3, but for some grids (e.g. SE Asia) you may want to use I0_E=2 and J0_E=2. For more information, please contact the Nested Model Working Group. |
Line numbers are not part of the input.geos file, but have been included for reference.
01: %%% UNIX CMDS MENU %%% : 02: Background symbol : & 03: Redirect symbol : > 04: Unix remove command : rm -f 05: Unix pathname separator : / 06: Unix wildcard character : * 07: Unix unzip command : gzip -dc 08: Zip file suffix : .gz
Line | Description |
---|---|
1 |
Header line |
2 |
Specify BACKGROUND (stored in Input_Opt%BACKGROUND). Set BACKGROUND to the symbol which is used to place Unix jobs in the background. Recommended value: "&". |
3 |
Specify REDIRECT (stored in Input_Opt%REDIRECT). Set REDIRECT to the symbol which is used to redirect output from one file to another. Recommended value: " >". (NOTE: leave a space before the greater than sign.) |
4 |
Specify REMOVE_CMD (stored in Input_Opt%REMOVE_CMD). Set REMOVE_CMD to the string which defines the Unix remove file command. Recommended value: "rm -f". |
5 |
Specify SEPARATOR (stored in Input_Opt%SEPARATOR). Set SEPARATOR to the symbol which is used as the directory path separator. Recommended value: "/". |
6 |
Specify STAR (stored in Input_Opt%STAR). Set STAR to the symbol which is used as the Unix wild card character. Recommended value: "*". |
7 |
Specify UNZIP_CMD (stored in Input_Opt%UNZIP_CMD). Set UNZIP_CMD to the string which defines the file unzipping command. Recommended value: "gzip -dc". |
8 |
Specify ZIP_SUFFIX (stored in Input_Opt%ZIP_SUFFIX). Set ZIP_SUFFIX to the file extension string which is used to denote compressed files. Recommended value: ".gz". |
5.2.2 The HEMCO_Config.rc file
In GEOS-Chem v10-01 and later versions, emissions are read, regridded, and calculated by the HEMCO emissions component. The emission settings are specified in the HEMCO Configuration file (HEMCO_Config.rc).
Please see the following link for detailed information about the HEMCO_Config.rc file:
5.2.3 The Planeflight.dat.YYYYMMDD file
We have IDL codes that can create a Planeflight.dat file from the DC8 and P3B navigation files from ARCTAS, ICARTT, and other aircraft missions. Click here for more information.
Sometimes it is necessary to compare GEOS-Chem output against aircraft observations. The plane flight following diagnostic (a.k.a. ND40 diagnostic) allows you to save out GEOS-Chem diagnostic quantities for grid boxes corresponding to aircraft flight tracks. This prevents you from having to save out huge 3-D punch files with lots of species.
The Planeflight.dat.YYYYMMDD files allow you to specify the diagnostic quantities (tracers, reaction rates, met fields, or chemical species) that you want to print out for a specific longitude, latitude, altitude, and time. A sample Planeflight.dat.YYYYMMDD file is given below. Of course if you have lots of flight track data points, your file will be much longer.
In GEOS-Chem v7-03-06 and higher versions, the plane flight following diagnostic has been modified to be consistent with the method of saving out plane flight data used in the ICARTT mission. If the plane flight following diagnostic is switched on, then it will look for a new Planeflight.dat.YYYYMMDD file each day. If a Planeflight.dat.YYYYMMDD file is found for a given day, then GEOS-Chem will save out diagnostic quantities along the flight track(s) specified within the file.
01: Planeflight.dat
02: Bob Yantosca
03: 26 Apr 2004
04: -------------------------------------------------------------------------------
05: 9 < -- # of variables to be output (list them below, one per line)
06: -------------------------------------------------------------------------------
07: TRA_004
08: O3
09: REA_O1D
10: REA_001
11: REA_299
12: GMAO_TEMP
13: GMAO_ABSH
14: GMAO_SURF
15: AODB_SULF
16: AODC_BLKC
17: -------------------------------------------------------------------------------
18: Now give the times and locations of the flight
19: -------------------------------------------------------------------------------
20: Point Type DD-MM-YYYY HH:MM LAT LON PRESS
21: 1 P3B04 01-01-2003 00:00 42.00 290.00 500.00
22: 2 DC801 01-01-2003 00:00 42.00 290.00 500.00
23: 3 P3B04 01-01-2003 01:00 41.00 290.00 500.00
24: 4 DC801 01-01-2003 01:00 42.00 289.00 500.00
25: 5 P3B04 01-01-2003 02:00 40.00 290.00 500.00
26: 99999 END 0- 0- 0 0 :0 0.00 0.00 0.00
Line | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1-4 |
Header lines with comments |
||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
Number of diagnostic quantities to print out. |
||||||||||||||||||||||||||||||||||||||||||||||||||
6 |
Separator line |
||||||||||||||||||||||||||||||||||||||||||||||||||
7-16 |
Here we list the diagnostic quantities that we want to print out at each flight track location. (For clarity, only a few flight track locations are listed, but in reality, you can list thousands of locations.)
As shown above, you may specify multiple flight tracks in a Planeflight.dat file. The only restriction is that flight track locations must be listed in increasing order of GMT. |
||||||||||||||||||||||||||||||||||||||||||||||||||
17-19 |
Separator Lines |
||||||||||||||||||||||||||||||||||||||||||||||||||
20 |
Comment line which shows you where to line up each column field of the flight track points. |
||||||||||||||||||||||||||||||||||||||||||||||||||
21-25 |
Here we list quantities which define each flight track point. Make sure that each field lines up with the guides in the line above.
GEOS-Chem will loop through each of the flight track points listed in Planeflight.dat and print out each of the diagnostic quantities. GEOS-Chem will pick the nearest model box to each flight track point for comparison. In the future we may introduce a more intelligent interpolation scheme. Note that it is OK to list flight track points from more than one aircraft in the same Planeflight.dat.YYYYMMDD file (as is shown above). However, all flight track points must be listed in increasing order of GMT time or else they will not be interpreted correctly by GEOS-Chem. |
||||||||||||||||||||||||||||||||||||||||||||||||||
26 |
Ending line |
5.3. GEOS-Chem chemistry mechanism files
In this section are included GEOS-Chem input files which only need to be modified every once and a while. These include files which describe the chemistry and photolysis mechanisms. You should only have to modify these files if you wish to change the chemical mechanism or photolysis mechanism.
The mglob.dat file contains convergence criteria and other parameters for SMVGEAR II (and hence is only needed for the full-chemistry simulations). A copy of mglob.dat ships with each of the GEOS-Chem run directories for full-chemistry simulations (e.g. standard, SOA, dicarbonyls).
The three most important parameters in this file are:
NREAD : Number of reactants and products per chemical reaction in globchem.dat file ERRMAXU : Relative error convergence criterion for SMVGEAR II urban domain YLOWU : Absolute error convergence criterion for SMVGEAR II urban domain
NREAD should be 20 if using the standard or SOA chemistry options.
Recommended values: ERRMAXU = 1.0E-01; YLOWU = 1.0E+06
You should not normally have to modify this file, unless the chemistry does not converge at a particular location.
This globchem.dat defines the chemistry mechanism that SMVGEAR II will use. If you feel that something should be changed in this file, please consult first with the GEOS-Chem Oxidants and Chemistry Working Group.
A copy of globchem.dat ships with each of the GEOS-Chem run directories for full-chemistry simulations (e.g. standard, UCX, SOA).
NOTES:
The chemga.dat file defines some aerosol properties for the full-chemistry run with the SMVGEAR solver. This file is read in by SMVGEAR routine chemset.F. You should not modify these without first consulting with the GEOS-Chem Oxidants and Chemistry Working Group.
A copy of chemga.dat ships with each of the GEOS-Chem run directories for full-chemistry simulations (e.g. standard, UCX, SOA).
5.4. GEOS-Chem photolysis mechanism files
GEOS-Chem v10-01 and later versions use the Fast-JX v7.0 photolysis mechanism. Several input files for the FAST-JX photolysis mechanism ship with the GEOS-Chem run directories. You should only have to modify these files if you wish to change the chemical mechanism or photolysis mechanism.
Please see the following link for detailed information about the photolysis mechanism files:
GEOS-Chem will create several files in the user's run directory. Some files include a YYYYMMDD date string as part of the file name. Please see the following link for detailed information on the GEOS-Chem output files: