| Wiki Markup |
|---|
{scrollbar} |
| Table of Contents |
|---|
Introduction
The configuration of DELFT-FEWS is defined in a set of XML files. In this section the different parts of the configuration are introduced. An understanding of these different parts of the configuration is required before attempting configuration of a DELFT-FEWS system.
...
Configuration Item | Directory on File System | Table name in file system | Single/ |
Definition of regional configuration, including all locations, parameters etc. | RegionConfigFiles | RegionConfigurations | Single |
Definition of system configuration items, including the plug-ins available to the system, definition, icons etc. | SystemConfigFiles | SystemConfigurations | Single |
Definition of modules for handling data and running forecasting models | ModuleConfigFiles | ModuleInstanceConfigs | Multiple |
Definition of workflows for running sequences of modules | WorkflowFiles | WorkflowFiles | Multiple |
Cold states for modules. Zip file containing model specific data exported by GA usually before running a model | ColdStateFiles | ColdStateFiles | Multiple |
Definition of mapping of ID's and parameters between external sources (e.g. telemetry, modules) and ID's and parameters defined in the DELFT-FEWS configuration | IdMapFiles | IdMaps | Multiple |
Definition of unit conversions between external sources (e.g. telemetry, modules) and units used in DELFT-FEWS | UnitConversionFiles | UnitConversions | Multiple |
Definition of flag conversions between external sources (e.g. telemetry, modules) and flags used in DELFT-FEWS | FlagConversionFiles | FlagConversions | Multiple |
Definition of layout of user displays, including What-if scenarios, Grid Display etc.) | DisplayConfigFiles | DisplayConfigurations | Multiple |
Definition of module parameters stored in DELFT-FEWS | ModuleParameters | ModuleParameters | Multiple |
Zipped files containing datasets for modules used by the forecasting system. | ModuleDataSetFiles | ModuleInstanceDatasets | Multiple |
Definition of HTML template files used in creating HTML reports for use on the web server. | ReportTemplateFiles | ReportTemplates | Multiple |
Map layers (shape files) used in main map display and spatial interpolation | MapLayerFiles | MapLayerFiles | Single |
Images used in reports etc | ReportImageFiles | ReportImageFiles | Single |
Icons used in main map display and button bar | IconFiles | IconFiles | Single |
Table 2 Overview of different configuration items contained in the file system only
...
In the database the default version for each configuration item is identified in an associated table. For each configuration item a default table is available. This is identified by a table with the same name, prefixed by "Default". For example for the SystemConfigurations a table with the name DefaultSystemConfigurations identifies which of the available versions in the former table is to be used a default.
Naming conventions for defining module config files
For complex forecasting systems the number of configuration files can be very large. This is particularly the case for the module config files, and because the names of these are used in Time Series Sets for storing and retrieving data, the names given should be chosen logically. Before configuring large numbers of XML files it is wise to define a naming convention and use this throughout. An example of such a convention is where a number of steps are used to process data prior to running a model.
A forecast model run for the HBV model in the Rhine may be defined in a module called:
HBV_Rhine_Forecast.xml
Data processing steps such as an interpolation module may then be called
HBV_Rhine_ForecastInterpolate.xml
Or a data merge module
HBV_Rhine_ForecastMergeInputs.xml
This clearly indicates the association between modules and brings structure to the configuration.
XML Schemas and schema validation
...