Difference between revisions of "GEOS-Chem diagnostic output files"

From Geos-chem
Jump to: navigation, search
(ObsPack diagnostic output)
Line 351: Line 351:
 
== Satellite timeseries diagnostic output in bpch format ==
 
== Satellite timeseries diagnostic output in bpch format ==
  
 +
{| border=1 cellspacing=0 cellpadding=5
 +
|-valign="top" bgcolor="#CCCCCC"
 +
!width="400px"|Timeseries file name
 +
!width="100px"|Format
 +
!width="400px"|Collections
 +
!width="150px"|Created by
 +
 +
|-valign="top"
 +
|<tt>ts_satellite.YYYYMMDDhh.bpch</tt>
 +
|bpch
 +
|Diagnostics requested in the [[List_of_diagnostics_archived_to_bpch_format#ND51_and_ND51b:_Satellite_timeseries|ND51 MENU and/or ND51b MENU of <tt>input.geos</tt>]].
 +
|
 +
*All simulations
 +
 +
|}
  
  
 
----
 
----
 
'''''[[GEOS-Chem restart files|Previous]] | [[Guide_to_visualization_and_analysis_tools_for_GEOS-Chem|Next]] | [[Getting Started with GEOS-Chem]]'''''
 
'''''[[GEOS-Chem restart files|Previous]] | [[Guide_to_visualization_and_analysis_tools_for_GEOS-Chem|Next]] | [[Getting Started with GEOS-Chem]]'''''

Revision as of 18:19, 17 December 2019

Previous | Next | Getting Started with GEOS-Chem

  1. Minimum system requirements
  2. Downloading source code
  3. Downloading data directories
  4. Creating run directories
  5. Configuring runs
  6. Compiling
  7. Running
  8. Output files
  9. Visualizing and processing output
  10. Coding and debugging
  11. 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 Created by Added/Removed
GEOSChem.AdvFluxVert.YYYYMMDD_hhmmz.nc4 netCDF AdvFluxVert
  • All simulations
  • Typically used only with benchmark
GEOSChem.AerosolMass.YYYYMMDD_hhmmz.nc4 netCDF AerosolMass
  • All full-chemistry simulations
  • Aerosol-only simulations
GEOSChem.Aerosols.YYYYMMDD_hhmmz.nc4 netCDF Aerosols
  • All full-chemistry simulations
  • Aerosol-only simulations
GEOSChem.BoundaryConditions.YYYYMMDD_hhmmz.nc4 netCDF BoundaryConditions
  • Can be created by all simulations
  • Can be read in by nested-grid simulations
GEOSChem.Budget.YYYYMMDD_hhmmz.nc4 netCDF Budget
  • All simulations
GEOSChem.CH4.YYYYMMDD_hhmmz.nc4 netCDF CH4
  • CH4 simulations
GEOSChem.CloudConvFlux.YYYYMMDD_hhmmz.nc4 netCDF CloudConvFlux
  • All simulations
GEOSChem.ConcAboveSfc.YYYYMMDD_hhmmz.nc4 netCDF ConcAboveSfc
  • Full-chemistry simulations
GEOSChem.ConcAfterChem.YYYYMMDD_hhmmz.nc4 netCDF ConcAfterChem
  • All full-chemistry simulations
  • CH4 simulation
GEOSChem.DryDep.YYYYMMDD_hhmmz.nc4 netCDF DryDep
  • All simulations with dry-depositing species
GEOSChem.Jvalues.YYYYMMDD_hhmmz.nc4 netCDF JValues
  • All full-chemistry simulations
GEOSChem.KppDiags.YYYYMMDD_hhmmz.nc4 netCDF KppDiags
  • All full-chemistry simulations
GEOSChem.LevelEdgeDiags.YYYYMMDD_hhmmz.nc4 netCDF LevelEdgeDiags
  • All simulations
GEOSChem.MercuryChem.YYYYMMDD_hhmmz.nc4 netCDF MercuryChem
  • Hg simulation
  • tagHg simulation
GEOSChem.MercuryEmis.YYYYMMDD_hhmmz.nc4 netCDF MercuryEmis
  • Hg simulation
  • tagHg simulation
GEOSChem.MercuryOcean.YYYYMMDD_hhmmz.nc4 netCDF MercuryOcean
  • Hg simulation
  • tagHg simulation
GEOSChem.POPs.YYYYMMDD_hhmmz.nc4 netCDF POPs
  • Hg simulation
  • tagHg simulation
GEOSChem.ProdLoss.YYYYMMDD_hhmmz.nc4 netCDF ProdLoss
  • All full-chemistry simulations
  • Aerosol-only simulation
  • tagCO simulation
  • tagO3 simulation
GEOSChem.RadioNuclide.YYYYMMDD_hhmmz.nc4 netCDF RadioNuclide
  • TransportTraces simulation
GEOSChem.SpeciesConc.YYYYMMDD_hhmmz.nc4 netCDF SpeciesConc
  • All simulations
GEOSChem.StateChm.YYYYMMDD_hhmmz.nc4 netCDF StateChm
  • All simulations
GEOSChem.StateMet.YYYYMMDD_hhmmz.nc4 netCDF StateMet
  • All simulations
GEOSChem.Transport.YYYYMMDD_hhmmz.nc4 netCDF Transport
  • All simulations
  • Typicaly only used with benchmark
GEOSChem.WetLossConv.YYYYMMDD_hhmmz.nc4 netCDF WetLossConv
  • All simulations with soluble species
GEOSChem.WetLossLS.YYYYMMDD_hhmmz.nc4 netCDF WetLossLS
  • All simulations with soluble species

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

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

NOTE: To use the Planeflight Diagnostic, you must compile GEOS-Chem with the BPCH_DIAG=y option.

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

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

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

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