|
|
(44 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
| This page describes the cloud convection (aka wet convection) algorithms of GEOS-Chem. | | This page describes the cloud convection (aka wet convection) algorithms of GEOS-Chem. We also invite you to read [[Wet deposition|our ''Wet deposition'' wiki page]], which contains information about the algorithms used for scavenging of soluble tracers. |
|
| |
|
| == Overview == | | == Overview == |
Line 13: |
Line 13: |
| == Relaxed Arakawa-Schubert scheme == | | == Relaxed Arakawa-Schubert scheme == |
|
| |
|
| This is the convection scheme that GEOS-Chem uses with both GEOS-3 and GEOS-5 meteorology. The source code for this scheme is located in routine <tt>NFCLDMX</tt> in <tt>convection_mod.f</tt>. | | This is the convection scheme that GEOS-Chem currently uses with [[GEOS-FP]] and [[MERRA-2]] meteorology. The source code for this scheme is located in routine <tt>DO_CONVECTION</tt> in <tt>GeosCore/convection_mod.F</tt>. |
| | |
| == Hack and Zhang-McFarlane schemes ==
| |
| | |
| This is the convection scheme that GEOS-Chem uses with both GEOS-4 and GCAP meteorology.
| |
| | |
| === GEOS-4 ===
| |
| | |
| The source code for the convection scheme required for GEOS-4 meteorology is contained within the F90 module <tt>fvdas_convect_mod.f</tt>. The main driver is called <tt>FVDAS_CONVECT</tt>. This routine calls the following routines:
| |
| | |
| #<tt>ARCONVTRAN</tt>: Prepares arrays for use by <tt>CONVTRAN</tt>
| |
| #<tt>CONVTRAN</tt>: Main driver for deep convection (i.e. Zhang/McFarlane scheme)
| |
| #<tt>HACK_CONV</tt>: Main driver for shallow convection (i.e. Hack scheme)
| |
| | |
| === GISS ===
| |
| | |
| The source code for the convection scheme required for GISS/GCAP meteorology is contained within the F90 module <tt>gcap_convect_mod.f</tt>. The main driver is called <tt>GCAP_CONVECT</tt>. This routine calls the following routines:
| |
| | |
| #<tt>ARCONVTRAN</tt>: Prepares arrays for use by <tt>CONVTRAN</tt>
| |
| #<tt>CONVTRAN</tt>: Main driver for deep convection (i.e. Zhang/McFarlane scheme)
| |
| | |
| There is no equivalent routine to <tt>HACK_CONV</tt> for the GCAP meterology. Instead, <tt>ARCONVTRAN</tt> and <tt>CONVTRAN</tt> are called with entraining mass fluxes, and then again with non-entraining mass fluxes.
| |
| | |
| --[[User:Bmy|Bob Y.]] 13:11, 19 February 2010 (EST)
| |
|
| |
|
| == Validation == | | == Validation == |
Line 56: |
Line 33: |
|
| |
|
| --[[User:Bmy|Bob Y.]] 13:11, 19 February 2010 (EST) | | --[[User:Bmy|Bob Y.]] 13:11, 19 February 2010 (EST) |
|
| |
| == Previous issues that are now resolved ==
| |
|
| |
|
| |
|
| |
| === Reduce time spent in routine DO_CONVECTION when using GEOS-FP or MERRA ===
| |
|
| |
| '''''This update is being tested with month benchmark simulation [[GEOS-Chem v10-01 benchmark history#v10-01c|GEOS-Chem v10-01c]].'''''
| |
|
| |
| Using the [http://tau.uoregon.edu Tuning and Analysis Utilities (TAU)], we were able to make the following modifications to routine <tt>DO_CONVECTION</tt> (in module file <tt>GeosCore/convection_mod.F</tt>) that resulted in a speedup in the [[GEOS-FP]]/[[MERRA]] convection module. We made modifications in the following routines:
| |
|
| |
| #<tt>DO_CONVECTION</tt> (in module <tt>GeosCore/convection_mod.F</tt>)
| |
| #*We no longer use objects from <tt>GeosCore/gc_type_mod.F</tt> (i.e. <tt>OPTIONS</tt>, <tt>DIMINFO</tt>, etc.). These have been largely superseded by the <tt>Input_Opt</tt> object.
| |
| #*Remove all pointer references to fields of <tt>State_Met</tt> and <tt>State_Chm</tt> from the parallel DO loop.
| |
| #*Now use the proper # of tracers for APM aerosol microphysics.
| |
| #*Now declare the parallel DO loop with <tt>!$OMP+PRIVATE</tt>, which results in better load-balancing.
| |
| #<tt>DO_MERRA_CONVECTION</tt> (in module <tt>GeosCore/convection_mod.F</tt>):
| |
| #*Now make the following variables local pointer variables instead of arguments:
| |
| #**<tt>AD, BXHEIGHT, CMFMC, DQRCU, DTRAIN, REEVAPCN, T, Q</tt>. These point to the corresponding variables in <tt>State_Met</tt> or <tt>State_Chm</tt>.
| |
| #**<tt>H2O2s, SO2s</tt>: These point to the corresponding arrays in <tt>GeosCore/sulfate_mod.F</tt>.
| |
| #<tt>COMPUTE_F</tt> (in module <tt>GeosCore/wetscav_mod.F</tt>)
| |
| #*Now make the F argument of routine COMPUTE_F an assumed-shape array (i.e. <tt>F(:,:,:)</tt> ). This allows us to pass pointer-valued arguments to
| |
| #<tt>GeosCore/gc_type_mod.F</tt>:
| |
| #*This has now been moved to the <tt>obsolete/</tt> subdirectory.
| |
|
| |
| [[Image:GEOSFP_Conv_Speedup.png]]
| |
|
| |
| Also note that with this fix, the total CPU time of this run (1-day with GEOS-4x5 met) dropped from 16:l1 to 15:23 (min:sec). So this fix is making the overall simulation run a little faster for each simulation day.
| |
|
| |
| --[[User:Bmy|Bob Y.]] 16:38, 18 April 2014 (EDT)
| |
|
| |
| === Removed array temporaries in call to FVDAS_CONVECT ===
| |
|
| |
| '''''This update is being tested with month benchmark simulation [[GEOS-Chem v10-01 benchmark history#v10-01c|GEOS-Chem v10-01c]].'''''
| |
|
| |
| The [[GEOS-Chem Unit Tester]] revealed the presence of array temporaries in the call to GEOS-4 convection routine <tt>FVDAS_CONVECT</tt>. To remove the array temporaries, we made these modifications in subroutine <tt>DO_GEOS4_CONVECT</tt>, located in module <tt>GeosCore/convection_mod.F</tt>:
| |
|
| |
| (1) Declare the <tt>F</tt> variable with the <tt>TARGET</tt> attribute, as follows:
| |
|
| |
| #if defined( APM )
| |
| INTEGER :: INDEXSOL(Input_Opt%N_TRACERS+N_APMTRA)
| |
| REAL*8, TARGET :: F (IIPAR,JJPAR,LLPAR,
| |
| & Input_Opt%N_TRACERS+N_APMTRA)
| |
| #else
| |
| INTEGER :: INDEXSOL(Input_Opt%N_TRACERS)
| |
| REAL*8, TARGET :: F (IIPAR,JJPAR,LLPAR,
| |
| & Input_Opt%N_TRACERS)
| |
| #endif
| |
|
| |
| (2) Add pointer variables <tt>p_STT</tt> and <tt>p_F</tt>:
| |
|
| |
| REAL*8, POINTER :: p_STT (:,:,:,:) ! Ptr to STT (flipped in vert)
| |
| REAL*8, POINTER :: p_F (:,:,:,:) ! Ptr to F (flipped in vert)
| |
|
| |
| (3) Point <tt>p_STT</tt> to the <tt>State_Chm%Tracers</tt> field and flip levels in the vertical. Likewise, point <tt>p_F</tt> to the <tt>F</tt> array, and also flip in the vertical:
| |
|
| |
| ! Point to various fields and flip in vertical. This avoids
| |
| ! array temporaries in the call to FVDAS_CONVECT (bmy, 4/14/14)
| |
| p_HKETA => State_Met%HKETA (:,:,LLPAR:1:-1 )
| |
| ... etc ...
| |
| p_STT => State_Chm%Tracers(:,:,LLPAR:1:-1,:)
| |
| p_F => F (:,:,LLPAR:1:-1,:)
| |
|
| |
| (4) Pass <tt>p_STT</tt> and <tt>p_F</tt> to subroutine <tt>FVDAS_CONVECT</tt>:
| |
|
| |
| ! Call the fvDAS convection routines (originally from NCAR!)
| |
| CALL FVDAS_CONVECT( TDT,
| |
| & N_TOT_TRC,
| |
| !----------------------------------------------------------------------------
| |
| ! Prior to 4/14/14:
| |
| ! Eliminate an array temporary (bmy, 4/14/14)
| |
| ! & STT (:,:,LLPAR:1:-1,:),
| |
| !----------------------------------------------------------------------------
| |
| & p_STT,
| |
| & RPDEL,
| |
| & p_HKETA,
| |
| & p_HKBETA,
| |
| & p_ZMMU,
| |
| & p_ZMMD,
| |
| & p_ZMEU,
| |
| & DP,
| |
| & NSTEP,
| |
| !----------------------------------------------------------------------------
| |
| ! Prior to 4/14/14:
| |
| ! Eliminate an array temporary (bmy, 4/14/14)
| |
| ! & F (:,:,LLPAR:1:-1,:),
| |
| !----------------------------------------------------------------------------
| |
| & p_F,
| |
| & TCVV,
| |
| & INDEXSOL,
| |
| & State_Met )
| |
|
| |
| (5) Nullify the pointers <tt>p_STT</tt> and <tt>p_F</tt> at the end of subroutine <tt>DO_GEOS4_CONVECT</tt>:
| |
|
| |
| ! Free pointers
| |
| NULLIFY( STT, p_STT, p_F )
| |
|
| |
| --[[User:Bmy|Bob Y.]] 11:05, 15 April 2014 (EDT)
| |
|
| |
| === Fixed minor issues in MERRA cloud convection routine ===
| |
|
| |
| Jenny Fisher discovered two minor issues in the [[MERRA]] convection routine <tt>DO_MERRA_CONVECTION</tt> (in module <tt>convection_mod.f</tt>):
| |
|
| |
| ==== ND38 diagnostic issue in routine DO_MERRA_CONVECTION ====
| |
|
| |
| '''''This update was tested in the 1-month benchmark simulation [[GEOS-Chem_v9-01-02_benchmark_history#v9-01-02j|v9-01-02j]] and approved on 16 Aug 2011.'''''
| |
|
| |
| '''''[mailto:jafisher@fas.harvard.edu Jenny Fisher] wrote]:'''''
| |
|
| |
| :The bug is in routine <tt>DO_MERRA_CONVECTION</tt>. When <tt>DIAG38</tt> is first written (around line 2056 in my code, after the comment titled "(3.4) ND38 Diagnostic"), DIAG38 is formed by adding T0 (converted to appropriate units) to the diagnostic each level K. This is correct. However, the second time we add to <tt>DIAG38</tt> (below the cloud base, around line 2245 in my code), we add <tt>T0_SUM</tt> to each level. From what we can tell, <tt>T0_SUM</tt> represents not the washout from each level but instead the total wet scavenging loss, summed over the entire column. So we are effectively double counting in these levels and adding way too much. [Helen Amos and I] think this should instead be adding <tt>WETLOSS</tt>.
| |
|
| |
| The fix is below:
| |
|
| |
| IF ( OPTIONS%USE_DIAG38 .and. F(K,IC) > 0d0 ) THEN
| |
| DIAG38(K,IC) = DIAG38(K,IC)
| |
| !------------------------------------------------------------------------------
| |
| ! Prior to 8/16/11:
| |
| ! Now use WETLOSS instead of T0_SUM in the ND38 diagnostic below the cloud
| |
| ! base. WETLOSS is the loss in this level, but T0_SUM is the loss summed
| |
| ! over the entire column. Using T0_SUM leads us to over-count the tracer
| |
| ! scavenged out of the column. (jaf, hamos, bmy, 8/16/11)
| |
| ! & + ( T0_SUM * AREA_M2 / TCVV_DNS )
| |
| !------------------------------------------------------------------------------
| |
| & + ( WETLOSS * AREA_M2 / TCVV_DNS )
| |
| ENDIF
| |
|
| |
| --[[User:Bmy|Bob Y.]] 16:48, 16 August 2011 (EDT)
| |
|
| |
| ==== Wrong IF tests used in routine DO_MERRA_CONVECTION ====
| |
|
| |
| '''''This update was tested in the 1-month benchmark simulation [[GEOS-Chem_v9-01-02_benchmark_history#v9-01-02j|v9-01-02j]] and approved on 16 Aug 2011.'''''
| |
|
| |
| :Routine <tt>DO_MERRA_CONVECTION</tt> was using tracer flags <tt>IDTHg2</tt> and <tt>IDTHgP</tt> to determine whether routines <tt>ADD_Hg2_WD</tt>, <tt>ADD_HgP_WD</tt>, and <tt>ADD_Hg2_SNOWPACK</tt> should be called. However, <tt>IDTHg2</tt> and <tt>IDTHgP</tt> aren't ever defined and were set to zero, so these routines were never called even when the correct mercury species were used.
| |
|
| |
| The fix is to replace these two lines of code
| |
|
| |
| IF ( IS_Hg .and. IC == IDT%Hg2 ) THEN
| |
| ...
| |
| IF ( IS_Hg .and. IC == IDT%HgP ) THEN
| |
|
| |
| with these:
| |
|
| |
| IF ( IS_Hg .and. IS_Hg2( IC ) ) THEN
| |
| ...
| |
| IF ( IS_Hg .and. IS_HgP( IC ) ) THEN
| |
|
| |
| --[[User:Bmy|Bob Y.]] 16:47, 16 August 2011 (EDT)
| |
|
| |
| == Outstanding issues that are not yet resolved ==
| |