NOTE: This page is being actively edited right now and the information might be incomplete.
FlexGrid documentation by Jiawei Zhuang (firstname.lastname@example.org)
- 1 Overview
- 2 FlexGrid Stage 1 User's Guide
- 3 FlexGrid Stage 2 User's Guide
- 4 FlexGrid implementation details
HEMCO's I/O 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 variable in run-time configuration files to perform metfield experiments (an interface resembling GCHP).
The idea of FlexGrid
In theory, setting up a new nested domain simply requires
- New metfields over that domain
- New regional emission data sets if necessary
- Tunning several domain-dependent or resolution-dependent parameters.
There's no reason that one has to touch the model source code. However, in previous versions, all nested domains were hard-coded so users need to do a lot of tedious coding in order to set up a new domain. The major trouble was metfield I/O, as we assumed that the model grid should exactly match the metfield grid. The solution is HEMCO, which has already been used for regridding emission data sets at multiple grids to the same model grid. Here we just do the reverse -- regrid the same metfield data set to different user-specified domains.
FlexGrid implementation plan
The table below shows the implementation plan for FlexGrid:
|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"||
|Stage 2: Implement custom nested simulations||Enable the compile option "NEST=cu" (custom) to allow custom nested simulations.||
|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.|
FlexGrid for different types of users
According to the availability of meteorological data, users can get different benefits from FlexGrid:
|Only have standard metfields
(e.g. global 4x5, 0.25x0.3125 nested NA)
|Have global native metfields
(For example, GCHP users might store them for global high-resolution runs. We can reuse them for nested simulations.)
FlexGrid Stage 1 User's Guide
Just change the MET option to "flexgrid". This works for any kinds of simulations (no matter global or nested, UCX or tropchem) that use GEOSFP or MERRA2 metfields.
For example, the original compile command for the 4x5 standard run is:
make -j4 UCX=yes CHEM=standard GRID=4x5 MET=geosfp
Now simple use
make -j4 UCX=yes CHEM=standard GRID=4x5 MET=flexgrid