Page History

...

Both of them belong the group node C.

Code Block

language	xml

<?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 workflows from the topology panel. In the example below some of the node(s) have a workflow configured.

Code Block

language	xml

<?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>

...

In the example below the runs from leaf node B will run in server mode and the runs started from the group node C will run in IFD mode.

Code Block

language	xml

<?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>
		<localRun>true</localRun>
		<node id="A" name="A">
			<workflowId>workflowA</workflowId>
			<localRun>false</localRun>
		</node>
		<node id="B" name="B"/>
	</nodes>
</topology>

...

It is possible to connect nodes in the topology. In the example below the node STKA2 is connected to two previous nodes (SBFQ2 and ISKQ2).

Code Block

language	xml

<node id="STKA2" name="STKA2 Stikine R Wrangell">
		<previousNodeId>SBFQ2</previousNodeId>
		<previousNodeId>ISKQ2</previousNodeId>
		<workflowId>STKA2_Forecast</workflowId>
</node>

...

The forecast length will be determined by the forecast length estimator. After the first run for a node the a time chooser will be shown which will allow the forecaster to edit the forecast length which was determined by the forecast length estimator.

Code Block

language	xml

nodes id="APRFC">
		<showModifiers>true</showModifiers>
		<workflowId>APRFC_Forecast</workflowId>
		<warmState unit="day" multiplier="10"/>
		<!-- Topology added for forecast group Southeast -->
		<nodes id="Southeast" name="Southeast">
			<workflowId>Southeast_Forecast</workflowId>

...

An configuration example is shown below.

Code Block

language	xml

<node id="SRYA2" name="SRYA2 Situk R nr Yakutat">
			<workflowId>SRYA2_Forecast</workflowId>
			<useForecastLengthFromInteractiveForecastDisplay>false</useForecastLengthFromInteractiveForecastDisplay>
</node>

...

A configuration example is given below.

Code Block

language	xml

<nodes id="Southeast" name="Southeast">
	<workflowId>Southeast_Forecast</workflowId>
	<warmStateSelectionPeriod unit="day" start="-12" end="-9"/>
	<node id="SRYA2" name="SRYA2 Situk R nr Yakutat">
		<workflowId>SRYA2_Forecast</workflowId>
		<useForecastLengthFromInteractiveForecastDisplay>false</useForecastLengthFromInteractiveForecastDisplay>
</node>

...

An configuration example is given below.

Code Block

language	xml

	<nodes id="WAPN6HUD_calb" name="WAPN6HUD">
				<workflowId>WAPN6HUD_Stats_Calibration</workflowId>
				<coldState unit="day" multiplier="18628"/>
				<node id="WAPN6HUD_Waterbalance_Multi-year" name="Waterbal_MY">

...

A configuration example is given below.

Code Block

language	xml

<nodes id="Southeast" name="Southeast">
	<workflowId>Southeast_Forecast</workflowId>
	<noInitialState></noInitialState>

...

This option is used, for example, in the HERMES-system. Below a configuration example:

Code Block

language	xml

<node id="ProcessTest" name="Process Data">
	<workflowId>ProcessImports</workflowId>
	<relativePeriod unit="day" start="-30" end="0"/>
	<localRun>false</localRun>
</node>

...

A configuration example is shown below.

Code Block

language	xml

<node id="Process" name="Process Data">
	<previousNodeId>Import</previousNodeId>
	<workflowId>ProcessImports</workflowId>
	<relativePeriod unit="day" start="-10" end="-5"/>
	<cardinalTimeStepStartTime unit="hour" multiplier="6"/>
	<initialStartTimeCardinalTimeStep unit="hour"/>
	<cardinalTimeStepEndTime unit="hour" multiplier="6"/>
	<initialEndTimeCardinalTimeStep unit="hour"/>
	<localRun>false</localRun>
</node>

...

This panel can be configured in the following way.

Code Block

language	xml

<node id="ProcessTest" name="Process Data">
            <workflowId>ProcessImports</workflowId>
            <relativeStartTime unit="day" value="-10"/>
            <localRun>false</localRun>
 </node>

...

Below a configuration example

Code Block

language	xml

<node id="rainfallpolicy_tweed" name="Set Rainfall Policy">
	<workflowId>Tweed_Rainfall_Forecast</workflowId>
	<coldStateFromCurrentRun>
		<workflowId>Tweed_URBS_IFD_Forecast</workflowId>
		<coldState unit="day" multiplier="2"/>
	</coldStateFromCurrentRun>
	<defaultModifierId>Rainfall Policy</defaultModifierId>
	<visibleModifierGroup>URBS_Official_Rainfall</visibleModifierGroup>
	<localRun>true</localRun>
	<showRunApprovedForecastButton>false</showRunApprovedForecastButton>
</node>

...

Below a configuration example of a node for which a forecast length, an <initialForecastLengthCardinalTimeStep> and a <cardinalTimeStepForecastLength> is configured.

Code Block

language	xml

<node id="B10_Main_RTC" name="Run model">
	<workflowId>Big10_RTCTools_RT</workflowId>
	<forecastLength unit="hour" multiplier="24"/>
	<cardinalTimeStepForecastLength unit="hour"/>
	<initialForecastLengthCardinalTimeStep id="HE6"/>
	<displayGroupId>Main_RT-RTC</displayGroupId>
	<timeSeriesButtonsPanelId>RT_buttons_Main</timeSeriesButtonsPanelId>
	<viewPermission>execute</viewPermission>
	<visibleModifierGroup>RT</visibleModifierGroup>
	<graceTime unit="hour" multiplier="1"/>
	<localRun>true</localRun>
	<saveLocalRunEnabled>true</saveLocalRunEnabled>
	<showRunApprovedForecastButton>true</showRunApprovedForecastButton>
</node>

...

The code snippet below shows a configuration example.

Code Block

language	xml

<node id="ZWF_LHM_Z0_REF2017BP18" name="Files LHM zonder zout">
	<workflowId>ZWF_LHM_Z0_REF2017BP18</workflowId>
	<timeZero date="2004-01-01" time="00:00:00"/>
	<localRun>false</localRun>
</node>

...

To make the time zero editable and/or to shfit the time zero compared to the system time the option <timeZeroShift> can be used.

Code Block

language	xml

<nodes id="WaterOrder HADT1" name="Water Order Apalachia">
	<timeZeroShift unit="hour" multiplier="0"/>
	<node id="WaterOrder_HADT1" name="Adjust Water Order">
		<locationId>HADT1</locationId>
		<workflowId>CalculateSpill_WaterOrder_HADT1</workflowId>

...

An example of a topology group file is shown below.

Code Block

language	xml

<?xml version="1.0" encoding="utf-8"?>
<topologyGroup 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/topologyGroup.xsd">
	<group id="ForecastGroup_Bear">
		<nodes id="Bear" name="Bear">
			<workflowId>Bear_Forecast</workflowId>
			<node id="MergeMAPBear" name="MergeMAP and Outflow">
				<workflowId>Bear_Forecast</workflowId>
				<moduleInstanceId>SetTimes_Forecast</moduleInstanceId>
				<moduleInstanceId>MergeMAP_Bear_Forecast</moduleInstanceId>
				<moduleInstanceId>Merge_RiverWare_Observed_QT</moduleInstanceId>
				<visibleModifierGroup>None</visibleModifierGroup>
			</node>
		</nodes>
	</group>
</topologyGroup>

...

The defined topology groups can be used in the topology.xml by using the element <groupId>. An example is shown below.

Code Block

language	xml

<nodes id="InflowForecast" name="Inflow Forecast">
			<warmState unit="day" multiplier="11"/>
			<groupId>ForecastGroup_Bear</groupId>

...

An example is shown below.

Code Block

language	xml

<?xml version="1.0" encoding="utf-8"?>
<topologyGroup 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/topologyGroup.xsd">
	<group id="ForecastGroup_Bear">
		<nodes id="Bear" name="Bear">
			<workflowId>Bear_Forecast</workflowId>
			<node id="MergeMAPBear" name="MergeMAP and Outflow">
				<mainPanel>modifiers panel</mainPanel>
				<toolWindow>plot overview</toolWindow>
			</node>
		</nodes>
	</group>
</topologyGroup>

...

An config example is shown below.

Code Block

language	xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2014 rel. 2 sp1 (http://www.altova.com) by Afdeling ICT (Stichting Deltares) -->
<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">
	<enableOriginalButtons>true</enableOriginalButtons>
	<enableAutoRun>false</enableAutoRun>
	<nodes id="NWM" name="Nationaal Water Model">
		<nodes id="Zoetwater" name="Zoetwater">
			<groupId>GroupZoetwater</groupId>
		</nodes>
		<nodes id="Zoetwater_files" name="Prepare Zoetwater files">
			<groupId>GroupZoetwater_Files</groupId>
		</nodes>
	</nodes>
</topology>

...

Page tree

Versions Compared

Old Version 83

New Version 84

Key