GEOS-Chem configuration files
- Minimum system requirements
- Downloading source code
- Downloading data directories
- Creating run directories
- Configuring runs
- Output files
- Visualizing and processing output
- Coding and debugging
- Further reading
This page describes the configuration files that are read by GEOS-Chem. Configuration files are automaticaly added to a GEOS-Chem run directory when it is created. The configuration files contain "out-of-the-box" default settings for each type of GEOS-Chem simulation. But you can edit these files to customize your GEOS-Chem simulation with different options.
List of GEOS-Chem configuration files
Below is a table listing GEOS-Chem input files that reside in the run directory.
Configuration files that specify user inputs are located in each GEOS-Chem run directory.
You can edit any of the default settings in these files to change the options that will be used in your GEOS-Chem simulation.
|input.geos||File containing all GEOS-Chem user options, such as:
|HEMCO_Config.rc||Specifies emission inventories that you want to include in GEOS-Chem via the HEMCO emissions component.||The HEMCO User's Guide|
|HEMCO_Diagn.rc||Specifies diagnostic archival options for emissions and related quantities computed by HEMCO emissions component.||The HEMCO User's Guide: Diagnostics.|
|HISTORY.rc||Specifies which GEOS-Chem diagnostics will be archived to netCDF output (for both GEOS-Chem "Classic" and GCHP modes)||Guide to GEOS-Chem History diagnostics|
These are found in the ExtData/CHEM_INPUTS/FAST_JX/ directory structure. Please see Input files for FAST-JX v7.0 for details.
You do not need to modify any of these files unless you wish to change the default photolysis settings.
Configuration files for the pre-defined GEOS-Chem chemical mechanisms are located in the subfolders of the GEOS-Chem source code directory:
You do not need to modify these files unless you wish to update the chemistry mechanism for your own research.
If you need to add new species or reactions, you can modify these globchem.* files and then rebuild the KPP code as described on our FlexChem wiki page.