GEOS-Chem diagnostic output files

From Geos-chem
Revision as of 21:34, 8 December 2020 by Bmy (Talk | contribs)

Jump to: navigation, search

Previous | Next | Getting Started with GEOS-Chem

  1. Minimum system requirements
  2. Installing required software
  3. Configuring your computational environment
  4. Downloading source code
  5. Downloading data directories
  6. Creating run directories
  7. Configuring runs
  8. Compiling
  9. Running
  10. Output files
  11. Python tools for use with GEOS-Chem
  12. Coding and debugging
  13. Further reading


On this page, we list the files that are generated by GEOS-Chem's various diagnostic packages.

History diagnostics output

The following files, which correspond to the default History diagnostic collections, will be created in the OutputDir/ folder in your GEOS-Chem run directory. You can prevent any of these files from being created by commenting out the collection name in the HISTORY.rc configuration file. You can also add your own new collections (i.e. requesting species concentrations for both time-averaged and instantaneous averaging modes) by updating HISTORY.rc. For more information, please see our Guide to GEOS-Chem History diagnostics.

In the table below, YYYYMMDD and hhmms corresponds to the simulation date and time at which the file was created. The z indicates UTC (sometimes called "Zulu" time).

History diagnostic file name Format Collection For simulation(s) Added/Removed
GEOSChem.AdvFluxVert.YYYYMMDD_hhmmz.nc4 netCDF AdvFluxVert
  • fullchem_benchmark
  • Added in 12.6.0
GEOSChem.AerosolMass.YYYYMMDD_hhmmz.nc4 netCDF AerosolMass
  • fullchem
  • aerosol
  • Added in 12.0.0
GEOSChem.Aerosols.YYYYMMDD_hhmmz.nc4 netCDF Aerosols
  • fullchem
  • aerosol
  • Added in 12.0.0
GEOSChem.BoundaryConditions.YYYYMMDD_hhmmz.nc4 netCDF BoundaryConditions
  • can be created by: all simulations
  • can be read by: nested-grid simulations
  • Added in 12.4.0
GEOSChem.Budget.YYYYMMDD_hhmmz.nc4 netCDF Budget
  • all simulations
  • Added in 12.1.0
GEOSChem.CH4.YYYYMMDD_hhmmz.nc4 netCDF CH4
  • CH4
  • tagCH4
  • Added in 12.1.0
GEOSChem.CloudConvFlux.YYYYMMDD_hhmmz.nc4 netCDF CloudConvFlux
  • all simulations
  • Added in 12.0.0
GEOSChem.ConcAboveSfc.YYYYMMDD_hhmmz.nc4 netCDF ConcAboveSfc
  • fullchem
  • Added in 12.6.0
GEOSChem.ConcAfterChem.YYYYMMDD_hhmmz.nc4 netCDF ConcAfterChem
  • fullchem
  • CH4
  • tagCH4
  • Added in 12.0.0
GEOSChem.DryDep.YYYYMMDD_hhmmz.nc4 netCDF DryDep
  • simulations w/ drydep species
  • Added in 12.0.0
GEOSChem.Jvalues.YYYYMMDD_hhmmz.nc4 netCDF JValues
  • fullchem
  • Added in 12.0.0
GEOSChem.KppDiags.YYYYMMDD_hhmmz.nc4 netCDF KppDiags
  • fullchem
  • Added in 12.7.0
GEOSChem.LevelEdgeDiags.YYYYMMDD_hhmmz.nc4 netCDF LevelEdgeDiags
  • all simulations
  • Added in 12.0.0
GEOSChem.MercuryChem.YYYYMMDD_hhmmz.nc4 netCDF MercuryChem
  • Hg
  • tagHg
  • Added in 12.0.0
GEOSChem.MercuryEmis.YYYYMMDD_hhmmz.nc4 netCDF MercuryEmis
  • Hg
  • tagHg
  • Added in 12.0.0
GEOSChem.MercuryOcean.YYYYMMDD_hhmmz.nc4 netCDF MercuryOcean
  • Hg
  • tagHg
  • Added in 12.0.0
GEOSChem.POPs.YYYYMMDD_hhmmz.nc4 netCDF POPs
  • Hg
  • tagHg
  • Added in 12.0.0
GEOSChem.Metrics.YYYYMMDD_hhmmz.nc4 netCDF Metrics
  • fullchem
  • CH4
  • tagCH4
  • Added in 13.0.0
GEOSChem.ProdLoss.YYYYMMDD_hhmmz.nc4 netCDF ProdLoss
  • fullchem
  • aerosol
  • tagCO
  • tagO3
  • Added in 12.0.0
GEOSChem.RadioNuclide.YYYYMMDD_hhmmz.nc4 netCDF RadioNuclide
  • TransportTracers
  • Added in 12.0.0
GEOSChem.SpeciesConc.YYYYMMDD_hhmmz.nc4 netCDF SpeciesConc
  • all simulations
  • Added in 12.0.0
GEOSChem.StateChm.YYYYMMDD_hhmmz.nc4 netCDF StateChm
  • all simulations
  • Added in 12.0.0
GEOSChem.StateMet.YYYYMMDD_hhmmz.nc4 netCDF StateMet
  • all simulations
  • Added in 12.0.0
GEOSChem.Transport.YYYYMMDD_hhmmz.nc4 netCDF Transport
  • Typically used for fullchem_benchmark
  • Moved to StateMet in 13.0.0
  • Added in 12.2.0
  • Removed in 13.0.0
GEOSChem.WetLossConv.YYYYMMDD_hhmmz.nc4 netCDF WetLossConv
  • simulations w/ wetdep species
  • Added in 12.0.0
GEOSChem.WetLossLS.YYYYMMDD_hhmmz.nc4 netCDF WetLossLS
  • simulations w/ wetdep species
  • Added in 12.0.0

HEMCO diagnostic ouptut

The HEMCO diagnostic output files will be created in the OutputDir/ folder in your GEOS-Chem run directory. For more information, please see our The HEMCO User's Guide: Diagnostics.

In the table below, YYYYMMDD and hhmms corresponds to the simulation date and time at which the file was created.

HEMCO diagnostic file name Format Collections Created by
HEMCO_diagnostics.YYYYMMDDhhmm.nc netCDF Diagnostic quantities requested in HEMCO_Diagn.rc
  • All simulations

--Bob Yantosca (talk) 16:07, 13 December 2019 (UTC)

Planeflight diagnostic output

By default, the planefight diagnostic output files will be created in your top-level run directory. You can change this setting by modifying the output file name setting in the Planeflight Menu of input.geos. For more information, please see our Planeflight diagnostic page.

In the table below, YYYYMMDD corresponds to the simulation date and time at which the file was created.

Planeflight diagnostic file name Format Collections Created by
plane.log.YYYYMMDD text Point diagnostics requested in Planeflight.dat
  • All simulations

ObsPack diagnostic output

By default, the ObsPack output files will be created in your top-level run directory. You can change this setting by modifying the output file name setting in the ObsPack Menu of input.geos. For more information, please see our ObsPack diagnostic page.

In the table below, YYYYMMDD and hhmms corresponds to the simulation date and time at which the file was created. The z indicates UTC (sometimes called "Zulu" time).

Obspack diagnostic file name Format Collections Created by
GEOSChem.ObsPack.YYYYMMDD_hhmmz.nc4 netCDF Point diagnostics at locations specified in an ObsPack format netCDF file
  • All simulations

--Bob Yantosca (talk) 16:41, 13 December 2019 (UTC)

Satellite timeseries diagnostic output in bpch format

NOTE: To use the satellite timeseries diagnostics, you must compile GEOS-Chem with the BPCH_DIAG=y option.

By default, the satellite timeseries files will be created in your top-level run directory. You can change by modifying the output file name setting in the ND51 MENU and/or ND51b MENU of input.geos.

In the table below, YYYYMMDD and hhmms corresponds to the simulation date and time at which the file was created.

Timeseries file name Format Collections Created by
ts_satellite.YYYYMMDDhh.bpch bpch Diagnostics requested in the ND51 MENU and/or ND51b MENU of input.geos.
  • All simulations



Previous | Next | Getting Started with GEOS-Chem