Difference between revisions of "FlexGrid"

From Geos-chem
Jump to: navigation, search
(FlexGrid implementation plan)
(FlexGrid implementation plan)
Line 35: Line 35:
 
|-valign="top"
 
|-valign="top"
 
|Stage 3: Grid-independent GEOS-Chem classic
 
|Stage 3: Grid-independent GEOS-Chem classic
|Unifying compile options "GRID=xxx" by moving all grid size parameters and resolution-dependent parameters to run-time configuration files.
+
|Unify compile options "GRID=xxx" by moving all grid size parameters and resolution-dependent parameters to run-time configuration files.
 
|No specific plan right now. Need to be traded off against the nested-GCHP development.
 
|No specific plan right now. Need to be traded off against the nested-GCHP development.

Revision as of 19:18, 29 June 2017

NOTE: This page is being actively edited right now and the information might be incomplete.

FlexGrid documentation by Jiawei Zhuang (jiaweizhuang@g.harvard.edu)

Overview

FlexGrid is a new functionality in GEOS-Chem v11-02 to unify all metfield I/O routines by HEMCO.

HEMCO's interface and regridding&cropping capability allow users to

  • Set up a nested simulation over any custom domains without changing model's source code.
  • Explicitly control each meteorological variables in configuration files to perform various experiments (an interface resembling GCHP).

FlexGrid implementation plan

The table below shows the implementation plan for FlexGrid:

Stage Detail Status
Stage 1: Read metfields by HEMCO Enable the compile option "MET=flexgrid" to read any NetCDF-format metfields through HEMCO. This unifies "MET=geosfp" and "MET=merra2"
  • Will be included in v11-02
Stage 2: Implement custom nested simulations Enable the compile option "NEST=cu" (custom) to allow custom nested simulations.
  • Will be included in v11-02
Stage 3: Grid-independent GEOS-Chem classic Unify compile options "GRID=xxx" by moving all grid size parameters and resolution-dependent parameters to run-time configuration files. No specific plan right now. Need to be traded off against the nested-GCHP development.