Reference & User Manual
|Release Level||7.0||Release Date||2016 12||Revision Level||beta|
|Last modified on: Saturday, 5-Nov-16 20:07 CET|
Meteorological scenarios are consistent and complete data sets of the meteorological variables, primarily wind field and temperature, required by WaterWare (model time series).
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.
The key hydro-meteorological parameters used in WaterWare are precipitation and air temperature; Additional parameters that can be extracted from MM5 model runs include:
A METEO SCENARIO OBJECT is described by the
Data RequirementsThe maintain a uniform and consisten data interface, the scenario generators read their data from one or more meteorological monitoring stations that can include virtual stations representing upper air (geostrophioc) data.
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
© Copyright 1995-2016 by: ESS Environmental Software and Services GmbH AUSTRIA | print page