GEOS-FP implementation details: Difference between revisions
| Line 50: | Line 50: | ||
In other areas of GEOS-Chem the changes are more involved. Below we provide a description of the areas of GEOS-Chem that were modified for MERRA: | In other areas of GEOS-Chem the changes are more involved. Below we provide a description of the areas of GEOS-Chem that were modified for MERRA: | ||
=== Top-level directory === | |||
{| border=1 cellspacing=0 cellpadding=5 | |||
|- bgcolor="#CCCCCC" | |||
!width="175px"|File | |||
!width="800px"|Modifications made | |||
|- | |||
|Makefile_header.mk | |||
| | |||
*Starting with [[GEOS-Chem v9-02 benchmark history#v9-02o|GEOS-Chem v9-02o]], we now use Makefile variables to set the various C-preprocessor switches. In particular: | |||
**<tt>MET=___</tt> selects the met field type( <tt>gcap, geos4, geos5, geosfp, merra</tt>) | |||
**<tt>GRID=___</tt> selects the horizontal grid (<tt>4x5, 2x25, 05x0666, 025x03125</tt>) | |||
**<tt>NEST=___</tt> specifies the nested-grid (<tt>CH, EU, NA, SE</tt>) | |||
|} | |||
--[[User:Bmy|Bob Y.]] 13:39, 7 November 2013 (EST) | |||
=== Headers directory === | === Headers directory === | ||
Revision as of 18:39, 7 November 2013
GEOS-FP was originally given the designation GEOS-5.7.1, which was later updated to GEOS-5.7.2. Currently, GEOS-FP is being produced with version 5.11.0 of the GEOS Data Assimilation System (aka GEOS-DAS). This means that the "5.7.x" nomenclature is no longer correct. For this reason, we shall refer to this product as GEOS-FP from now on. (Bob Yantosca, 21 Aug 2013)
On this page we list the necessary modifications to GEOS-Chem for compatibility with the GEOS-FP meteorological data.
Overview
The GEOS-FP data product (aka GEOS5-FP) is the newest version of the operational meteorological data produced by NASA/GMAO. Overall, the structure of GEOS-FP is very similar to MERRA. Therefore, within GEOS-Chem we can (for the most part) treat GEOS-FP in the same way as we do for the MERRA meteorology.
Key similarities to MERRA
The following aspects of GEOS-FP are identical to the older GEOS-5.2.0 operational data product.
- The GEOS-FP vertical grid (72 hybrid levels) is identical to that of both MERRA and GEOS-5.2.0.
- By and large, the same data fields that were in the MERRA product are also contained in GEOS-FP:
- GEOS-FP provides the same time-invariant fields (FRLAKE, FRLAND, FRLANDIC, FROCEAN, PHIS) as MERRA
- The same correction that was applied to the MERRA SNOMAS (snow mass) field has also been applied to the GEOS-FP SNOMAS field.
- GEOS-FP contains the same precipitation fields (DQRCU, DQRLSAN, PFICU, PFILSAN, PFLCU, PFLLSAN, REEVAPCN, REEVAPLSAN) as MERRA. This means that we can use the MERRA wet deposition algorithms with the GEOS-FP data.
- The GEOS-FP time archiving is identical to that of MERRA ...
- ... with one exception: GEOS-FP instantaneous data is archived every 3 hours, as opposed to 6 hours in MERRA.
--Bob Y. 09:46, 21 August 2013 (EDT)
Key differences from MERRA
The following aspects of GEOS-FP differ from the MERRA operational data product:
- All GEOS-FP data are placed on a horizontal grid of 0.25° x 0.3125°.
- MERRA data fields are placed on three different horizontal grids (0.5° x 0.666°, 1° x 1.25° and 1.25° x 1.25°).
- All GEOS-FP data are placed on the 72-level hybrid grid.
- Some MERRA fields were only available on a 42-level pressure grid (thus requiring interpolation).
- The following data GEOS-FP data fields differ from the corresponding MERRA fields:
- RH is now a 3-hour time-averaged field, as opposed to a 6-hour instantaneous field in MERRA.
- QV and T are now instantaneous 3-hour fields, as opposed to 3-hour time-averaged fields in MERRA.
- The 3-D precipitation fields now make the (e.g. DQIDTMST, DQVDTMST, DQLDTMST, etc.) obsolete. We no longer archive these.
- We have chosen to save the processed GEOS-FP data in netCDF format, as opposed to GEOS-Chem binary format.
--Bob Y. 09:47, 21 August 2013 (EDT)
Required coding changes in GEOS-Chem
NOTE: This section is still under construction. Not all tables have yet been updated.
As noted in the section above, the similarities between MERRA and GEOS-FP (especially of the vertical grids) means that in most cases we can just treat MERRA in the same way as for GEOS-5. In many areas of the code, the coding changes are straightforward and simply involve an extension of C-preprocessor statements such as:
#if defined( GEOS_5 ) || defined( MERRA )
to
#if defined( GEOS_5 ) || defined( MERRA ) || defined( GEOS_FP )
In other areas of GEOS-Chem the changes are more involved. Below we provide a description of the areas of GEOS-Chem that were modified for MERRA:
Top-level directory
| File | Modifications made |
|---|---|
| Makefile_header.mk |
|
--Bob Y. 13:39, 7 November 2013 (EST)
Headers directory
The following modifications for GEOS-FP were made in the Headers/ directory:
| File | Modifications made |
|---|---|
| CMN_SIZE_mod.F |
|
| gigc_state_met_mod.F90 |
|
--Bob Y. 13:35, 7 November 2013 (EST)
GeosUtil directory
The following modifications for GEOS-5.7.2 were made in the GeosUtil/ directory:
| File | Modifications made |
|---|---|
| bpch2_mod.F |
In routine GET_MODELNAME:
In routine GET_NAME_EXT:
In routine GET_RES_EXT:
|
| directory_mod.F |
At the top of the module:
|
| grid_mod.F |
In routine COMPUTE_GRID:
In routine INIT_GRID:
|
| pressure_mod.F |
In routines GET_PEDGE and GET_PEDGE_FULLGRID:
In routine INIT_PRESSURE:
|
| time_mod.F |
In routine GET_A1_TIME:
|
| transfer_mod.F |
In several routines:
|
--Bob Y. 17:31, 8 February 2012 (EST)
GeosCore directory
The following modifications for GEOS-5.7.2 were made in the GeosCore/ directory:
| File | Modifications made |
|---|---|
| carbon_mod.F | In routine SOAG_CLOUD:
|
| convection_mod.F |
In routine DO_CONVECTION:
|
| dao_mod.F |
In routine COPY_I6_FIELDS:
In routines IS_ICE, IS_LAND, IS_NEAR, IS_WATER:
In routine INTERP:
|
| depo_mercury_mod.F |
In routine ADD_Hg2_SNOWPACK
|
| diag3.F |
|
| dust_mod.F |
In routine SRC_DUST_DEAD:
|
| dust_dead_mod.F |
In routine DST_MBL:
|
| fast_j.F |
|
| gamap_mod.F |
In routine INIT_TRACERINFO:
|
| geos57_read_mod.F90 |
|
| global_ch4_mod.F |
In routines WETLAND_EMIS and READ_COPROD:
|
| global_hno3_mod.F |
In routine GET_GLOBAL_HNO3:
|
| global_o3_mod.F |
In routine GET_GLOBAL_O3
|
| initialize.F |
|
| input_mod.F |
In routine READ_SIMULATION_MENU:
In routine READ_CONVECTION_MENU:
In routine READ_EMISSIONS_MENU:
In routine VALIDATE_DIRECTORIES:
|
| land_mercury_mod.F |
In routines LAND_MERCURY_FLUX:
In routines SOILEMIS:
|
| lightning_nox_mod.F |
In routine LIGHTNING:
In routine GET_OTD_LIS_SCALE:
|
| Makefile |
|
| main.F |
|
| megan_mod.F |
At top of module
In routine INIT_MEGAN:
|
| mercury_mod.F |
In routine CHEM_Hg0_Hg2:
|
| nei2005_anthro_mod.F |
In routines EMISS_NEI2005_ANTHRO and EMISS_NEI_ANTHRO_05x0666:
|
| ocean_mercury_mod.F |
In routines OCEAN_MERCURY_FLUX and MLD_ADJUSTMENT:
|
| planeflight_mod.F |
In routine PLANEFLIGHT
|
| schem.F |
|
| sulfate_mod.F |
In routine CHEM_SO2:
In routine INIT_SULFATE
|
| tagged_co_mod.F |
In routine READ_PCO_LCO_STRAT:
|
| upbdflx_mod.F |
In routines UPBDFLX_O3 and UPBDFLX_HD:
|
| vdiff_mod.F90 |
In routine VDIFFDR:
|
| wetscav_mod.F |
In routines DO_WETDEP, DO_WASHOUT_ONLY
In routine MAKE_QQ:
In routine RAINOUT:
|
--Bob Y. 13:42, 9 February 2012 (EST)
GeosApm directory
The following modifications for GEOS-5.7.2 were made in the GeosTomas/ directory:
| File | Modifications made |
|---|---|
| Makefile |
|
| carbon_mod.F |
|
| dao_mod.F |
|
| dust_mod.F |
|
| dust_dead_mod.F |
|
| main.F |
|
| sulfate_mod.F |
|
| wetscav_mod.F |
|
--Bob Y. 13:49, 9 February 2012 (EST)
NcdfUtil directory
We have added the NcdfUtil/ directory, which contains routines for netCDF file I/O. These routines are based on the NcdfUtilities package by Bob Yantosca. These are built when you compile GEOS-Chem with the NETCDF=yes Makefile option.
| File | Description |
|---|---|
| Makefile | GNU Makefile used to build the NcdfUtil code. |
| TestNcdfUtil.F90 | Test program to verify that the netCDF libraries were built properly. (This is executed only when you issue a make ncdfcheck command.) |
| m_do_err_out.F90 | Routine to print out netCDF error messages. |
| m_netcdf_io_checks.F90 | Routines to check whether a netCDF file contains a specified variable or dimension. |
| m_netcdf_io_close.F90 | Routines to close a netCDF file. |
| m_netcdf_io_create.F90 | Routines used to open a netCDF file for output and to synchronize a netCDF file. |
| m_netcdf_io_define.F90 | Routines to define netCDF variables and attributes. Use this when writing data to a netCDF file. |
| m_netcdf_io_get_dimlen.F90 | Routines to return dimension information from a netCDF file. |
| m_netcdf_io_handle_err.F90 | Routines for netCDF I/O error handling. |
| m_netcdf_io_open.F90 | Routines for opening a netCDF file for reading or for writing. |
| m_netcdf_io_read.F90 | Routines for reading variables (of INTEGER, REAL*4, REAL*8, and CHARACTER types) from a netCDF file. |
| m_netcdf_io_readattr.F90 | Routines for reading global and variable attributes (of INTEGER, REAL*4, REAL*8, and CHARACTER types) from a netCDF file. |
| m_netcdf_io_write.F90 | Routines for writing data to a netCDF file |
--Bob Y. 10:34, 3 February 2012 (EST)
NcdfUtil/perl subdirectory
In this directory, we have added scripts for automatically generating Fortran code with the proper calls from the NcdfUtilities package. We anticipate that this will be a convenience for GEOS-Chem users, as it will relieve some of the drudgery of writing these calls by hand.
| File | Description |
|---|---|
| StrTrim.pm | Perl module used by the ncCode* scripts. Contains routines for stripping withe space from strings. |
| ncCodeDef | Perl script that generates Fortran code to open a netCDF file and define the various dimensions, variables, and attributes. |
| ncCodeWrite | Perl script that will generate Fortran code to write data to a netCDF file. |
| ncCodeRead | Perl script that will generate Fortran code to read data from a netCDF file. |
| nc_definitions.rc | Generic input file used by the ncCode* scripts. You can edit this. |
| definitions_cn.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 CN data. |
| definitions_a1.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 A1 data. |
| definitions_a3cld.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 A3cld data. |
| definitions_a3dyn.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 A3dyn data. |
| definitions_a3mstc.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 A3mstC data. |
| definitions_a3mste.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 A3mstE data. |
| definitions_i3.rc | Customized version of nc_definitions.rc that will generate Fortran code for reading GEOS-5.7.2 I3 data. |
--Bob Y. 10:34, 3 February 2012 (EST)
Resolved issues
Fractional sea ice
In order to preserve some information about sea ice leads during the regridding process, we have binned the fractional sea ice coverage into deciles (0-10%, 10-20% ... 90-100% coverage) and saved those as separate fields in the GEOS-5.7.2 data archive for GEOS-Chem. We have used the same algorithm we developed for MERRA met fields to do the binning.
--Bob Y. 16:12, 24 January 2012 (EST)
SNOMAS
The SNOMAS (snow depth) fields in both GEOS-5.7.2 and MERRA differ from that in GEOS-5.2.0. It appears that in GEOS-5.2.0 a default snow mass value was applied to grid boxes that had > 90% land ice coverage. This was not done in MERRA or GEOS-5.7.2. Bob Yantosca had implemented an algorithm to adjust the MERRA SNOMAS field to be backwards-compatible with GEOS-5.2.0. We have used this algorithm to adjust the GEOS-5.7.2 SNOMAS field accordingly.
--Bob Y. 16:14, 24 January 2012 (EST)
Dust emissions
The dust emissions in GEOS-Chem rely on "tunable parameters" to scale the dust emissions to a specified total. This is because the dust emissions are very highly dependent on the surface winds, and a small difference in winds (e.g. from GEOS-5 to GEOS-FP) can cause a huge difference in dust emission flux.
In routine DST_MBL (in dust_dead_mod.f), we have added the following code:
!----------------------------------------------------------------
! Based on results from GEOS-FP 4x5 for 04/2012-04/2013
!
! (GEOS-5 - GEOS-FP)/GEOS-5 * 100 is 23.56% in each size bin.
!
! We need to scale to the parameter FLX_MSS_FDG_FCT to make the
! dust emissions consistent. Consequently, to bring GEOS-FP 4x5
! dust emissions up to GEOS-5 levels, we need to MULTIPLY the
! FLX_MSS_FDG_FCT used for GEOS-5 by:
!
! 1 / (1. - 0.2356) = 1 / 0.7644 = 1.3082
!
! -- R. Yantosca, M. Sulprizio, 07 Nov 2013
!----------------------------------------------------------------
REAL*8, PARAMETER :: FLX_MSS_FDG_FCT = 7.0d-4 * 1.3082d0
--Melissa Sulprizio 11:42, 7 November 2013 (EST)
Lightning
TBD
Wet deposition and scavenging
Helen Amos, Bess Corbitt, and Qiaoqiao Wang had implemented an updated algorithm for wet scavenging that takes advantage of the new precipitation fields from the MERRA data archive. This was included in GEOS-Chem v9-01-01 and higher versions.
Because GEOS-5.7.2 contains the same precipitation data fields as MERRA (i.e. DQRCU, DQRLSAN, PFICU, PFILSAN, PFLCU, PFLLSAN, REEVAPCN, REEVAPLSAN), we can use the new wet deposition algorithm with the GEOS-5.7.2 met data.
--Bob Y. 16:16, 24 January 2012 (EST)
Implementation history
Initial source code modifications for GEOS-5.7.2
This update was tested in the 1-month benchmark simulation v9-01-03g and approved on 27 Feb 2012.
NOTE: At the time of this update GEOS-5.7.2 has not been validated, so the #define GEOS_57 switch in define.h should not be used.
The following modifications are slated to be incorporated into the 1-month benchmark GEOS-Chem v9-01-03g:
- Modify the Headers, GeosUtil, and GeosCore directories for GEOS-5.7.2
- Update the GeosApm and GeosTomas directories, primarily to synchronize files with GeosCore
- Add NcdfUtil directory
- Resolve several issues, including: Fractional sea ice, SNOMAS, Wet deposition and scavenging
--Melissa Payer 17:29, 24 February 2012 (EST)
Bug fix for declaration of GEOS-5.7.2 PFICU, PFLCU, PFILSAN, PFLLSAN fields
This update was tested in the 1-month benchmark simulation v9-02g and approved on 24 Mar 2013.
In module file GeosCore/gigc_state_met_mod.F90, it was discovered that the PFICU, PFLCU, PFILSAN, and PFLLSAN met fields for GEOS-5.7.2 were being allocated with the wrong vertical dimension. In GEOS-5.7.2, these fields are placed on level edges and need to be allocated with LLPAR+1 levels. But in MERRA, these fields are placed on level centers and need to be allocated with LLPAR levels.
We have introduced the following fix in routine Init_GIGC_State_Met of Headers/gigc_state_met_mod.F90:
INTEGER :: LX
...
#elif defined( GEOS_57 ) || defined( MERRA )
!=======================================================================
! GEOS-5.7.x / MERRA met fields
!=======================================================================
#if defined( GEOS_57 )
LX = LM + 1
#elif defined( MERRA )
LX = LM
#endif
ALLOCATE( State_Met%PFICU ( IM, JM, LX ), STAT=RC )
IF ( RC /= GIGC_SUCCESS ) RETURN
State_Met%PFICU = 0d0
ALLOCATE( State_Met%PFILSAN ( IM, JM, LX ), STAT=RC )
IF ( RC /= GIGC_SUCCESS ) RETURN
State_Met%PFILSAN = 0d0
ALLOCATE( State_Met%PFLCU ( IM, JM, LX ), STAT=RC )
IF ( RC /= GIGC_SUCCESS ) RETURN
State_Met%PFLCU = 0d0
ALLOCATE( State_Met%PFLLSAN ( IM, JM, LX ), STAT=RC )
IF ( RC /= GIGC_SUCCESS ) RETURN
State_Met%PFLLSAN = 0d0
This will make sure that the fields will be declared properly for either GEOS-5.7.2 or MERRA. (NOTE: LM is set to LLPAR, and thus LM+1 = LLPAR+1.
--Bob Y. 11:32, 18 March 2013 (EDT)
Make sure State_Met%T is initialized properly for GEOS-FP simulations
For simulations with the GEOS-FP met fields, temperature is an I3 (i.e. 3-hr instantaneous) met field. We need to read temperature at times t and t+3hrs, and then interpolate linearly to the proper time.
At time t=0 of a GEOS-FP simulation, the initial temperature is read from netCDF files into State_Met%TMPU1. However, we must also save this into State_Met%T. Otherwise, temperature will be not initialized properly until the first call to INTERP. This can cause a floating-point error further upstream.
We have added the following code to routine Geos57_Read_I3_1 in GeosCore/geos57_read_mod.F90:
! For now, copy State_Met%TMPU1 to State_Met%T. At the next met field
! read, we will State_Met%T from the values of State_Met%TMPU1 and
! State_Met%TMPU2. (bmy, 9/6/13)
State_Met%T = State_Met%TMPU1
This error condition was caught by the GEOS-Chem unit tester when compiling with option FPE=yes.
--Bob Y. 13:13, 12 September 2013 (EDT)