Release Level	5.3.0 beta
Release Date	2007 06
Revision Level	1.1

Meteorological Scenarios

Meteorological scenarios are named OBJECTS that are derived from the monitoring data from one or more applicable (nearby) meteorological stations, the interpolation of several station, of from some meteorological model or pre-processor including the optional non-hydrostatic meteorological forecasting model MM5 that operates with global meteorological model data as its input.

Meteorological scenarios are generated by model specific Meteorological Scenario Generators that ensures synchronization, completeness and consistency of the meteorological time series data for the respective simulation model or their dedicated meteorological pre-processors.

Access to a Meteorological Scenario is through a BUTTON Meteorologyat the corresponding model scenario.

Meteorological scenarios are part of either:

• scheduled model scenarios, where they are generated automatically and read only for the user, but available for inspection;
• interactive scenarios, where they are generate under interactive control and choices (date, stations) by the user.

• For CAMx, they are spatially distributed an vertically layered; they can be generated either by the optional non-hydrostatic meteorological model MM5, or a combination of the diagnostic wind model DWM and a CAMx specific meteorological pre-processor that generates distributed and layered data from individual station data.

• For AERMOD, the data are extracted from one (or more spatially averaged) observations stations, including an upper atmosphere station, and processed by the AERMET meteorological pre-processor, that generates hourly values, averaged over the model domain.

  
  

• For PBM, meteorological scenario can be
  • defined interactively by the user for interactive scenarios analysis,
  • extracted from existing meteorological observations from the data base for historical periods;
  • automatically used from real-time monitoring statiuons including forecasted data at a station level

Different meteorological parameters are required or estimated by the respective pre-processors. A METEO SCENARIO OBJECT is described by the

1. standard OBJECT header;
2. Description of the generation method and parameters where applicable, and the raw meteo data (station) it was generated from.
3. Basic attributes:
   • Start date and duration (inherited from the corrsponding model scenario)
   • Model Domain for which the scenario is applicable
   • Grid resolution
   • Time series for (anemometric) station specific or spatially averaged wind speed, direction, and temperature.
   • Time series for (upper atmosphere) station specific or spatially averaged wind speed and direction.

4. Meteo Station Selection:

   the currently selected meteo station is shown by name, the name is a link to the station OBJECT.

   Once a station is being displayed, it can be added to the list with a SELECT button. The DEFAULT station (for a new domain) is the nearest (measured from the center point of the model domain) meteorological monitoring station with available real-time data.

   Any but the last of the stations on the list can be dropped (excluded) from consideration by thre user.

   At least one anemometric station, and station for upper air data (geostrophic) must be available for a feasible meteorological scenario.

5. For interactive scenarios: Generate BUTTON: triggers the scenario generation, depending on the model (CAMx, AERMOD, PBM) and the scenario (hourly, daily); the results of the Generator are shown as a combination of scalar values, time series, or matrices of vector (wind) or scalar (temperature, humidity, etc.) data. The BUTTON is shown in RED if the scenario must be updated; The BUTTON is shown in GREEN if the results are available and consistent with the current selection of meteo stations.

   If consistent results are available, the user can choose the parameter, vertical layer and time step for matrix display.

Scenario Generator

Data Requirements

The stations required for each model scenario are defined in the respective scernarion, and can be modified (selected and de-selected) by the user interactively. For interactive scenarios, this selection becomes effective immediately for the current run, for scheduled runs it will become effective for the next model run and thereafter.

When a meteorological scenario is requested, the preprocessor first checks data availability for the stations defined for that scenario, and for the period selected. If no data can be found, the run or model scenario is aborted and a corresponding error message is logged in the System Log Files.