ML092870678

From kanterella
Revision as of 23:57, 6 December 2019 by StriderTol (talk | contribs) (Created page by program invented by StriderTol)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Exhibit O - Aermod Implementation Guide
ML092870678
Person / Time
Site: Indian Point  Entergy icon.png
Issue date: 01/09/2008
From:
Environmental Protection Agency
To:
Atomic Safety and Licensing Board Panel
SECY RAS
Shared Package
ML092870100 List:
References
50-247-LR, 50-286-LR
Download: ML092870678 (4)


Text

Indian Point Nuclear Generating Units 2 and 3 Docket Nos. 50-247/ 50-286-LR NRC Staff's Response in Opposition to State of New York's Motion for Partial Summary Disposition of NYS Contention 16116A Exhibit 0

AERMOD IMPLEMENTATION GUIDE Last Revised: January 9,2008 AERMOD Implementation Workgroup U. S. Environmental Protection Agency Office of Air Quality Planning and Standards Air Quality Assessment Division Research Triangle Park, North Carolina

4.0 TERRAIN DATA AND PROCESSING 4.1 MODELING SOURCES WITH TERRAIN-FOLLOWING PLUMES IN SLOPING TERRAIN (01/09/08)

Under the regulatory default mode (DFAULT option on the MODELOPT keyword), for all situations in which there is a difference in elevation between the source and receptor, AERMOD simulates the total concentration as the weighted sum of 2 plume states (Cimorelli, et ul., 2004):

I) a horizontal plume state (where the plume's elevation is assumed to be determined by release height and plume rise effects only, and thereby allowing for impingement if terrain rises to the elevation of the plume); and, 2) a terrain-responding plume state (where the plume is assumed to be entirely terrain following).

For cases in which receptor elevations are lower than the base elevation of the source (i.e.,

receptors that are down-slope of the source), AERMOD will predict concentrations that are less than what would be estimated from an otherwise identical flat terrain situation. While this is appropriate and realistic in most cases, for cases of down-sloping terrain where expert judgment suggests that the plume is terrain-following (e.g., down-slope gravityldrainage flow), AERMOD will tend to underestimate concentrations when terrain effects are taken into account. AERMOD may also tend to underestimate concentrations relative to flat terrain results for cases involving low-level, non-buoyant sources with up-sloping terrain since the horizontal plume component will pass below the receptor elevation. Sears (2003) has examined these situations for low-level area sources, and has shown that as terrain slope increases the ratio of estimated concentrations from AERMOD to ISC (which assumes flat terrain for area sources) decreases substantially.

To avoid underestimating concentrations in such situations, it may be reasonable in cases of terrain-following plumes in sloping terrain to apply the non-DFAULT option to assume flat, level terrain. This determination should be made on a case-by-case basis, relying on the modeler's experience and knowledge of the surrounding terrain and other factors that affect the air flow in the study area, characteristics of the plume (release height and buoyancy), and other factors that may contribute to a terrain-followi~igplume, especially under worst-case

~neteorologicalconditions associated with the source. The decision to use the non-DFAULT option for flat terrain, and details regarding how it will be applied within the overall modeling analysis, should be documented and justified in a modeling protocol submitted to the appropriate reviewing authority prior to conducting the analysis.

4.2 AERMAP DEM ARRAY AND DOMAIN BOUNDARY (09127105)

Section 2.1.2 of the AERMAP User's Guide (EPA, 2004c) states that the DEM array and domain boundary must include all terrain features that exceed a 10% elevation slope from any given receptor. The 10% slope rule may lead to excessively large domains in areas with considerable terrain features (e.g., fjords, successive mountain ranges, etc). In these situations, the reviewing authority may make a case-by-case determination regarding the domain size needed for AERMAP to determine the critical dividing streamline height for each receptor.

AERMOD Implementation Guide .Janziury 9, 2008 6.0 SOURCE CHARACTERIZATION 6.1 CAPPED AND HORIZONTAL STACKS (09127105)

For capped and horizontal stacks that are NOT subject to building downwash influences a simple screening approach (Model Clearinghouse procedure for ISC) can be applied. This approach uses an effective stack diameter to maintain the flow rate, and hence the buoyancy, of the plume, while suppressing plume momentum by setting the exit velocity to 0.001 4 s . To appropriately account for stack-tip downwash, the user should first apply the non-default option of no stack-tip downwash (i.e., NOSTD keyword). Then, for capped stacks, the stack release height should be reduced by three actual stack diameters to account for the ~ ~ l a x i ~ nstack-tip u ~ n downwash adjustment while no adjustment to release heigllt should be made for horizontal releases.

Capped and horizontal stacks that are subject to building downwash should not be modeled using an effective stack diameter to simulate the restriction to vertical flow since the PRIME algorithms use the stack diameter to define the initial plume radius which, in turn, is used to solve conservation laws. The user should input the actual stack diameter and exit temperature but set the exit velocity to a nominally low value, such as 0.001 d s . This approach will have the desired effect of restricting the vertical flow while avoiding the mass conservation problem inherent with effective diameter approach. The approach suggested here is expected to provide a conservative estimate of impacts. Also, since PRIME does not explicitly consider stack-tip downwash, no adjustments to stack height should be made.

6.2 USE OF AREA SOURCE ALGORITHM IN AERMOD (09127105)

Because of issues related to excessive run times and technical issues with model formulation, the approach that AERMOD uses to address plume meander has not been implemented for area sources. As a result, concentration predictions for area sources may be overestimated under very light wind conditions (i.e., u << 1.0 d s ) . In general, this is not expected to be a problem for meteorological data collected using standard wind instruments since instrument thresholds are generally too high. However, the problem could arise with meteorological data derived from very low threshold instruments, such as sonic anemometers. While not currently accepted for regulatory applications of AERMOD, this problem has also arisen when data from a gridded n~eteorologicalmodel was used to drive AERMOD. Meteorological grid models can at times produce extremely light winds. During such conditions time-averaged plumes tend to spread primarily as a result of low frequency eddy translation rather than eddy diffusion. AERMOD treats this meander effect by estimating the concentration from two limiting states: 1) a coherent plume state that considers lateral diffusive turbulence only (the mean wind direction is well defined) and 2) a random plume state (mean wind direction is poorly defined) that allows the plunle to spread uniformly, about the source, in the x-y plane. The final concentration predicted by AERMOD is a weighted sum of these two bounding concentrations. Interpolation between the coherent and random plume concentrations is accomplislled by assuming that the total horizontal "energy" is distributed between the wind's mean and turbulent components.