Function: |
Configure topology of an IFD environment |
Where to Use? |
Mandatory for a IFD installation |
Why to Use? |
The topology.xml is necessary to be able to use panels like the topology panel and the forecast panel |
Description: |
Topology panel is used to define the topology of an IFD environment. Also the behaviour of the forecast panel which is used to start |
Available since: |
DelftFEWS201001 |
Contents
Overview
The topology.xml is an mandatory configuration file when you are setting up an IFD-environment. This configuration file is used to configure the topology of a region.
The topology is defined by individual nodes. The topology can be viewed in the topology panel, which shows a block diagram of the topology, or in the forecast panel, which shows
a tree view of the topoloy. The behaviour of the forecast panel can also be configured in the topology-file. A workflow can be configured for a topology-node. By default the workflow will
run locally when the node is selected in the forecast panel. This can be switched off by setting the option enableAutoRun to false.
The topology.xml plays a central role in configuring an IFD-environment since it is used to configure the forecast panel which is the central panel in an IFD-environment.
Configuration
Qualifier definition
Qualifiers are defined in the regionConfigFiles directory. An example looks like:
<topology xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/topology.xsd"> <nodes id="ABRFC"> <nodes id="NMWTX" name="NMWTX"> <workflowId>NMWTX_Forecast</workflowId> <node id="EGLN5" name="EAGLE NEST DAM"> <workflowId>EGLN5_Forecast</workflowId> </node> <node id="CMMN5" name="CIMARRON 4SW"> <previousNodeId>EGLN5</previousNodeId> <workflowId>CMMN5_Forecast</workflowId> </node> <node id="CMRN5" name="CIMARRON"> <localRun>false</localRun> <workflowId>CMRN5_Forecast</workflowId> </node>
Time Series
The most useful way is first to read all locations from the DBF into one locationSet, where all attributes are assigned.
See for example:
<timeSeriesSet>
<moduleInstanceId>ImportCAW</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.meting</parameterId>
<qualifierId>min</qualifierId>
<locationSetId>Boezem_Poldergemaal_H.meting</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<relativeViewPeriod unit="day" start="-6000" end="0"/>
<readWriteMode>editing visible to all future task runs</readWriteMode>
<synchLevel>5</synchLevel>
</timeSeriesSet>
