Difference between revisions of "GCHP Output Data"

From Geos-chem
Jump to: navigation, search
Line 7: Line 7:
#[[GCHP_Basic_Example_Run|Basic Example Run]]
#[[GCHP_Basic_Example_Run|Basic Example Run]]
#[[Running_GCHP|Advanced Run Examples]]
#[[Running_GCHP|Configuring a Run]]
#<span style="color:blue">'''Output Data'''</span>
#<span style="color:blue">'''Output Data'''</span>
#[[Developing_GCHP|Developing GCHP]]
#[[Developing_GCHP|Developing GCHP]]

Revision as of 19:47, 8 August 2018

Previous | Next | Getting Started with GCHP

  1. Hardware and Software Requirements
  2. Downloading Source Code
  3. Obtaining a Run Directory
  4. Setting Up the GCHP Environment
  5. Compiling
  6. Basic Example Run
  7. Configuring a Run
  8. Output Data
  9. Developing GCHP
  10. Run Configuration Files

GCHP Output

List of Output Files

Running GCHP produces several output data and log files. The table belows lists what files to expect. All of these files are deleted if you run make cleanup_output within the run directory.

Filename Description
OutputDir/GCHP.{collection}.YYYYMMDD_HHmmz.nc4 Cubed sphere output data. Note that you can change the filename format for any collection within HISTORY.rc.
gchp.log Log file containing GCHP standard output including what would typically go to a GEOS-Chem Classic log file. Note that you can change this log file's name when you run GCHP by editing it in your run script.
PET00000.GEOSCHEMchem.log Can be ignored.
HEMCO.log Log file generated by HEMCO. This file is also output when running GEOS-Chem classic.
cap_restart MAPL output text file containing GCHP run end time to be used as the next run's start time if doing multi-segmented runs. If not doing multi-segmented runs then this file should be deleted prior to rerunning so that start information in CAP.rc is used instead.
*.rcx Contains basic information about each diagnostic collection.
EGRESS Can be ignored.
trac_avg.gchp_c24_standard.YYYYMMDDHHmm Can be ignored. All GCHP data output diagnostics data is stored in the OutputDir subdirectory.

Diagnostic Data

GCHP diagnostic data is in netCDF-4 format and is stored in the OutputDir directory within your run directory. The output filename format is GCHP.collection.YYYYMMDD_HHmmz.nc4 where one or more collection names are configured in the output configuration file HISTORY.rc. You are free to create as many additional collections with any names you choose by adding them to HISTORY.rc. Any 2D or 3D arrays stored in State_Met, State_Chm, or State_Diag can be included in a History collection.

Restart Files

To be added

Data Visualization and Post-Processing

Each collection output file contains data on the cubed sphere grid at the resolution of your run. You can conservatively regrid to lat-lon for post-run analysis using one of the tools described below.

  1. Python package xESMF developed by Jiawei Zhuang (Harvard). This package is a wrapper for the ESMF python regridding interface.
  2. Jupyter Notebook developed by Lizzie Lundgren (Harvard). This notebook contains example python code to regrid and compare GCHP and GEOS-Chem netcdf diagnostics using Jiawei Zhuang's xESMF package.
  3. FORTRAN tool CSRegridTool developed by Sebastian Eastham (MIT). This tool regrids cubed sphere and lat-lon netcdf files.
  4. Matlab package CSGrid developed by Sebastian Eastham (MIT). This package is a data analysis and visualization suite for both cubed sphere and lat-lon GEOS-Chem data.

Please note that we also have a GEOS-Chem python tutorial written by Jiawei Zhuang available on the GEOS-Chem GitHub site and we are in the process of migrating GAMAP IDL benchmarking code to python in the gcpy package currently in development. We will no longer maintain IDL code for post-processing of GEOS-Chem output once we completely replace binary diagnostics with netcdf diagnostics in GEOS-Chem Classic.

Previous | Next | GCHP Home