...
First the background of the topology.xml wil be explained in the overview section. In the following sections Configuration of nodes and Configuration of states, forecast lengths and time zero the most important configuration features of the topology.xml will be explained. In the last section all the configuration options will be explained in the order in which they can be found in the topology.xsd schema.detail.
Overview
The topology.xml is a mandatory configuration file when you are setting up an IFD-environment. This configuration file is used to configure the topology of a FEWS-system.
...
| Code Block |
|---|
<?xml version="1.0" encoding="UTF-8"?> <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="C" name="C"> <node id="A" name="A"/> <node id="B" name="B"/> </nodes> </topology> |
It is possible to run a workflow in IFD mode or in server mode workflows from the topology panel. In the example below some of the node(s) have a workflow configured.
| Code Block |
|---|
<?xml version="1.0" encoding="UTF-8"?> <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="C" name="C"> <workflowId>workflowC</workflowId> <node id="A" name="A"> <workflowId>workflowA</workflowId> </node> <node id="B" name="B"/> </nodes> </topology> |
...
By default all the workflows started from a leaf node are started in IFD mode. Workflows which are started from a group node are always started in server mode.
The results of an IFD-This means that the results of the run are only temporary available in FEWS and that the results (until the next restart) and are only available visible at the operator client which started the run. As soon as the FEWS system is restarted all the IFD runs will be deleted.
IFD runs are typically used to evaluate the effect of modifiers on the results of a forecast. A workflow which is started from a group node will by default be started as a server run. A server run will run at a FSS when it is started from an operator client. When it is started from a stand alone it will run locally but the results of the run will be available after a restart of the system.
...
However if for a node the option initialForecastLengthCardinalTimeStep is configured then the end time of the node stays the same if the time zero changes.
Below a configuration example of a node for which a forecast length, an initialForecastLengthCardinalTimeStep and a cardinalTimeStepForecastLength is configured.
...