Difference between revisions of "GEOS-Chem v11-02"

Revision as of 13:45, 12 May 2017

Overview

History

The table below shows the previous, current, and successive versions of GEOS-Chem:

What's new in this version

NOTE: v11-02a, v11-02b, etc. denote 1-month benchmark simulations, which are designed to evaluate GEOS-Chem's performance at intermediate stages of development.

v11-02a

Please see the the following link for complete information about the validation of GEOS-Chem v11-02a:

1. Approval form for 1-month benchmark simulation v11-02a

v11-02b

v11-02c

v11-02d

v11-02e

In the pipeline

New data directories

The following HEMCO data directories have been added or updated for GEOS-Chem v11-02. You will have to download the directories relevant to your simulation.

--Melissa Sulprizio (talk) 22:21, 29 March 2017 (UTC)

Validation

In this section we provide information about the benchmarks and tests that we have done to validate GEOS-Chem v11-01.

1-month and 1-year benchmarks

For complete information about the benchmark simulations used to validate GEOS-Chem v11-02, please see our GEOS-Chem v11-02 benchmark history wiki page.

Unit tests for GEOS-Chem v11-02

We perform a full set of unit tests on GEOS-Chem on an almost daily basis. These tests ensure that each new feature being added does not break any existing functionality.

Here are the unit tests that we ran before submitting 1-month benchmark simulation for v11-02. Click on the links below to see the results from each set of unit tests:

Previous issues now resolved in GEOS-Chem v11-02

The following bugs and/or technical issues have been resolved in v11-02:

Fixed an incorrect format statement in input_mod.F

This update will be added to v11-02c.

Chris Holmes wrote:

An incorrect format specification caused GEOS-Chem to crash rather than write a helpful error message when the transport timestep is too big. The code in RED was removed and the lines in GREEN was added at approximately line 3324 of input_mod.F.

        IF ( Input_Opt%TS_DYN > MAX_DYN .and. LTRAN ) THEN
           write(MSG,'(I8,a,L)') '<>', Input_Opt%TS_DYN, Input_Opt%HPC
           WRITE( MSG, 300 ) 'Transport timestep exceeds max:',
    &                         Input_Opt%TS_DYN, MAX_DYN
300        FORMAT( a, i8, ' >', i8 ) 
           CALL ERROR_STOP( MSG, LOCATION )
        ENDIF

--Bob Yantosca (talk) 17:55, 18 April 2017 (UTC)

Bug fixes for the ND50 timeseries diagnostic

These issues will be resolved in GEOS-Chem v11-02c.

Chris Holmes wrote:

I have found what I suspect are two bugs in ND50.

1. Function ITS_TIME_FOR_WRITE_DIAG50() checks if the integer part of the hour is zero to decide whether to write to disk. With the 20 minute time steps recommended in v11-01, Diag50 gets written and overwritten multiple times in the first hour of every day! The fix is simply to have this function return TRUE if the GMT time is 00:00.

2. Within WRITE_DIAG50 there is the following block of code

        ! Pick the proper divisor, depending on whether or not the
        ! species in question is archived only each chem timestep
        SELECT CASE ( ND50_TRACERS(W) )
           CASE (91, 92, 76, 77 )
              DIVISOR = COUNT_CHEM3D
           CASE DEFAULT
              DIVISOR = COUNT
        END SELECT

I see nothing special about tracers 76, 77, 91, and 92 that should make them divided by a different number. The special tracers numbers are all >= 150 for ND50. I suspect this is left over from a previous code revision. I think it should be DIVISOR=COUNT for all ND50_Tracers.

--Bob Yantosca (talk) 14:42, 14 April 2017 (UTC)

Removed the NNPAR parameter from CMN_SIZE_mod.F

This update will be added to v11-02a.

The NNPAR parameter is a holdover from when we used COMMON blocks to store GEOS-Chem arrays. With the advent of the GEOS-Chem species database, we now use State_Chm%nSpecies to represent the total number of species in the chemistry mechanism, and State_Chm%nAdvect to represent the total number of advected species.

We have therefore removed the following lines (in RED) from CMN_SIZE_mod.F:

      !=================================================================
      ! TRACER & EMISSION SPECIES PARAMETERS
      !
      ! NNPAR   = max number of tracers
      ! NEMPARA = max number of anthropogenic emission species
      ! NEMPARB = max number of biogenic      emission species
      !=================================================================
      ! increase NNPAR and NEMPARA an extra amount (hotp 7/31/09)
#if   defined( TOMAS )
# if    defined( TOMAS40 )
      INTEGER,    PARAMETER :: NNPAR   = 430   ! For TOMAS40 (sfarina 6/11/13)
# elif  defined( TOMAS15 )
      INTEGER,    PARAMETER :: NNPAR   = 205   ! For TOMAS15 (sfarina 6/11/13)
# elif  defined( TOMAS12 )
      INTEGER,    PARAMETER :: NNPAR   = 178   ! For TOMAS12 (sfarina 6/11/13)
# else
      INTEGER,    PARAMETER :: NNPAR   = 340   ! For TOMAS (win, bmy, sfarina 6/11/13)f
# endif
#else
      INTEGER,    PARAMETER :: NNPAR   = 150   ! For non-TOMAS simulations
#endif

--Bob Yantosca (talk) 20:27, 17 March 2017 (UTC)

Print the version number to the log file

This update will be added to v11-02a.

In routine DISPLAY_GRID_AND_MODEL of GeosCore/main.F, we now print out the version number, e.g.

Using GEOS-Chem version: v11-02

to the log file (i.e. stdout output stream). This will facilitate debugging.

--Bob Yantosca (talk) 18:21, 16 March 2017 (UTC)

Include TOA pressure when calculating dry pressure edges

This update will be added to v11-02a.

For physicality and consistency with GCHP, the top-of-atmosphere (TOA) pressure is now included when calculating dry pressure edges. The following lines in GeosCore/dao_mod.F were changed from:

     ! Reset dry surface pressure to zero
     PS_DRY = 0.0e+0_fp

to:

     ! Reset dry surface pressure to TOA value
     PS_DRY = GET_AP(LLPAR+1)

--Melissa Sulprizio (talk) 20:47, 14 April 2017 (UTC)

ND26 vertical flux diagnostic does not yield mass balance in advection

This update will be added to v11-02b.

To achieve mass balance in the advection diagnostic output (ND24, ND25, and ND26) Ilya Stanevic (U. Toronto) suggested that the FZ array be used to compute the ND26 vertical mass flux diagnostic for all levels. This is similar to how FX is used for ND24 and FY for ND25. Note that this fix is only for global advection since the FZ array is not defined for the nested model. With this update, the global ND26 vertical flux diagnostic is defined as the flux into the grid box above (e.g. ND26(:,:,1) is flux from level 1 to level 2 and ND26(:,:,LLPAR) is all zeros).

--Lizzie Lundgren (talk) 21:41, 9 May 2017 (UTC)

ND40 planeflight diagnostic not always written out when turned on

This update will be added to v11-02b.

Lee Murray (University of Rochester) wrote:

I think the FlexChem implementation accidentally disabled the planeflight diagnostic for the full chemistry simulation. We used to initialize the planeflight diagnostic in chemdr.F for full chemistry simulations (now no more) and all the other versions in main.F. We should change main.F to always call SETUP_PLANEFLIGHT whenever the diagnostic is turned on.

        ! Plane following diagnostic
        IF ( ND40 > 0 .and. DO_DIAG_WRITE ) THEN 
        
           ! Call SETUP_PLANEFLIGHT routine if necessary
           IF ( ITS_A_NEW_DAY() ) THEN
              
!               ! If it's a full-chemistry simulation but LCHEM=F,
!               ! or if it's an offline simulation, call setup routine 
!               IF ( ITS_A_FULLCHEM_SIM ) THEN
!                  IF ( .not. LCHEM ) THEN
!                     CALL SETUP_PLANEFLIGHT( am_I_Root, Input_Opt,
!     &                                       State_Chm, RC )
!                  ENDIF
!               ELSE
!                  CALL SETUP_PLANEFLIGHT( am_I_Root, Input_Opt, 
!     &                                    State_Chm, RC )
!               ENDIF

              CALL SETUP_PLANEFLIGHT( am_I_Root, Input_Opt, State_Chm, RC )

           ENDIF
        ENDIF

--Lizzie Lundgren (talk) 19:44, 10 May 2017 (UTC)

CO2 emissions unit conversion not consistent with new advection pressure

This update will be added to v11-02b.

A pressure update was introduced in v11-01h that corrected an advection issue in which tracer mass was transported relative to moist rather than dry air. To conserve mass throughout the model, all unit conversions were updated to use a dry pressure difference consistent with the new values used in advection. This replaced the previous method which calculated dry pressure difference per level directly from moist edge pressures and GMAO specific humidity.

Meemong Lee discovered that a CO2-only unit conversion for carbon dioxide emissions in co2_mod.F continued to use an old method for converting units that pre-dated the v11-01h update. To correct this, the unit conversion should be changed to be consistent with the analogous unit conversion in unitconv_mod.F90.

Prior to fix:

              E_CO2  =  HcoState%Spc(IDff)%Emis%Val(I,J,1)
    &                * DTSRCE / ( State_Met%DELP(I,J,1) 
    &                * G0_100 * ( 1.0e+0_fp
    &                - State_Met%SPHU(I,J,1) * 1.0e-3_fp ) )   

Update:

            E_CO2  =  HcoState%Spc(IDff)%Emis%Val(I,J,1)
    &                * DTSRCE * ( 1.0e+0_fp / ( g0_100
    &                * State_Met%DELP_DRY(I,J,L) ) )
   

--Lizzie Lundgren (talk) 19:44, 10 May 2017 (UTC)

Outstanding issues not yet resolved in GEOS-Chem v11-02

TBD