Difference between revisions of "FlexGrid"

From Geos-chem
Jump to: navigation, search
(Overview)
(FlexGrid implementation plan)
Line 11: Line 11:
 
* Explicitly control each meteorological variables in configuration files to perform various experiments (an interface resembling [[GCHP]])
 
* Explicitly control each meteorological variables in configuration files to perform various experiments (an interface resembling [[GCHP]])
  
=== FlexGrid implementation plan ===
+
== FlexGrid implementation plan ==
  
 
The table below shows the implementation plan for FlexGrid
 
The table below shows the implementation plan for FlexGrid
Line 17: Line 17:
 
{| border=1 cellspacing=0 cellpadding=5  
 
{| border=1 cellspacing=0 cellpadding=5  
 
|-bgcolor="#CCCCCC"
 
|-bgcolor="#CCCCCC"
!width="100px"|Stage
+
!width="250px"|Stage
!width="500px"|Detail
+
!width="250px"|Detail
 
!width="100px"|Status
 
!width="100px"|Status
  

Revision as of 19:02, 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 will 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 unify "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 Unifying compile options"GRID=xxx" by moving all grid size and related parameters to run-time configuration files. No specific plan right now. To do be traded off against the nested-GCHP.