Difference between revisions of "GEOS-Chem output files"

From Geos-chem
Jump to: navigation, search
(Output files created by GCHP)
(Additional output files created by GCHP)
 
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page contains information about files produced by GEOS-Chem simulations, including diagnostic data and restart files used for initial conditions.  For information about the input files that ship with the GEOS-Chem run directories, please see our [[GEOS-Chem Input Files|''GEOS-Chem Input Files'' wiki page]].
+
__FORCETOC__
 +
'''''[[Running_GEOS-Chem|Previous]] | [[GEOS-Chem log files|Next]] | [[Getting Started with GEOS-Chem]]'''''
 +
#[[Minimum system requirements for GEOS-Chem|Minimum system requirements]]
 +
#[[Installing required software]]
 +
#[[Configuring your computational environment]]
 +
#[[Downloading GEOS-Chem source code|Downloading source code]]
 +
#[[Downloading GEOS-Chem data directories|Downloading data directories]]
 +
#[[Creating GEOS-Chem run directories|Creating run directories]]
 +
#[[GEOS-Chem configuration files|Configuring runs]]
 +
#[[Compiling GEOS-Chem|Compiling]]
 +
#[[Running GEOS-Chem|Running]]
 +
#<span style="color:blue">'''Output files'''</span>
 +
#*[[GEOS-Chem log files|Log files]]
 +
#*[[GEOS-Chem restart files|Restart files]]
 +
#*[[GEOS-Chem diagnostic output files|Diagnostic output files]]
 +
#[[Python tools for use with GEOS-Chem]]
 +
#[[GEOS-Chem_coding_and_debugging|Coding and debugging]]
 +
#[[GEOS-Chem_overview#Further_reading|Further reading]]
  
== List of files created by GEOS-Chem ==
 
  
Each time you compile and run GEOS-Chem, several files are written in the GEOS-Chem run directory.  The table below provides a comprehensive list of all GEOS-Chem output files:
+
== Output files created by GEOS-Chem ==
  
<blockquote>NOTE: Several of the files listed in the tables below (e.g. log files and diagnostic output files) contain the <tt>.mp</tt> or <tt>.sp</tt> suffix:
+
GEOS-Chem creates several output files.  They can be grouped into 3 categoriesPlease click on each link to find more information.
*<tt>.mp</tt> ("multi-processor") denotes GEOS-Chem was compiled with [[Parallelizing GEOS-Chem|OpenMP parallelization]].
+
*<tt>.sp</tt> ("single-processor") denotes that GEOS-Chem was compiled without OpenMP parallelization.
+
*The <tt>.mp</tt> or <tt>.sp</tt> suffixes are typically applied upon successful completion of a GEOS-Chem simulationIf a GEOS-Chem simulation dies prematurely, certain files might lack the <tt>.mp</tt> or <tt>.sp</tt> suffix.
+
</blockquote>
+
 
+
=== Log files ===
+
  
 
{| border=1 cellspacing=0 cellpadding=5  
 
{| border=1 cellspacing=0 cellpadding=5  
|-bgcolor="#CCCCCC"
+
|-bgcolor="#CCCCCC" valign="top"
!width="325px"|File(s)
+
!width="200px"|Output file type
!width="75px"|Format
+
!width="800px"|Description
!width="500px"|Description
+
!width="200px"|Notes
+
  
|-valign="top"
+
|-valign+"top"
|[[#The lastbuild file|<tt>lastbuild.mp</tt> or<br><tt>lastbuild.sp</tt>]]
+
|[[GEOS-Chem log files|'''Log files''']]
|Text
+
|Log files redirect the output of GEOS-Chem <tt>PRINT*</tt> or <tt>WRITE</tt> statements to a file.  You can check the log files for an "echo-back" of simulation options, as well as error messages.
|'''The lastbuild file'''Contains a summary of all of the options that were used to build the GEOS-Chem executable.  This file is created each time you compile GEOS-Chem.
+
|Please include this file when [[Submitting GEOS-Chem support requests|submitting a GEOS-Chem support request]].
+
  
|-valign="top"
+
|-valign+"top"
|[[#GEOS-Chem log file|<tt>GC_*.log</tt> or<br><tt>GC_*.log.mp</tt> or <br><tt>GC_*.log.sp</tt>]]
+
|[[GEOS-Chem restart files|'''Restart files''']]
|Text
+
|Restart files contain the initial conditions that are used to start a GEOS-Chem simulation.  Restart files are also written to disk at the end of each GEOS-Chem simulation, and can be used to initialize the subsequent simulation stage.
|'''The GEOS-Chem log file.''' Contains an "echo-back" of all input options that were specified in <tt>input.geos</tt>, the list of diagnostic quantities that are being archived, the list of files that are being read, and information about the operations that are being done at each GEOS-Chem timestep.  If you run dies with an error, a detailed error message should be printed here.
+
|Please include this file when [[Submitting GEOS-Chem support requests|submitting a GEOS-Chem support request]].
+
  
|-valign="top"
+
|-valign+"top"
|[[#HEMCO log file|<tt>HEMCO.log</tt> or<br><tt>HEMCO.log.mp</tt> or<br><tt>HEMCO.log.sp</tt>]]
+
|[[GEOS-Chem diagnostic output files|'''Diagnostic output files''']]  
|Text
+
|Diagnostic output files contain quantities that are archived from a GEOS-Chem simulation.  These can be used in your scientific analysis.
|'''The HEMCO log file.''' Contains information about how emissions, met fields, and other relevant data are read from disk and processed by HEMCO for input into GEOS-Chem.
+
|Please include this file when [[Submitting GEOS-Chem support requests|submitting a GEOS-Chem support request]].
+
 
+
|-valign="top"
+
|<tt>slurm-JOBID.out</tt>
+
|Text
+
|'''The job output file'''.  If you used a batch scheduler such as SLURM, PBS, LSF, etc. to submit your GEOS-Chem simulation, then output from the Unix stdout and/or stderr streams may be printed to this fileThis file may contain important error messages.
+
|Please include this file when [[Submitting GEOS-Chem support requests|submitting a GEOS-Chem support request]].
+
  
 
|}
 
|}
  
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 16:19, 30 November 2018 (UTC)
+
== Further reading ==
 
+
#''[[Guide to netCDF in GEOS-Chem]]''
=== Restart files ===
+
#''[[Guide to GEOS-Chem diagnostics]]''
 
+
{| border=1 cellspacing=0 cellpadding=5
+
|-bgcolor="#CCCCCC"
+
!width="325px"|File(s)
+
!width="75px"|Format
+
!width="500px"|Description
+
!width="200px"|Notes
+
 
+
|-valign="top"
+
|[[#GEOS-Chem restart files|<tt>GEOSChem.Restart.YYYYMMDD_hhmmz.nc4</tt>]]
+
|netCDF
+
|'''The GEOS-Chem restart file.''' Contains species concentrations that are read in at simulation startup. 
+
 
+
GEOS-Chem writes a restart file at the end of each simulation.  This allows a long simulation to be split into several individal run stages..
+
 
+
For example, the restart file that was created at 00:00 UTC on August 1, 2016 is named: <tt>GEOSChem.Restart.20160801_0000z.nc4</tt>. The z indicates "Zulu" or "Z" time, which is another name for UTC.
+
 
+
For more information, please see [[GEOS-Chem restart files|our ''GEOS-Chem restart files'' wiki page]].
+
|
+
 
+
|-valign="top"
+
|<tt>HEMCO_restart.YYYYMMDDhhmm.nc</tt>
+
|netCDF
+
|'''The HEMCO restart file'''.  The [[HEMCO|HEMCO emissions component]] will save out certain quantities (mostly pertaining to soil NOx and biogenic emissions) in order to facilitate long GEOS-Chem simulations with several run stages. 
+
|
+
 
+
|}
+
 
+
=== Diagnostic output files ===
+
 
+
{| border=1 cellspacing=0 cellpadding=5
+
|-bgcolor="#CCCCCC"
+
!width="325px"|File(s)
+
!width="75px"|Format
+
!width="500px"|Description
+
!width="200px"|Notes
+
 
+
|-valign="top"
+
|[[#GEOS-Chem netCDF diagnostic files|<tt>GEOSChem.*.YYYYMMDD_hhmmz.nc4</tt>]]
+
|netCDF
+
|'''GEOS-Chem netCDF diagnostic (aka "History") output.''' NetCDF files containing diagnostic output from GEOS-Chem, for each of the various [[List of diagnostics archived to netCDF format|diagnostic collections]].  The data may be either time-averaged or instantaneous.  You can specify which collections to archive in the <tt>HISTORY.rc</tt> input file.
+
|Available in [[GEOS-Chem 12]]
+
 
+
|-valign="top"
+
|[[#HEMCO diagnostic files|<tt>HEMCO_diagnostics.YYYYMMDDhhmm</tt>]]
+
|NetCDF
+
|'''HEMCO diagnostic files'''.  Files containing diagnostic quantities that are archived directly by the [[HEMCO|HEMCO emissions component]].
+
|
+
 
+
|-valign="top"
+
|[[ObsPack diagnostic#Output file format|<tt>GEOSChem.ObsPack.YYYYMMDD_hhmmz.nc4</tt>]]
+
|NetCDF
+
|'''ObsPack diagnostic files'''.  Files containing diagnostic quantities that are archived directly by the optional [[ObsPack diagnostic]].
+
|Available in [[GEOS-Chem 12#12.2.0|GEOS-Chem 12.2.0]] and later versions
+
 
+
|-valign="top"
+
|[[#GEOS-Chem binary punch diagnostic files|<tt>trac_avg.{met}_{grid}_{sim}.YYYYMMDDhh</tt>]]
+
|BPCH
+
|'''GEOS-Chem "binary punch" (aka "bpch") diagnostic data'''.  For several years, this was the standard file format for GEOS-Chem diagnostics.
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|-valign="top"
+
|[[#GEOS-Chem plane-flight diagnostic|<tt>plane.log.YYYYMMDD</tt>]]
+
|Text
+
|File containing from the [[Planeflight diagnostic|'''GEOS-Chem plane-flight diagnostic output''']].
+
|
+
 
+
|-valign="top"
+
|<tt>stations.YYYYMMDDhh</tt>
+
|BPCH
+
|Diagnostic output file that contains [[List_of_diagnostics_archived_to_bpch_format#ND48:_Station_timeseries|'''ND48 station timeseries output''']] as specified in <tt>input.geos</tt>.
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|-valign="top"
+
|<tt>tsYYYYMMDDhh.bpch</tt>
+
|BPCH
+
|Diagnostic output file that contains [[List_of_diagnostics_archived_to_bpch_format#ND49:_Instantaneous_timeseries|'''ND49 instantaneous timeseries output ''']] as specified in <tt>input.geos</tt>.
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|-valign="top"
+
|<tt>ts_24hr_avg.YYYYMMDDhh.bpch</tt>
+
|BPCH
+
|Diagnostic output file that contains [[List_of_diagnostics_archived_to_bpch_format#ND50:_24h_average_timeseries|'''ND50 24-hour average timeseries output''']] as specified in <tt>input.geos</tt>.
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|-valign="top"
+
|<tt>ts_satellite.YYYYMMDDhh.bpch</tt>
+
|BPCH
+
|Diagnostic output file that contains [[List_of_diagnostics_archived_to_bpch_format#ND51_and_ND51b:_Satellite_timeseries|'''ND51 local-time-average (satellite) timeseries output''']] as specified in <tt>input.geos</tt>.
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|-valign="top"
+
|<tt>paranox_ts.YYYYMMDDhh.bpch</tt>
+
|BPCH
+
|Diagnostic output file that contains [[List_of_diagnostics_archived_to_bpch_format#ND63:_Ship_emission_diagnostics|'''ND63 ship timeseries output''']] as specified in <tt>input.geos</tt>.
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|-valign="top"
+
|[[#diaginfo.dat and tracerinfo.dat files|<tt>diaginfo.dat</tt> and <tt>tracerinfo.dat</tt>]]
+
|Text
+
|Contains metadata used by GAMAP to read data in binary punch format.ostic output file that contains
+
|We will soon retire the bpch file format in favor of netCDF diagnostics.
+
 
+
|}
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:23, 11 January 2019 (UTC)
+
 
+
=== Output files created by GCHP ===
+
 
+
Please see the [[GCHP_Output_Data|GCHP Output Data wiki page]] for information about GCHP output.
+
 
+
--[[User:Lizzie Lundgren|Lizzie Lundgren]] ([[User talk:Lizzie Lundgren|talk]]) 18:38, 10 May 2019 (UTC)
+
 
+
== In-depth descriptions of GEOS-Chem output files ==
+
 
+
=== diaginfo.dat and tracerinfo.dat files ===
+
 
+
''NOTE: For the time being, you can still archive diagnostics to binary punch (aka bpch) file format in [[GEOS-Chem 12]].  But note that the bpch output will be removed in a future GEOS-Chem version.''
+
 
+
The metadata for GEOS-Chem diagnostics in binary punch format is stored in two different text files: <tt>diaginfo.dat</tt> and <tt>tracerinfo.dat</tt>.  Please see [http://acmg.seas.harvard.edu/gamap/doc/Chapter_7.html Chapter 7 of ''The GAMAP User's Guide''] for more information about these files.
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:22, 30 November 2018 (UTC)
+
 
+
=== GEOS-Chem binary punch diagnostic files ===
+
 
+
''NOTE: For the time being, you can still archive diagnostics to binary punch (aka bpch) file format in [[GEOS-Chem 12]].  But note that the bpch output will be removed in a future GEOS-Chem version.''
+
 
+
For a complete description of all available GEOS-Chem diagnostics in binary punch format, please see [[List of diagnostics archived to bpch format|our ''List of diagnostics archived to bpch format'' wiki page]].
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:08, 30 November 2018 (UTC)
+
 
+
=== GEOS-Chem netCDF diagnostic files ===
+
 
+
For a complete description of netCDF diagnostic collections that are available via the GEOS-Chem History Component, please see [[List of diagnostics archived to netCDF format|our ''List of diagnostics archived to netCDF format'' wiki page]].
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:40, 11 January 2019 (UTC)
+
 
+
=== GEOS-Chem log file ===
+
 
+
The GEOS-Chem log file contains an "echo-back" of all input options, as well as a list of files that are being read in, and operations that are being done at each timestep.  Here is an example log file from a recent 1-month benchmark simulation:
+
 
+
*************  S T A R T I N G  4 x 5  G E O S - C H E M  *************
+
+
===> Mode of operation        : GEOS-Chem "Classic"
+
===> GEOS-Chem version        : 12.1.0
+
===> Compiler                  : Intel Fortran Compiler (aka ifort)
+
===> Driven by meteorology    : GMAO GEOS-FP (on native 72-layer vertical grid)
+
===> ISORROPIA ATE package    : ON
+
===> Parallelization w/ OpenMP : ON
+
===> Binary punch diagnostics  : ON
+
===> netCDF diagnostics        : ON
+
===> netCDF file compression  : SUPPORTED
+
+
===> SIMULATION START TIME: 2018/11/21 10:38 <===
+
+
===============================================================================
+
G E O S - C H E M  U S E R  I N P U T
+
+
READ_INPUT_FILE: Reading input.geos
+
+
SIMULATION MENU
+
---------------
+
Start time of run          : 20160701 000000
+
End time of run            : 20160801 000000
+
Run directory              : ./
+
Data Directory              : /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/
+
CHEM_INPUTS directory      : /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/CHEM_INPUTS/
+
Resolution-specific dir    : GEOS_4x5/
+
Is this a nested-grid sim?  :    F
+
Global offsets I0, J0      :    0    0
+
+
TIMESTEP MENU
+
---------------
+
Transport/Convection [sec]  :  600
+
Chemistry/Emissions  [sec]  :  1200
+
+
... etc ...
+
 
+
If your simulation stopped with an error, a detailed error message should also appear in the GEOS-Chem log file.
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:13, 30 November 2018 (UTC)
+
 
+
=== GEOS-Chem plane-flight diagnostic output ===
+
 
+
Please see [[Planeflight_diagnostic|our ''Planeflight diagnostic'' wiki page]] for more information about the input and output file formats used by the GEOS-Chem plane-flight diagnostic.
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:38, 30 November 2018 (UTC)
+
 
+
=== ObsPack diagnostic output ===
+
 
+
In [[GEOS-Chem 12#12.2.0|GEOS-Chem 12.2.0]] and later, you can use the optional [[ObsPack diagnostic]] to archive GEOS-Chem quantities at specified coordinates (e.g. lon/lat/alt) to netCDF files.  You might find ObsPack useful if you need to get GEOS-Chem output for locations where you have either station data or flight track data. 
+
 
+
For more information about the ObsPack file structure, [[ObsPack diagnostic#Output file format|please follow this link]].
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:46, 11 January 2019 (UTC)
+
 
+
=== GEOS-Chem restart files ===
+
 
+
Please see [[GEOS-Chem restart files|our ''GEOS-Chem restart files'' wiki page]] for more information.
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:08, 30 November 2018 (UTC)
+
 
+
=== HEMCO diagnostic output files ===
+
 
+
Pease see the [[The HEMCO User's Guide#Diagnostics|'''Diagnostics''' section of ''The HEMCO User's Guide]] for more information.
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:08, 30 November 2018 (UTC)
+
 
+
=== HEMCO log file ===
+
 
+
The [[HEMCO|HEMCO emissions component]] also produces a log file, which is named <tt>HEMCO.log</tt>.  The HEMCO log file contains information about how emissions, met fields, and other relevant data are read from disk and processed for input into GEOS-Chem.
+
 
+
''(NOTE: When your simulation finishes successfully, the HEMCO.log file is automatically renamed to either <tt>HEMCO.log.mp</tt> (if OpenMP parallelization is turned on) or <tt>HEMCO.log.sp</tt> (if OpenMP parallelization is turned off).  But if your run dies with an error, the HEMCO log file will not have been renamed.)''
+
 
+
Here is a sample <tt>HEMCO.log</tt> file from a recent 1-month benchmark simulation (edited for brevity):
+
 
+
-------------------------------------------------------------------------------
+
Using HEMCO v2.1.010   
+
-------------------------------------------------------------------------------
+
Registering HEMCO species:
+
Species NO
+
Species O3
+
Species PAN
+
Species CO
+
... etc ...
+
+
-------------------------------------------------------------------------------
+
-------------------------------------------------------------------------------
+
Use air-sea flux emissions (extension module)
+
    - Use species:
+
    - DMS          25
+
    - ACET          9
+
    - ALD2          11
+
-------------------------------------------------------------------------------
+
Use ParaNOx ship emissions (extension module)
+
    - Use the following species: (MW, emitted as HEMCO ID)
+
      NO  : 30.00    1
+
      NO2 : 46.00  64
+
      O3  : 48.00    2
+
      HNO3: 63.00    7
+
READ_LUT_NCFILE: Reading /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/HEMCO/PARANOX/v2015-02/ship_plume_lut_02ms.nc
+
READ_LUT_NCFILE: Reading /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/HEMCO/PARANOX/v2015-02/ship_plume_lut_06ms.nc
+
READ_LUT_NCFILE: Reading /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/HEMCO/PARANOX/v2015-02/ship_plume_lut_10ms.nc
+
READ_LUT_NCFILE: Reading /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/HEMCO/PARANOX/v2015-02/ship_plume_lut_14ms.nc
+
READ_LUT_NCFILE: Reading /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/HEMCO/PARANOX/v2015-02/ship_plume_lut_18ms.nc
+
-------------------------------------------------------------------------------
+
Use lightning NOx emissions (extension module)
+
  - Use species NO->          1
+
  - Use OTD-LIS factors from file?  T
+
  - Use GEOS-5 flash rates:  F
+
  - Use scalar scale factor:    1.000000
+
  - Use gridded scale field: none
+
      - INIT_LIGHTNOX: Reading /n/holylfs/EXTERNAL_REPOS/GEOS-CHEM/gcgrid/data/ExtData/HEMCO/LIGHTNOX/v2014-07/light_dist.ott2010.dat
+
-------------------------------------------------------------------------------
+
Use soil NOx emissions (extension module)
+
    - NOx species            : NO          1
+
    - NOx scale factor      :    1.000000
+
    - NOx scale field        : none
+
    - Use fertilizer NOx    :  T
+
    - Fertilizer scale factor:  6.800000090152025E-003
+
-------------------------------------------------------------------------------
+
-------------------------------------------------------------------------------
+
Use DEAD dust emissions (extension module)
+
Use the following species (Name: HcoID):
+
  DST1:          38
+
  DST2:          39
+
  DST3:          40
+
  DST4:          41
+
  Global mass flux tuning factor:  8.328599999999999E-004
+
-------------------------------------------------------------------------------
+
-------------------------------------------------------------------------------
+
Use sea salt aerosol emissions (extension module)
+
  Accumulation aerosol: SALA:          42
+
  - size range      :  1.000000000000000E-002  0.500000000000000
+
  Coarse aerosol      : SALC:          43
+
  - size range      :  1.000000000000000E-002  0.500000000000000
+
  - wind scale factor:    1.00000000000000
+
-------------------------------------------------------------------------------
+
Use MEGAN biogenic emissions (extension module)
+
-------------------------------------------------------------------------------
+
  - This is instance            1
+
  - Use the following species:
+
    Isoprene  = ISOP          6
+
    Acetone    = ACET          9
+
    C3 Alkenes = PRPE          18
+
    Ethene    = C2H4          -1
+
    ALD2      = ALD2          11
+
    EOH        = EOH          96
+
  SOA-Precursor = SOAP          94
+
  SOA-Simple  = SOAS          95
+
  --> Isoprene scale factor is    1.00000000000000
+
  --> Use CO2 inhibition on isoprene option  T
+
  --> Global atmospheric CO2 concentration :    390.000000000000      ppmv
+
  --> Normalize LAI by PFT:  T
+
  - MEGAN monoterpene option enabled
+
    CO        = CO          4
+
      a-,b-pinene    = MTPA          70
+
      Other monoterp.= MTPO          72
+
      Limonene      = LIMO          71
+
      Sesquiterpenes = SESQ        184
+
-------------------------------------------------------------------------------
+
Use GFED extension
+
    - Use GFED-4              :  T
+
    - Use daily scale factors :  F
+
    - Use hourly scale factors:  F
+
    - Hydrophilic OC fraction :  0.5000000
+
    - Hydrophilic BC fraction :  0.2000000
+
    - POG1 fraction          :  0.4900000
+
    - SOAP fraction          :  1.3000000E-02
+
    - Emit GFED species NO    as model species NO
+
      --> Will use scale factor:    1.000000
+
      --> Will use scale field : none
+
    - Emit GFED species CO    as model species CO
+
      --> Will use scale factor:    1.050000
+
      --> Will use scale field : none
+
    ... etc...
+
 
+
-------------------------------------------------------------------------------
+
HEMCO v2.1.010 FINISHED.
+
Warnings (level 1 or lower):  25386
+
-------------------------------------------------------------------------------
+
 
+
For more information, please see [[The HEMCO User's Guide|''The HEMCO User's Guide'']].
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:24, 30 November 2018 (UTC)
+
 
+
=== HEMCO restart files ===
+
 
+
Pease see the [[The HEMCO User's Guide#Restart_variables|'''Restart variables''' section of ''The HEMCO User's Guide]] for more information.
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:08, 30 November 2018 (UTC)
+
 
+
=== The lastbuild file ===
+
 
+
The GEOS-Chem "Classic" compilation sequence generates a file that contains all of the options that were used to build the executable file.  This file is named either <tt>lastbuild.mp</tt> (if [[Parallelizing GEOS-Chem|OpenMP parallelization]] is turned on) or <tt>lastbuild.sp</tt> (if OpenMp parallelization is turned off). 
+
 
+
Here is a sample <tt>lastbuild.mp</tt> file from a recent 1-month benchmark simulation:
+
 
+
<tt>LAST BUILD INFORMATION:
+
  CODE_DIR    : /n/home05/msulprizio/GC/Code.Dev
+
  CODE_BRANCH  : dev/12.1.0
+
  <span style="color:green">LAST_COMMIT  : Revert to reading I3 met fields each hour instead of once per day</span>
+
  COMMIT_DATE  : Wed Nov 21 09:07:51 2018 -0500
+
  <span style="color:red">VERSION      : 12.1.0</span>
+
  VERSION_TAG  : GC_12.1.0
+
  <span style="color:blue">MET          : geosfp</span>
+
  <span style="color:orange">GRID        : 4x5</span>
+
  <span style="color:purple">SIM          : benchmark</span>
+
  <span style="color:brown">NEST        : n</span>
+
  TRACEBACK    : y
+
  BOUNDS      : n
+
  DEBUG        : n
+
  FPE          : n
+
  NO_ISO      : n
+
  NO_REDUCED  : y
+
  CHEM        : Standard
+
  TOMAS12      : n
+
  TOMAS15      : n
+
  TOMAS30      : n
+
  TOMAS40      : n
+
  RRTMG        : n
+
  MASSCONS    : n
+
  TIMERS      : 1
+
  TAU_PROF    : n
+
  BPCH_DIAG    : y
+
  NC_DIAG      : y
+
  <span style="color:magenta">COMPILER    : ifort 17.0.4</span>
+
  Datetime    : 2018/11/21 10:33</tt>     
+
 
+
The [[GEOS-Chem Support Team]] will need to see the following fields of the lastbuild file in order to [[Submitting GEOS-Chem support requests|assist you in resolving bugs or technical issues]] that you might encounter.
+
 
+
{| border=1 cellpadding=5 cellspacing=0
+
 
+
|-valign="top"
+
!width="125px" bgcolor="#CCCCCC"|Item
+
!width="875px" bgcolor="#CCCCCC"|Description
+
 
+
|-valign="top"
+
|<tt><span style="color:green">LAST_COMMIT</span></tt>
+
|The location (aka "commit") of your source code in the Git version history.  (You can use the <tt>gitk</tt> browser to view the Git version history.)
+
 
+
|-valign="top"
+
|<tt><span style="color:red">VERSION</span></tt>
+
|The GEOS-Chem version number.
+
 
+
|-valign="top"
+
|<tt><span style="color:blue">MET</span></tt>
+
|The meteorology that is driving GEOS-Chem (e.g. geosfp, merra2).
+
 
+
|-valign="top"
+
|<tt><span style="color:orange">GRID</span></tt>
+
|The horizontal grid (e.g. 4&deg; x 5&deg; , 2&deg; x 2.5&deg;, 0.25&deg; x 0.3125&deg;, 0.5&deg; x 0.625&deg;) that your simulation uses.
+
 
+
|-valign="top"
+
|<tt><span style="color:purple">SIM</span></tt>
+
|The name of your GEOS-Chem simulation (e.g. Standard, Benchmark, CH4, Rn-Pb-Be, Hg, etc.).
+
 
+
|-valign="top"
+
|<tt><span style="color:brown">NEST</span></tt>
+
|The nested region that your simulation uses (e.g. as, af, ch, na, eu, etc.).  This only applies to nested-grid simulations.
+
 
+
|-valign="top"
+
|<tt><span style="color:magenta">COMPILER</span></tt>
+
|The compiler version that you used to build the GEOS-Chem executable file.
+
 
+
|}
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:09, 30 November 2018 (UTC)
+
 
+
== Previous issues that are now resolved ==
+
 
+
=== Enable compression in netCDF-4 output files ===
+
 
+
<span style="color:green">'''''This update was included in [[GEOS-Chem v11-02#v11-02a|v11-02a]] (approved 12 May 2017).'''''</span>
+
 
+
For more information about this issue, please see [[The_NcdfUtilities_package#Enable_compression_in_netCDF-4_output_files|this post on our ''The NcdfUtilities package'' wiki page]].
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:50, 24 May 2018 (UTC)
+
 
+
=== Improve write speed of netCDF output files ===
+
 
+
<span style="color:green">'''''This update was included in [[GEOS-Chem v11-01#v11-01 public release|GEOS-Chem v11-01 public release]]'''''</span>
+
  
For more information about this issue, please see [[The_NcdfUtilities_package#Improve_write_speed_of_netCDF_output_files|this post on our ''The NcdfUtilities package'' wiki page]].
 
  
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 19:05, 8 March 2017 (UTC)
+
----
 +
'''''[[Running_GEOS-Chem|Previous]] | [[GEOS-Chem log files|Next]] | [[Getting Started with GEOS-Chem]]'''''

Latest revision as of 22:14, 8 December 2020

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


Output files created by GEOS-Chem

GEOS-Chem creates several output files. They can be grouped into 3 categories. Please click on each link to find more information.

Output file type Description
Log files Log files redirect the output of GEOS-Chem PRINT* or WRITE statements to a file. You can check the log files for an "echo-back" of simulation options, as well as error messages.
Restart files Restart files contain the initial conditions that are used to start a GEOS-Chem simulation. Restart files are also written to disk at the end of each GEOS-Chem simulation, and can be used to initialize the subsequent simulation stage.
Diagnostic output files Diagnostic output files contain quantities that are archived from a GEOS-Chem simulation. These can be used in your scientific analysis.

Further reading

  1. Guide to netCDF in GEOS-Chem
  2. Guide to GEOS-Chem diagnostics



Previous | Next | Getting Started with GEOS-Chem