Leaf area indices in GEOS-Chem: Difference between revisions
Line 16: | Line 16: | ||
GEOS-Chem users had the option to use either LAI data from the AVHRR satellite instrument or the [[MODIS leaf area indices|MODIS satellite instrument]]. Individual sets of <tt>lai*.global</tt> files were prepared for both AVHRR LAI and MODIS LAI data. Users could select either AVHRR LAI or MODIS LAI with a switch in the <tt>input.geos</tt> file. Customary usage is to select the MODIS LAI data, [[MEGAN biogenic emissions#Use MEGAN with MODIS leaf area indices|for reasons explained HERE]]. | GEOS-Chem users had the option to use either LAI data from the AVHRR satellite instrument or the [[MODIS leaf area indices|MODIS satellite instrument]]. Individual sets of <tt>lai*.global</tt> files were prepared for both AVHRR LAI and MODIS LAI data. Users could select either AVHRR LAI or MODIS LAI with a switch in the <tt>input.geos</tt> file. Customary usage is to select the MODIS LAI data, [[MEGAN biogenic emissions#Use MEGAN with MODIS leaf area indices|for reasons explained HERE]]. | ||
--[[User:Bmy|Bob Y.]] 14:22, 12 April 2012 (EDT) | |||
=== LAI used by MEGAN biogenic emissions === | === LAI used by MEGAN biogenic emissions === | ||
Line 22: | Line 24: | ||
When modifications were made for the [[GEOS-5]] 0.5° x 0.666° nested grids, separate subroutines were added into <tt>lai_mod.f</tt> to read from LAI data sets that were specifically regridded to each 0.5° x 0.666° nested grid window (China/SE Asia, N. America, and Europe). This adds another layer of complexity on top of an somewhat already overburdened code. | When modifications were made for the [[GEOS-5]] 0.5° x 0.666° nested grids, separate subroutines were added into <tt>lai_mod.f</tt> to read from LAI data sets that were specifically regridded to each 0.5° x 0.666° nested grid window (China/SE Asia, N. America, and Europe). This adds another layer of complexity on top of an somewhat already overburdened code. | ||
--[[User:Bmy|Bob Y.]] 14:22, 12 April 2012 (EDT) | |||
=== LAI used by the mercury simulation === | === LAI used by the mercury simulation === | ||
In the [[Mercury|GEOS-Chem mercury simulation]], the routine which computes Hg emission from soils (<tt>SOILEMIS</tt>, in module <tt>land_mercury_mod.F</tt>) uses the daily averaged LAI (stored in the <tt>ISOLAI</tt>, in <tt>lai_mod.F</tt>) in order to attenuate solar radiation. As mentioned [[#LAI used by MEGAN biogenic emissions|above]], this LAI data is first read in from disk at 1° x 1° resolution and then regridded to the current GEOS-Chem resolution. | In the [[Mercury|GEOS-Chem mercury simulation]], the routine which computes Hg emission from soils (<tt>SOILEMIS</tt>, in module <tt>land_mercury_mod.F</tt>) uses the daily averaged LAI (stored in the <tt>ISOLAI</tt>, in <tt>lai_mod.F</tt>) in order to attenuate solar radiation. As mentioned [[#LAI used by MEGAN biogenic emissions|above]], this LAI data is first read in from disk at 1° x 1° resolution and then regridded to the current GEOS-Chem resolution. | ||
--[[User:Bmy|Bob Y.]] 14:22, 12 April 2012 (EDT) | |||
=== Issues that needed to be resolved === | === Issues that needed to be resolved === | ||
Line 34: | Line 40: | ||
Finally, to facilitate simulations at ultra-fine horizontal resolution, we will eventually adopt the [[Olson land map#Olson 2001 land map|Olson 2001 land map]], which has a native resolution of 0.25° x 0.25°. We will also use an updated version of the MODIS LAI data at 0.25 x 0.25 resolution. We need a flexible mechanism that will allow us to switch between LAI data at different native horizontal resolutions. | Finally, to facilitate simulations at ultra-fine horizontal resolution, we will eventually adopt the [[Olson land map#Olson 2001 land map|Olson 2001 land map]], which has a native resolution of 0.25° x 0.25°. We will also use an updated version of the MODIS LAI data at 0.25 x 0.25 resolution. We need a flexible mechanism that will allow us to switch between LAI data at different native horizontal resolutions. | ||
--[[User:Bmy|Bob Y.]] 14:22, 12 April 2012 (EDT) | |||
== Implementation of an updated LAI code == | == Implementation of an updated LAI code == |
Revision as of 18:22, 12 April 2012
On this page we provide an overview of how leaf area index (LAI) data is used in GEOS-Chem. Leaf area index is defined as the total leaf surface area divided by the total surface area of a grid box (typical units are: cm2 leaf cm-2 GEOS-Chem grid box).
Also be sure to see our MODIS leaf area indices page, which describes the leaf area indices derived from the MODIS satellite instrument.
Overview
Prior to the official release of GEOS-Chem v9-01-03, GEOS-Chem used leaf area index data in the following manner:
LAI used by dry deposition and soil NOx emissions
As of this writing (April 2012), GEOS-Chem currently uses leaf area index (LAI) data from separate sources. The dry deposition and soil NOx emissions modules utilize the data stored in ASCII files named lai*.global. These files (one per month) are created (using offline IDL routines) for each specific GEOS-Chem grid configuration (i.e. 4° x 5°, 2° x 2.5°, and 0.5° x 0.666° nested grids, etc.). The lai*.global files are read from disk by routines readlai.F and rdlai.F, which save the LAI data into arrays named XLAI (in CMN_DEP_mod.F) and XYLAI (in CMN_VEL_mod.F).
The XLAI and XYLAI arrays store the leaf area index as a function of Olson land type (cf Olson 1992 land map). The XLAI array has dimensions (IIPAR,JJPAR,NTYPE), where IIPAR is the number of longitudes in the horizontal grid, JJPAR is the number of latitudes, and NTYPE is the number of individual Olson land types per each GEOS-Chem grid box. The XYLAI array contained the same data as in XYLAI, but for historical reasons was dimensioned with only one spatial dimension: (IIPAR*JJPAR,NTYPE).
Please note that there is a direct correspondence between the LAI data stored in the lai*.global files (and saved into XLAI and XYLAI arrays) and the Olson land map. Therefore, if you are using the Olson 1992 land map (native resolution 0.5° x 0.5°, default in GEOS-Chem), then you must also use LAI data at 0.5° x 0.5° native resolution. On the other hand, if you are using the Olson 2001 land map (native resolution 0.25° x 0.25°), then you must also use LAI data at 0.25° x 0.25° resolution.
GEOS-Chem users had the option to use either LAI data from the AVHRR satellite instrument or the MODIS satellite instrument. Individual sets of lai*.global files were prepared for both AVHRR LAI and MODIS LAI data. Users could select either AVHRR LAI or MODIS LAI with a switch in the input.geos file. Customary usage is to select the MODIS LAI data, for reasons explained HERE.
--Bob Y. 14:22, 12 April 2012 (EDT)
LAI used by MEGAN biogenic emissions
The MEGAN biogenic emissions module also relies on MODIS LAI data. Routine RDISOLAI (in lai_mod.F) reads MODIS LAI at 1° x 1° native resolution from files in binary punch format. The LAI data is regridded on-the-fly to GEOS-Chem resolution and stored in arrays named ISOLAI (daily LAI), PMISOLAI (LAI for previous month), MISOLAI (LAI for this month), and NMISOLAI (LAI for next month), all in lai_mod.F. The MEGAN module gets the MODIS LAI data directly from these arrays.
When modifications were made for the GEOS-5 0.5° x 0.666° nested grids, separate subroutines were added into lai_mod.f to read from LAI data sets that were specifically regridded to each 0.5° x 0.666° nested grid window (China/SE Asia, N. America, and Europe). This adds another layer of complexity on top of an somewhat already overburdened code.
--Bob Y. 14:22, 12 April 2012 (EDT)
LAI used by the mercury simulation
In the GEOS-Chem mercury simulation, the routine which computes Hg emission from soils (SOILEMIS, in module land_mercury_mod.F) uses the daily averaged LAI (stored in the ISOLAI, in lai_mod.F) in order to attenuate solar radiation. As mentioned above, this LAI data is first read in from disk at 1° x 1° resolution and then regridded to the current GEOS-Chem resolution.
--Bob Y. 14:22, 12 April 2012 (EDT)
Issues that needed to be resolved
These different sources of LAI data (i.e. one data set stored in the lai*.global files at GEOS-Chem resolution, one data stored in binary files at 1° x 1° native resolution, and the special data sets for the 0.5° x 0.666° nested grids) present an inconsistency that should be resolved as GEOS-Chem development continues to advance.
Furthermore, for the Grid-independent GEOS-Chem project we must migrate away from ASCII files (which prevent efficient interfacing with external GCMs). We also cannot assume any particular horizontal grid, since that is now to be specified by the external GCM. Therefore, we must instead read the LAI data from disk at the same native resolution, and from this, populate the arrays that are used by the dry deposition, soil NOx emissions, and MEGAN biogenic emissions modules.
Finally, to facilitate simulations at ultra-fine horizontal resolution, we will eventually adopt the Olson 2001 land map, which has a native resolution of 0.25° x 0.25°. We will also use an updated version of the MODIS LAI data at 0.25 x 0.25 resolution. We need a flexible mechanism that will allow us to switch between LAI data at different native horizontal resolutions.
--Bob Y. 14:22, 12 April 2012 (EDT)
Implementation of an updated LAI code
To resolve the issues discussed in the preceding section, the GEOS-Chem Support Team has created the following new GEOS-Chem modules:
- olson_landmap_mod.F90
- Used to read in the Olson land cover map directly from netCDF files at its native resolution (0.5° x 0.5° if using Olson 1992, 0.25° x 0.25° if using Olson 2001). This removes the need for obsolete ASCII files. Please see our Olson land map wiki page for a complete description.
- modis_lai_mod.F90
- This module replaces the existing GEOS-Chem module lai_mod.F. Using the Olson land map information supplied by olson_landmap_mod.F90, the routines in modis_lai_mod.F90 perform the following tasks:
- Read MODIS LAI data from netCDF files at its native resoluton (either 0.5° x 0.5° or 0.25° x 0.25°, depending on which Olson land map version is used)
- Regrid MODIS LAI data to the current GEOS-Chem resolution on-the-fly.
- Populate the XLAI array for backwards compatibility with the existing legacy Dry deposition and Soil NOx emissions modules.des.
- Populate LAI arrays that are needed for MEGAN biogenic emissions and the Mercury simulation.
- mapping_mod.F90
- Used to pass land type and regridding information from olson_landmap_mod.F90 to modis_lai_mod.F90.
For the MEGAN biogenic emissions and Mercury simulations, we have now replaced variables from lai_mod.F with the corresponding variables from modis_lai_mod.F90 as shown in this table:
Variable | Type | Which stores this quantity | In this module | Is now replaced by | In this module |
---|---|---|---|---|---|
ISOLAI | array | Daily interpolated leaf area index [cm2 cm-2] | lai_mod.F | GC_LAI | modis_lai_mod.F90 |
PMISOLAI | array | Previous month's leaf area index, as read from disk [cm2 cm-2] | lai_mod.F | GC_LAI_PM | modis_lai_mod.F90 |
MISOLAI | array | Current month's leaf area index, as read from disk [cm2 cm-2] | lai_mod.F | GC_LAI_CM | modis_lai_mod.F90 |
NMISOLAI | array | Next month's leaf area index, as read from disk [cm2 cm-2] | lai_mod.F | GC_LAI_NM | modis_lai_mod.F90 |
DAYS_BTW_M | scalar | # of days between the start of 2 successive LAI months | lai_mod.F | DAYS_BTW_MON | modis_lai_mod.F90 |
We have also taken the opportunity to replace the obsolete XYLAI array with XLAI, which will allow us to retire the obsolete legacy code module CMN_VEL_mod.F. We will keep the XLAI array for compatibility with the dry deposition module for the foreseeable future (at least until the dry deposition module is modernized).
--Bob Y. 14:15, 12 April 2012 (EDT)
Validation
We have validated that the new LAI scheme generates identical XLAI arrays w/r/t the old scheme. This causes the dry deposition and soil NOx emissions to behave in precisely the same way as before.
The arrays GC_LAI etc. differ from the ISOLAI etc. arrays slightly (but generally agree to within 0.001). This is due to the fact that the ISOLAI arrays were regridded from 1° x 1° native resolution, but now we are regridding from much finer resolution (either 0.5° x 0.5° or 0.25° x 0.25°). See our Validation section below.