This page describes the current wet deposition scheme used in GEOS-Chem.
- 1 Overview
- 2 Validation
- 3 References
- 4 Previous issues that have been resolved
- 5 Outstanding issues
The Harvard Atmospheric Chemistry Modeling Group developed a wet deposition scheme (including scavenging of soluble tracer in convective updrafts, as well as rainout and washout of soluble tracers) for the GMI model. This scheme was then implemented into GEOS-Chem. Jacob et al  describes the algorithm in full. This scheme is also described in Liu et al .
The following update to the original wet scavenging algorithm will be added to GEOS-Chem following the v8-03-02 release:
Allow both washout and rainout when precipitation forms
Qiaoqiao Wang wrote:
- When there is new formation of precipitation in lower layer k, rainout will be applied to the whole precipitation area: max(Fk,Fk+1), considering the contribution of precipitation formation overhead. This will overestimate rainout effect when Fk+1 is much larger than Fk. Therefore, we now apply rainout effect to precipitation area Fk and washout effect to the area: max (0, Fk+1-Fk) in the same grid box.
NOTE: This update was incorporated into GEOS-Chem v9-01-01.
Updates for aerosol scavenging efficiency
Qiaoqiao Wang wrote:
- The bulk below-cloud scavenging parameterization of Dana and Hales used in the standard GEOS-Chem model integrates scavenging efficiencies over typical aerosol size distributions. This overestimates scavenging as it does not account for the preferential removal of the very fine and coarse particles over the course of the precipitation event, shifting the aerosol size distribution toward the more scavenging-resistant accumulation mode that accounts for most of aerosol mass. Now we use the below-cloud scavenging coefficients integrated over accumulation mode for most aerosols and over coarse mode for coarse dust and sea salt.
--Bob Y. 15:50, 11 January 2011 (EST)
Updates for MERRA met fields
The wet deposition algorithm for GEOS-5 is relatively unchanged, except that we allow both rainout and washout to form within a grid box simultaneously. The wet deposition code has been partitioned into several new subroutines within wetdep_mod.f in order to allow for better compatibility with the wet deposition scheme used for the MERRA met fields.
--Bob Y. 14:12, 9 March 2011 (EST)
Add scavenging by snow
NOTE: This has not been incorporated into GEOS-Chem at this time.
Qiaoqiao Wang wrote:
- [I added] snow scavenging. For in-cloud scavenging by rain droplets, we assume 100% of water-soluble aerosols are rained out. But In the case of snow, only dust and hydrophobic BC is considered to be IN and then could be rained out. The below-cloud scavenging coefficients are also higher for snow than for rain droplets.
--Bob Y. 14:14, 9 March 2011 (EST)
See Liu et al .
- Dana, M.T., and J.M. Hales, Statistical aspects of the washout of polydisperse aerosols, Atmos. Environ, 10, 45-50, 1976.
- Domine, F., and E. Thibert, Mechanism of incorporation of trace gases in ice grown from the gas phase, Geophys. Res. Lett., 23, 3627-3630, 1996.
- Giorgi, F., and W.L. Chameides, Rainout lifetimes of highly soluble aerosols as inferred from simulations with a general circulation model, J. Geophys. Res., 91, 14,367-14,376, 1986.
- Jacob, D.J., Heterogeneous chemistry and tropospheric ozone, Atmos. Environ., 34, 2131-2159, 2000. PDF
- Jacob, D.J. H. Liu, C.Mari, and R.M. Yantosca, Harvard wet deposition scheme for GMI, Harvard University Atmospheric Chemistry Modeling Group, revised March 2000. PDF
- Levine, S.Z., and S.E. Schwartz, In-cloud and below-cloud scavenging of nitric acid vapor, Atmos. Environ., 16, 1725-1734, 1982.
- Liu, H., D.J. Jacob, I. Bey, and R.M. Yantosca, Constraints from 210Pb and 7Be on wet deposition and transport in a global three-dimensional chemical tracer model driven by assimilated meteorological fields, J. Geophys. Res., 106, 12,109-12,128, 2001. PDF
- Mari, C., D.J. Jacob, and P. Bechtold, Transport and scavenging of soluble gases in a deep convective cloud, J. Geophys. Res., 105, 22,255-22,267, 2000. PDF
- Selin, N.E. and D.J. Jacob, Seasonal and spatial patterns of mercury wet deposition in the United States: North American vs. intercontinental sources, Atmospheric Environment, 42, 5193-5204, 2008. PDF
Previous issues that have been resolved
Negative tracer in routine WETDEP because of negative RH
Fixes are available at ftp://ftp.as.harvard.edu/pub/geos-chem/patches/v8-01-01.
--phs 16:31, 6 June 2008 (EDT)
Negative tracer in routine WETDEP
Dylan Millet wrote:
- I'm having a run die consistently at the same time (October 1, 2005; first time step of the month) in large-scale wetdep, with an STT element < 0.
- Platform: Linux cluster
- Threads: 8
- Version: v7-4-13 out of the box.
- GEOS4, 4x5, 30L, full chemistry
- IFORT 10.1
- In Section 6 (No Downward Precip) of wetscav_mod.f, subroutine safety is getting called.
WETDEP - STT < 0 at 1 1 29 for tracer 7 in area 6
- (First of all it seems odd to do wetdep for L=29, this is 63 km up). Have you seen anything like this? I ran for the whole year starting Jan 1 successfully until this point.
- ... By the way, the problem persists when I turn off chemistry altogether.
Philippe Le Sager replied:
- I used your restart file and the same input.geos (w/ chemistry on and off). My code went thru without problem. I tried both Sun Studio and Ifort 9 compilers, and the later on two different machines (altix and ceres). I used v7-04-13 and v8-01-01. I never reproduced your error.
- We just got the new Ifort 10, and tried it too. I run v8-01-01 without an error. But when I tried v7-04-13, I finally reproduced your error, with the exact same negative values!
- In other words: the bug happens with IFort 10 and v7-04-13 only.
- Also, have a look at this recent development. This is not the reason for your bug (I tried v8 w/ ifort 10 and isorropia -like v7-04-13- and it did not crash), but using RPMARES instead of Isorropia may be a way to fix it.
- ... More about the Ifort 10 / v7-04-13 issue. When I wanted to debug with TotalView, I could not reproduce the bug anymore.... because I simply suppress any optimization. So, I did more test and found that if the default -O2 optimization is used, GEOS-Chem crashes. But it works fine with -O1. It is hard to tell what happens, since only the emissions step is done between reading the restart file and the crash.
- Bob and I will further test Ifort 10 for optimization on our machines. Maybe we will find something... For the time being, you may have to switch to -O1, at least for the run that crashes. You will find the optimization flag at the beginning of the Makefile.ifort.
Long story short: This appears to be an optimization issue with IFORT 10 and v7-04-13. Upgrading to GEOS-Chem v8-01-01 should solve this problem.
--Bmy 10:38, 17 April 2008 (EDT)
Negative tracer in routine WETDEP #2
If you find find negative values caused by the wet deposition (particularly on data date 22 July 2010), then here is a workaround:
Mark Parrington wrote
- I'm getting negative values in the wet deposition and am having some difficulty in identifying a possible reason. I've experienced this problem in 3 different versions of the model (v8-02-01, v8-02-04, and v8-03-02) and have tried turning off the chemistry and changing the optimization. Has anyone else had a similar problem?
Claire Carouge replied:
- I don't know if this would help, but a crash on negative or NaN values in wet deposition doesn't always mean that there is a problem in wet deposition.
- GEOS-Chem has the subroutine CHECK_STT in GeosCore/tracer_mod.f. This function is used at some points in the code to check the concentration values (STT array) and stop the code if there is any negative, NaN, or Inf values. In particular, it's used in the wet deposition, but not before this point.
- I think the first thing to do is to identify were the bad values are created. You can insert calls to the CHECK_STT subroutine at different places in main.f (e.g. after transport, after PBL, after emissions, etc.) and see where the code stops. Then you can refine by adding the calls to CHECK_STT into the problematic subroutine and so on.
Mark Parrington followed up:
- I traced the bug to excessive evaporation in a subroutine called MAKE_QQ in wetscav_mod.f - which gives very small, ~1.0E-22, values of the accumulated precipitation (PREACC) leading to very large negative values of the convective fraction of precipitation (FRAC). To get around this I hard-wired the value of FRAC in MAKE_QQ to be 0.67 for the large scale fraction or else 0.33, if the value of PREACC is less than 1.0E-10 (around line number 474 in wetscav_mod.f v9-01-01):
! Large scale or convective fraction of precipitation IF ( LS ) THEN FRAC = ( PREACC(I,J) - PRECON(I,J) ) / PREACC(I,J) ! mp hack for -ve wet deposition if ( preacc(i,j) .lt. 1.0E-10 ) frac = 0.67 ELSE FRAC = PRECON(I,J) / PREACC(I,J) ! mp hack for -ve wet deposition if ( preacc(i,j) .lt. 1.0E-10 ) frac = 0.33 ENDIF
- I was successfully able to run the model up to the end of October this way. I found this issue in v8-02-04 and v9-01-01 but only for the 2x2.5 simulation.
--Bob Y. 12:07, 28 April 2011 (EDT)
Values of F_PRIME greater than 1 in WETDEP
In GEOS-Chem v8-03-01, the value of the variable F_PRIME may end up being slightly greater than 1 under some circumstances. This can cause a negative tracer condition to occur in subroutine WETDEP of wetscav_mod.f.
Kelley Wells wrote:
- The following error message is continually produced in the 03 to 06 UTC time period of 29 July 2010 (2° x 2.5°, GEOS-5).
WETDEP - STT < 0 at 73 65 11 for tracer 1 in area 4
- We've determined that the issue is due to the variable F_PRIME being slightly greater than 1.0 at this point, thus resulting in F > 1.0 and finally RAINFRAC > 1.0. But, it's currently a mystery as to why F_PRIME is greater than 1.0, since both variables that go into its calculation (Q and K_RAIN) have positive values.
Dylan Millet wrote:
- The value of F_PRIME is only very marginally >1, so that
print*,f_prime gives 1.00000000
print*,f_prime - 1d0 gives something on the order of 1E-12
- As best we can tell this is what gives the negative tracer value which causes the run to crash. Inserting a line of code setting:
F = MAX( F_PRIME, FTOP ) !### Kludge, don't let F be greater than 1 F = MIN( F, 1d0 )
- Seems to have fixed the issue. Perhaps we can be more careful and use a more elaborate IF test such as:
IF( ( ( F - 1d0 ) > 0d0 ) ) .and. ( ( F - 1d0 ) < 1d-6 ) ) THEN F = 1d0 ENDIF
- which would catch this type of numerical instability error but not risk masking some other problem.
This type of error can be attributed to numerical instability. You can test by recompiling with the DEBUG=yes option, which will turn off all optimization. You might find that this error disappears when the optimization is turned off. However, turning off all optimization is only recommended for debugging purposes, as code that is not optimized will run much more slowly. Therefore, we recommend adding an IF statement (as shown above) to make sure that the value of F never exceeds 1.
NOTE: In GEOS-Chem v9-01-01 the wet deposition code was rewritten such that subroutine WETDEP was broken up into smaller subroutines, for better compatibility with the new MERRA wet scavenging algorithm. We are unsure if this condition exists in v9-01-01 as of this writing.
--Bob Y. 09:24, 11 March 2011 (EST)
Washout fix for non-aerosol species
Prior to GEOS-Chem v9-01-02, this bug was causing the wet deposition algorithm to underestimate washout of highly soluble gases:
Helen Amos wrote:
- In section 2.2.2 of Jacob et al. (2000), the first bullet point states:
If fi,L > Fi/f, scavenging is limited by mass transfer and we follow exactly the same procedure as for aerosols and HNO3 (section 2.2.1).
- Prior to GEOS-Chem v9-01-02, WASHFRAC_LIQ_GAS was not executing washout of non-aerosol tracers as dictated by this statement.
- Washout proceeds in two ways: (1) Henry's law equilibrium and (2) limited by mass transfer. Aerosols, HNO3, and highly soluble gases should proceed through washout obeying the mass transfer limitation. Moderately and sparingly soluble gases should proceed through washout obeying Henry's law equilibrium. The purpose of WASHFRAC_LIQ_GAS is to calculate WASHFRAC for non-aerosol species, where WASHFRAC is the fraction of a tracer available for washout. WASHFRAC is calculated using Henry's law if fi,L <= Fi/f (Eqn 15-16, Jacob et al. 2000), and WASHFRAC is calculated using mass transfer if fi,L > Fi/f (Eqn 14, Jacob et al. 2000). The algorithms in WASHOUT are written such that if you specify that a tracer proceed through washout according to Henry's law, the code expects WASHFRAC to be calculated using Henry's law (Eqn 15-16, Jacob et al. 2000). Similarly, if you specify that a tracer proceed through washout limited by mass transfer, then the code expects WASHFRAC to be calculated using mass transfer (Eqn 14). Prior to GEOS-Chem v9-01-02, every soluble gas (except HNO3) was arbitrarily forced to proceed through washout according to Henry's law, even when fi,L > Fi/f and WASHFRAC had been calculated from mass transfer equations. In short, there was a mismatch in information between WASHFRAC_LIQ_GAS and WASHOUT. This mismatch caused an underestimate in the washout of highly soluble gases because too much tracer was being re-evaporated (negative term in WETLOSS, where WETLOSS is the amount of tracer lost in a grid box).
- A logical is now passed as an input/output parameter to WASHFRAC_LIQ_GAS and this logical will specify whether a non-aerosol species should proceed through washout according to Henry's law equilibrium or limited by mass transfer. The code is now consistent with Section 2.2.2 of Jacob et al. (2000).
This fix was originally tested in the 1-month benchmark simulation v9-01-02b. A second bug in WASHFRAC_LIQ_GAS was discovered, invalidating v9-01-02b (see discussion below). The complete fix for WASHFRAC_LIQ_GAS has been added to the standard code and approved in the 1-month benchmark simulation v9-01-02f.
Update 7/28/2011: The original algorithm we tested in 1-month benchmark v9-01-02b was incorrect. Prior to v9-01-02b, routine WASHFRAC_LIQ_GAS looked like this:
IF (WASHFRAC > WASHFRAC_F_14) THEN WASHFRAC = WASHFRAC_F_14
In benchmark simulation v9-01-02b we had modified this IF statement (incorrectly) to:
IF ( WASHFRAC > WASHFRAC_F_14 ) THEN WASHFRAC = WASHFRAC_F_14 AER = TRUE. ENDIF
However, this IF statement should have been:
IF ( WASHFRAC > WASHFRAC_F_14 ) THEN WASHFRAC = F * WASHFRAC_F_14 AER = TRUE. ENDIF
We will add this fix to the standard code and resubmit a 1-month benchmark simulation.
--Bob Y. 14:57, 28 July 2011 (EDT)
This fix has been added to the standard code and was approved in the v9-01-02f benchmark.
--Helen Amos 03:57, 13 Aug 2011 (EST)