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

Revision as of 21:08, 20 November 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
    • Log files
    • Restart files
    • Diagnostic output files
11. Visualizing and processing output
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).

--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.

--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.

--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).

--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.

Previous | Next | Getting Started with GEOS-Chem