Post on 23-Jan-2016
1
AirWareAirWare: : RRelease R5.3 betaelease R5.3 beta
AERMOD/AERMETAERMOD/AERMET
AirWareAirWare: : RRelease R5.3 betaelease R5.3 beta
AERMOD/AERMETAERMOD/AERMET
DDr. Kurt FedraDDr. Kurt FedraEnvironmental Software & Services GmbH Environmental Software & Services GmbH A-2352 GumpoldskirchenA-2352 Gumpoldskirchen AUSTRIA AUSTRIAinfo@ess.co.at http://www.ess.co.at/AIRWAREinfo@ess.co.at http://www.ess.co.at/AIRWARE
2
AERMODAERMODAERMODAERMODEPA REGULATORY MODEL, developed from
ISC-ST2/ISC3AERMOD is a
steady-state Gaussian plume modelBasic assumptions:• Homogeneous meteorological conditions in
time and space over the aggregation period;• Constant emissions• Aggregation period: minimally the time
needed to reach steady state (function of domain size and wind speed)
EPA REGULATORY MODEL, developed from ISC-ST2/ISC3
AERMOD is a
steady-state Gaussian plume modelBasic assumptions:• Homogeneous meteorological conditions in
time and space over the aggregation period;• Constant emissions• Aggregation period: minimally the time
needed to reach steady state (function of domain size and wind speed)
3
AERMODAERMODAERMODAERMODModel provide an analytical solution to the
dispersion equations in 3D;
Horizontal and vertical concentration distributions are assumed to follow Gaussian (bell shaped) distribution.
Vertical “complications”: – Terrain following or impacting;– Partial reflection at mixing height.
Model provide an analytical solution to the dispersion equations in 3D;
Horizontal and vertical concentration distributions are assumed to follow Gaussian (bell shaped) distribution.
Vertical “complications”: – Terrain following or impacting;– Partial reflection at mixing height.
4
AERMODAERMODAERMODAERMODBasic principle: conservation lawsBasic principle: conservation laws
heightstack effective
g/semission
y andin x ion concentrat ..
m/s) (downwind, windspeed
zy,at x,ion concentrat ,,
:
2exp
2exp
.2
exp(.2
),,(
22
2
eff
z
eff
z
eff
y
H
Q
ofDS
u
zyxC
where
HzHz
y
u
QzyxC
zy
5
6
7
turbulenceturbulenceturbulenceturbulenceISC used tabulated stability classes (Pasquill)
defined by wind speed, cloud cover, day/night (heat flux)
AERMOD uses boundary layer physics,• Roughness length (Monin-Obukhov Length, L)
• surface roughness length, z0
• surface friction velocity, u• surface heat flux, H• convective scaling velocity, w .
ISC used tabulated stability classes (Pasquill) defined by wind speed, cloud cover, day/night (heat flux)
AERMOD uses boundary layer physics,• Roughness length (Monin-Obukhov Length, L)
• surface roughness length, z0
• surface friction velocity, u• surface heat flux, H• convective scaling velocity, w .
8
turbulenceturbulenceturbulenceturbulenceRoughness length (Monin-Obukhov Length, L)
Measure of “surface roughness”, approximately 1/10 of obstacle physical vertical dimensions, varies, also seasonally (vegetation), from
• 0.0001 m (water surfaces) to • 1 m (cities)• 1.3 m (forests)
Roughness sub-layer: wind speeds deviates from a vertical logarithmic profile.
Roughness length (Monin-Obukhov Length, L)
Measure of “surface roughness”, approximately 1/10 of obstacle physical vertical dimensions, varies, also seasonally (vegetation), from
• 0.0001 m (water surfaces) to • 1 m (cities)• 1.3 m (forests)
Roughness sub-layer: wind speeds deviates from a vertical logarithmic profile.
9
turbulenceturbulenceturbulenceturbulenceSurface friction velocity, u
Wind speed at reference height corrected by a vertical logarithmic profile to the roughness sub-layer and Monin-Obukhov length.
Surface friction velocity, u
Wind speed at reference height corrected by a vertical logarithmic profile to the roughness sub-layer and Monin-Obukhov length.
10
turbulenceturbulenceturbulenceturbulence
Monin-Obukhov length, L,
• A function of temperature,
• wind speed • and heat flux.
Monin-Obukhov length, L,
• A function of temperature,
• wind speed • and heat flux.
constant sKarman' von ,4.0
air ofdensity
air ofheat specific
constantgravity
where
3
k
c
g
kgH
uTcL
p
refp
constant sKarman' von ,4.0
air ofdensity
air ofheat specific
constantgravity
where
3
k
c
g
kgH
uTcL
p
refp
11
turbulenceturbulenceturbulenceturbulence
Surface (sensible) heat flux, H
Bowen ratio:
Related to soil moisture:
0.1: wet
10: very dry
Surface (sensible) heat flux, H
Bowen ratio:
Related to soil moisture:
0.1: wet
10: very dry
RadiationNet R
fluxheat Sensible
RatioBowen
:
/11
9.0
n
0
0
H
B
where
B
RH n
RadiationNet R
fluxheat Sensible
RatioBowen
:
/11
9.0
n
0
0
H
B
where
B
RH n
BQQ
QEF
Q
Q
Q
QB
he
e
e
h
e
h
1
1
on)(evaporati heatinglatent
T)(air heating sensible where
BQQ
QEF
Q
Q
Q
QB
he
e
e
h
e
h
1
1
on)(evaporati heatinglatent
T)(air heating sensible where
12
turbulenceturbulenceturbulenceturbulence
Convective scaling velocity, w .
Now: Deardorff velocity, scale of wind speed
In the convective mixed layer:
typically 1 m s-1 …..
Convective scaling velocity, w .
Now: Deardorff velocity, scale of wind speed
In the convective mixed layer:
typically 1 m s-1 …..
flux re temperatupotential
depthlayer mixing average
re temperatuabsolute
onaccelerati nalgravitatio
where
''
3/1
'''*
i
v
iv
z
T
g
zT
gw
flux re temperatupotential
depthlayer mixing average
re temperatuabsolute
onaccelerati nalgravitatio
where
''
3/1
'''*
i
v
iv
z
T
g
zT
gw
13
Performance:Performance:Performance:Performance:Needs to be solved for each source (but
offers the possibility for source apportioning)
Needs to be solved for each receptor point (grid cell, but can be solved for any arbitrary location)
Steady state solution: provides an upper estimate of concentration
Needs to be solved for each source (but offers the possibility for source apportioning)
Needs to be solved for each receptor point (grid cell, but can be solved for any arbitrary location)
Steady state solution: provides an upper estimate of concentration
14
Data requirements:Data requirements:Data requirements:Data requirements:• Emission data (stack properties)
• Meteorology:– Single station data (episode, or 24 hours, one
year (hourly)): wind speed/direction, air temperature (plume rise)
– Vertical profile (mixing layer) one morning sounding (value)
– Solar radiation, cloud cover (heat budget)
• Emission data (stack properties)
• Meteorology:– Single station data (episode, or 24 hours, one
year (hourly)): wind speed/direction, air temperature (plume rise)
– Vertical profile (mixing layer) one morning sounding (value)
– Solar radiation, cloud cover (heat budget)
15
AERMET pre-processor:AERMET pre-processor:AERMET pre-processor:AERMET pre-processor:
AERMET operates on data from:
• National Weather Service (NWS) hourly surface observations,
• NWS twice-daily upper air soundings,
• data collected from an on-site measurement program such as from an instrumented tower.
AERMET operates on data from:
• National Weather Service (NWS) hourly surface observations,
• NWS twice-daily upper air soundings,
• data collected from an on-site measurement program such as from an instrumented tower.
16
AERMET data requirements:AERMET data requirements:AERMET data requirements:AERMET data requirements:Hourly Surface Observations:• wind speed and direction;• ambient temperature;• opaque sky cover; in the absence of opaque sky
cover, total sky cover;• station pressure is recommended, but not
required,
Upper Air Soundings:• morning sounding (the 1200 GMT sounding for
applications in the United States).
Hourly Surface Observations:• wind speed and direction;• ambient temperature;• opaque sky cover; in the absence of opaque sky
cover, total sky cover;• station pressure is recommended, but not
required,
Upper Air Soundings:• morning sounding (the 1200 GMT sounding for
applications in the United States).
17
AERMOD implementation:AERMOD implementation:AERMOD implementation:AERMOD implementation:For City/local domains (< 30 km),
• Hourly now-cast runs;
• Daily 24 hour forecast runs;
• Interactive scenario analysis:– 24 hours daily runs (domains)– Annual runs (domains);– EIA for domains (24 hours)– EIA for single sources (annual, hourly)– Monitoring station location (annual, hourly)
For City/local domains (< 30 km),
• Hourly now-cast runs;
• Daily 24 hour forecast runs;
• Interactive scenario analysis:– 24 hours daily runs (domains)– Annual runs (domains);– EIA for domains (24 hours)– EIA for single sources (annual, hourly)– Monitoring station location (annual, hourly)
18
AERMOD implementation:AERMOD implementation:AERMOD implementation:AERMOD implementation:High-resolution (10 m) convolution model
(kernel), for all models that include traffic emissions (large number of segments).
Includes a mixing-zone approach over the street surface.
Unit emission kernel scaled for each road segment (10 m elements).
Transparently integrated with all AERMOD runs.
High-resolution (10 m) convolution model (kernel), for all models that include traffic emissions (large number of segments).
Includes a mixing-zone approach over the street surface.
Unit emission kernel scaled for each road segment (10 m elements).
Transparently integrated with all AERMOD runs.
19
AERMOD configuration:AERMOD configuration:AERMOD configuration:AERMOD configuration:For each mode of operation (nowcast,
forecast, interactive scenarios, single source EIA, MS location, traffic)
the model needs:
•A model scenario
•A meteorological scenario
•An emission scenario
For each mode of operation (nowcast, forecast, interactive scenarios, single source EIA, MS location, traffic)
the model needs:
•A model scenario
•A meteorological scenario
•An emission scenario
20
AERMOD scenarios:AERMOD scenarios:AERMOD scenarios:AERMOD scenarios:
Nowcast scenarios are organised by domain, and shown for the current (latest) run;
Configuration of a nowcast scenarios:
• Select NEW from the scenario list;
• Edit the scenario (domain, meteorlogy, emissions)
• Edit the shell script entry (ADMIN only)
Nowcast scenarios are organised by domain, and shown for the current (latest) run;
Configuration of a nowcast scenarios:
• Select NEW from the scenario list;
• Edit the scenario (domain, meteorlogy, emissions)
• Edit the shell script entry (ADMIN only)
21
22
23
24
25
26
27
AERMOD implementationAERMOD implementationAERMOD implementationAERMOD implementationInteractive scenarios:• 24 hour runs including comparison of
scenarios (domain level impact assessment);
• High-resolution 1 hour runs for individual street segments
• Annual runs for monitoring station location (single source)
• Annual runs for single source impact assessment.
Interactive scenarios:• 24 hour runs including comparison of
scenarios (domain level impact assessment);
• High-resolution 1 hour runs for individual street segments
• Annual runs for monitoring station location (single source)
• Annual runs for single source impact assessment.
28
AERMOD interactive:AERMOD interactive:AERMOD interactive:AERMOD interactive:
24 hour runs including comparison of scenarios (domain level impact assessment);
• Listing of scenarios with name, simulation date, pollutant simulated, run status (results, ready to runready to run, running).
• NEW button for creating a new scenario
24 hour runs including comparison of scenarios (domain level impact assessment);
• Listing of scenarios with name, simulation date, pollutant simulated, run status (results, ready to runready to run, running).
• NEW button for creating a new scenario
29
30
31
32
AERMOD implementationAERMOD implementationAERMOD implementationAERMOD implementationInteractive scenarios:
• High-resolution 1 hour runs for individual street segments
• High resolution kernel/convolutions for 24 hourly runs, transparently combined with AERMOD for point and area sources.
Interactive scenarios:
• High-resolution 1 hour runs for individual street segments
• High resolution kernel/convolutions for 24 hourly runs, transparently combined with AERMOD for point and area sources.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
AERMOD implementationAERMOD implementationAERMOD implementationAERMOD implementationInteractive scenarios:Annual runs for monitoring station location
(single source):
• Finds the N locations (for possible monitoring stations) with a user defined minimum distance AROUND an emission source with the highest annual average concentration over populated areas.
Interactive scenarios:Annual runs for monitoring station location
(single source):
• Finds the N locations (for possible monitoring stations) with a user defined minimum distance AROUND an emission source with the highest annual average concentration over populated areas.
53
54
55
56
57
AERMOD implementationAERMOD implementationAERMOD implementationAERMOD implementationInteractive scenarios:
Annual runs for single source impact assessment:
• Computes annual average concentration on an hourly basis around a single source, at user defined or automatically located simulated monitoring stations.
Interactive scenarios:
Annual runs for single source impact assessment:
• Computes annual average concentration on an hourly basis around a single source, at user defined or automatically located simulated monitoring stations.
58
59
60
61
62
63
64