AirWare
air quality assessment & management
Reference and User Manual
     
      AirWare   On-line Reference Manual
        Release Level 6.2
        Release Date 2013 09
        Revision Level 1.0
      Last modified on:   Friday, 20-Dec-13 11:52 CET

      Environmental Impact Assessment: annual runs

      AirWare provides an option to perform a screening level impact assessment for any set existing, hypothetical new, or modified point, area or line emission sources within any user defined domain.

      This is based on annual runs of the AERMOD model with an hourly resolution.

      Depending on data availability, the assessment results can include:

      1. Average and maximum concentrations (annual average of hourly values) in a user defined domain around the source and any number of user defined target areas (receptor areas);
      2. Area above a user defined reference concentration for the domain as well as a user defined impact zone around the source, comparing values inside and outside that zone;
      3. Population exposed to an annual average concentration above a user defined level (require spatially distributed population data;
      4. Detailed statistics of maxima and violations/exceedances:
        • Listing and map display of the 30 maxima;
        • listing and map display of exceedances: maxima, average above threshold;
        • percentile values of axceedances, map of concentration above standard, display of maxima in every category, with a user defined distance filter.

      Impact scenarios

      The primary scenario parameters to be selected include the model domain and associated emission sources. Other top level buttons lead to a scenario checker (for the underlying meteorological scenario);
      The button "reset" or abort" control the model run;
      the button "Maxima" leads the a detailed presentation of the assessment results.

      The impact assessment works on the basis of the standard emission inventory, with an emission scenario automatically generated for the selected model domain. The EIA model is implemented for point, area sources and line sources that can be toggled on/off in the listing for each group.

      Domain/Source selection:   the first user choice is the selection of a model domain and the associated emission sources in the emission scenario, or the definition of one or more new emissions sources as part of the domain specific emission inventory.

      The source to be evaluated is selected from the coresponding OBJECT data base (by source type) or the emission inventories (by geographical domain). Links (button: emissions) are part of the impact assessment start and main scenario page.

      If a new source is being defined for the purpose of the assessment, tagging it as hypothetical or planned, will exclude it from consideration from the normal scheduled daily and hourly model runs, but add it to the list of sourcs that can be selected in the emission scenario.

      Model period and meteorology   for the impacts scenario, a period (a calender year, selected at the scenario main page) and a meteorological data source (button: Meteorology) must be selected. Data sources can be monitoring data, MM5/NFL re-analysis data, or an AERMET file.

      Scenario parameters:

      Model scenario parameters include:

      • Simulation year;
      • Meteorological data sources (read only, selected via the Meteorology button/dialog);
      • Pollutant:   the user can select a (conservative or first order decaying) pollutant from the pull-down menu, the emission strength and temporal emission patterns are automatically copied from the emission inventory.
      • model domain and size (read only selected via the Domain button/dialog)
      • model resolution
      • Albedo, roughness(refers to the location of the meteorological data source), Bowen ratio
      • use of an AERMET file
      • run option: fastall option (yes/no)
      • AERMOD standard model output directory (automatically generated, active directory link)

      For PM10, the assessment will be performed in terms of daily (24 hour) averages, compliant with the European air quality standards (2008/50/EC).

      Thresholds and standards: the impact assessment is done in reference to threshold or standard values for ambient concentration the user can specify for

      • short-term (hourly values, and daily average for PM10)
      • long-term (annual average and maxima).

      Run request:   with the scenario defined, the user can submit a run request. If the (meteorological) data are complete (checker function) and all necessary scenario parameters have been defined completely and consistently, the model will be run for 24*365 hours. Depending on settings (domain size and resolution, run mode), this may take several hours.

      The run request will be confirmed in a separate dialog box, where an eMail address for notification when the run is completed can be specified.

      Runs on external compute servers:   to exploit fast, dedicated multi-core hardware for long-term (annual) model runs, these can be started on external compute servers (subject to the respective configuration of these servers;

      After defining the scenario on the local application server, the remote run can be started using the SCENARIOID:

      • login to the compute server; then type:
      • sudo /var/www/cgi-bin/aermod/runEIA.sh $SCENARIOID
      • to view the log for each scenario, use:
        tail /data/PROJECT/aermod/eia/logs/aermod_$SCENARIOID.log

        Assessment results are described on a separate page.


© Copyright 1995-2016 by:   ESS   Environmental Software and Services GmbH AUSTRIA | print page