...
A failed run is indicated by an icon with a exclamation mark 
. If the time zero of the failed run is equal to the time zero of the node the exclamation mark will be red 
otherwise it will be black. 
In the example below the node Matsu has a failed run with a time zero equal to the time zero of the IFD (09-19-2012). When time zero changes (because the system time was changed) the icons also change. The red exclamation marks are changed to black.
Modifiers
When a modifier is made at a node with a local successful run then the icon will change to a yellow icon with a blue check (local run) 
or yellow icon with a green check (server run)
to indicate that the workflow of that node needs to rerun.
In the example below a modifier was made to the node KUPA2.
State selection
If the user changes the state selection in the IFD so that the state selection used in the run doesn't match the state selection in the IFD anymore then the icon will turn to a yellow icon with a blue check (local run) or yellow icon with a green check (server run)to indicate that the node needs to be rerun. An example is shown below
Forecast length
If a user increases the forecast length the status will also be set to invalid and change to the icon to a yellow icon with a blue check (local run) or yellow icon with a green check (server run)to indicate that the node needs to be rerun.
Previous node has an invalid status
The results of a node can only be valid if all the previous nodes have run successfully prior to the run of a node and when all the previous nodes have valid status.
In the example below node TUNA2 has a successfull status. When the user reruns the previous node NEBA2 then node TUNA2 also needs to rerun to make sure that its results are up-to-date. To indicate this the icon of node TUNA2 is changed to a yellow icon with a blue check (local run) .
Time zero different and another item is invalid
When the time zero of the node is different than the time zero of the workflow and at the same time one of the conditions below is true
...
then the icon will change into a grey icon with a yellow checkmark (server runs and local runs)
. Below a few examples.
Red outline
As of 2016.01, The IFD status icon can be surrounded by a red outline. See figure below. This red outline surrounding the IFD status icon indicates that the workflow task completed but not all of the data has been synchronised back to the operator client. This red outline feature is disabled for DDA clients as it pertains only to synchronisation in LDS clients.
...
The file-menu also provides an option default layout. By selecting this option the default layout can be reloaded.
Contents
| Table of Contents | ||
|---|---|---|
|
Which displays are used in the IFD?
The IFD (Interactive Forecasting Displays) consists of several panels. Each of these panels has a specific role in the process of creating a forecast with the IFD. In this chapter the functionality of each panel in the IFD will be explained.
In chapter How to create a forecast with the IFD will be explained with a use case how a forecast can be created with the IFD by using the combined functionality of the separate panels.
Forecast panel
The forecast panel (indicated in yellow rectangle above) plays a central role in creating a forecast in the IFD. The forecast panel shows a tree with all the forecast points for a region and a logical grouping of these forecast points.
It is also possible to show the work process of a forecaster in the forecast panel. The forecast panel consists of three main sections each of them will be explained in detail in the coming sections.
Button bar
The top of the forecast panel shows a button bar. By default this button bar will look like this.
In the panel below the buttons are explained in the detail.
...
...
- option <localRun> is set to true
- user has the permission <runWorkflowLocallyPermission> or this option is not configured
...
- option <localRun> is set to false
- option <showRunApprovedForecastButton> is set to true
...
...
If the button is selected the threshold icons will be shown instead
of the regular run status icons
...
...
...
...
- option <localRun> is set to false
- option <showRunApprovedForecastButton> is set to true
...
updates the system time to the current time.
...
...
The forecast tree is shown in the middle section of the forecast panel.
The tree consists of two types of nodes:
- workflow nodes: nodes which can be used to start forecasts and view the results of their forecasts,
- view nodes: nodes without a workflow, these nodes are used for viewing purposes.
The status of the workflow of the workflow nodes is indicated by an icon.
The icon can indicate the following statuses:
- Running,
- Pending,
- Failed,
- Succesfull
- Succesfull but the time zero of the run is different then the time zero of the IFD,
- Succesfull but the workflow needs to be rerun because the state selection was changed, a modifier was created after the run or the forecast length is changed,
- A combination of the 2 statuses above.
Below an overview of all the combinations which are available for a succesfull run (local or server).
Running
A workflow which is running locally or at the server will be indicated by a curved arrow icon.
In the example below the workflow of the node ALKA2 is running.
Pending
A workflow that is pending to run is indicated by an hourglass 
. In the example above all the nodes below ALKA2 are pending.
Succesfull run
If a workflow was fully succesfull the node will have a blue 
or green icon 
.
A local succesfull run will be indicated by a blue icon a succesfull server run will be indicated by a green icon .
In the example below a server run has run succesfully run for node North Slope. For the leaf nodes KUPA2, SGRA2 and CRUA2 a successfull IFD run was executed.
Successful run with a different time zero
If the time zero of a node is different than the time zero which was used in the successful run then the icons will be different.
The example below shows a screenshot of the same Delft-FEWS system as shown above but now with a different time zero.
The icons are grey instead of green and blue and the check marks are now blue and green.
Failed run
A failed run is indicated by an icon with a exclamation mark . If the time zero of the failed run is equal to the time zero of the node the exclamation mark will be red otherwise it will be black.
In the example below the node Matsu has a failed run with a time zero equal to the time zero of the IFD (09-19-2012).
When time zero changes (because the system time was changed) the icons also change. The red exclamation marks are changed to black.
Modifiers
When a modifier is made at a node with a local successful run then the icon will change to a yellow icon with a blue check (local run) or yellow icon with a green check (server run)to indicate that the workflow of that node needs to rerun.
In the example below a modifier was made to the node KUPA2.
State selection
If the user changes the state selection in the IFD so that the state selection used in the run doesn't match the state selection in the IFD anymore then the icon will turn to a yellow icon with a blue check (local run) or yellow icon with a green check (server run)to indicate that the node needs to be rerun.
An example is shown below
Forecast length
If a user increases the forecast length the status will also be set to invalid and change to the icon to a yellow icon with a blue check (local run) or yellow icon with a green check (server run)to indicate that the node needs to be rerun.
Previous node has an invalid status
The results of a node can only be valid if all the previous nodes have run successfully prior to the run of a node and when all the previous nodes have valid status.
In the example below node TUNA2 has a successfull status. When the user reruns the previous node NEBA2 then node TUNA2 also needs to rerun to make sure that its results are up-to-date.
To indicate this the icon of node TUNA2 is changed to a yellow icon with a blue check (local run) .
Time zero different and another item is invalid
When the time zero of the node is different than the time zero of the workflow and at the same time one of the conditions below is true
- state selection is different,
- a previous node has an invalid status,
- a modifier was created or changed after the run was finished,
- the forecast length is changed.
then the icon will change into a grey icon with a yellow checkmark (server runs and local runs). Below a few examples.
Red outline
As of 2016.01, The IFD status icon can be surrounded by a red outline. See figure below. This red outline surrounding the IFD status icon indicates that the workflow task completed but not all of the data has been synchronised back to the operator client. This red outline feature is disabled for DDA clients as it pertains only to synchronisation in LDS clients.
Task properties panel
The bottom section of the forecast panel can be used to select the task properties of a node.
The following properties can be changed or set:
- State selection,
- Time zero,
- Forecast length,
- User description for the workflow,
- What-if scenario.
The majority of these settings can be adjusted in the bottom section of the panel.
More options are available in the panel which can be started by clicking on the "edit run options" button.
...
In the following section 24 Topology is described which configuration options are available.
Modifiers panel
The modifiers panel is an important display in the IFD. It shows the modifiers which are created for the selected node in the forecast panel or (since 2019.02) the modifiers for the grid plot on which spatial modifier mode has been activated. Modifiers can be created, modified or deleted in this panel.
The upper part of the display gives an overview of the modifiers created for the currently selected node in the forecaster panel. When a modifier is selected in this panel, the details will be shown in the lower part of the panel. It also allows the user to make mods active and inactive with the checkbox in the column Active. When a modifier is made locally, it get's a salmon background color. When it is saved to the server (by running the associated WF on the server), it gets a green background color.
A mod can be deleted by pressing the cross icon. If you have made a local change to a saved modifier, only the local change will be deleted when you press the cross. The background color will change back from salmon to green. If you delete it again, the saved modifier will be deleted as well. (Note, in a SA the behavior is different. In a SA a single delete action deletes the entire modifier.) If you make use of the Run Info panel (see Explorer Tasks, with <taskClass>nl.wldelft.fews.gui.plugin.runinfo.RunInfoPanel</taskClass>), this will show both the saved and local modifiers, so you can compare them directly.
The copy-icon copies the modifier.
...
Spatial display
Since 2019.02, there are modifier types which are used to modify grid time series. These spatial modifiers need to be created through the spatial display instead of the modifiers panel. More information on how to create spatial modifiers in the spatial display is found at User Guide > 05 Spatial Display > Creating Spatial Modifiers.
Topology panel
The topology panel shows the topology of the selected node. When a leaf node is selected the topology of the children of the parent node is shown. When a parent node is selected the topology of its children is shown.
The colors of the boxes in the topology change when a threshold is passed. The color of the box and the thresholds which are monitored are configurable in the threshold module of Delft-FEWS.
Plot display
...
Plot overview
The plot overview is a panel which shows a thumbnail of each plot which is configured for the selected node. This panel gives an overview of the selected node. When a plot is selected the primary plot is automatically updated, also other plots display which are not locked (see previous chapter) are updated.
...
Forecaster help (aka Document Viewer)
The forecaster aid document panel (or document viewer) displays (user provided) documents linked to nodes in the Topology. The following formats are supported: text-files, images and pdf-files.
The documents are organised in directories and subdirectories, which can be configured in the topology.xml as a forecasterHelperDirectories. Nodes with the same id as the (sub)directory name will display the documents in that (sub)folder. If you make use sub-folders, make sure to also include the main folder as a directory when you list the <forecasterHelperDirectories>. Documents in the folder configured as <allNodesDirectory> will be visible at all nodes.
The documents within these folders can be part of the configuration (e.g. user guide), be placed there by users for easy access, or created by the report module of Delft-FEWS, to make them easily accessible through the Delft-FEWS interface. As long as the file format is supported, the document(s) will be shown at the relevant node in your Topology.
For instance:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<forecasterHelperDirectories>
<directory>d:\Data\ForecasterHelperData\</directory>
<directory>d:\Data\FHD3\</directory>
<directory>$DOCUMENTS_ROOT_FOLDER$</directory>
<directory>$DOCUMENTS_ROOT_FOLDER$/subfolder_1/</directory>
<directory>$DOCUMENTS_ROOT_FOLDER$/subfolder_2</directory>
<allNodesDirectory>$DOCUMENTS_ALWAYSVISIBLE_FOLDER$</allNodesDirectory>
</forecasterHelperDirectories>
|
You can also link directories to multiple nodes, by making use of the <multipleNodesDirectory> element. Any node which id starts with the <nodeIdPrefix> will be linked to that particular documents folder.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<forecasterHelperDirectories>
<directory>$DOCUMENTS_ROOT_FOLDER$</directory>
<allNodesDirectory>$DOCUMENTS_ALWAYSVISIBLE_FOLDER$</allNodesDirectory>
<multipleNodesDirectory nodeIdPrefix="Archive">$DOCUMENTS_ARCHIVE_FOLDER$</multipleNodesDirectory>
<multipleNodesDirectory nodeIdPrefix="Configuration">$DOCUMENTS_CONFIGURATION_FOLDER$</multipleNodesDirectory>
</forecasterHelperDirectories>
<...>
<node id="ArchiveTo_flood_Config" name="Archive Config to local disk">
<workflowId>Export_ToArchive_FloodOps_Config</workflowId>
<filterId>Parameter_FloodOps</filterId>
<toolWindow>document selection panel</toolWindow>
</node> |
If the forecasterHelperDirectories is not configured, the INFORMATION_PANEL_FOLDER property defined in the global.properties will be used instead.
To add the Forecaster help panel and document viewer to the Delft-FEWS explorer, please add the following tasks to Explorer.xml. The <predefinedDisplay> "documents" (or taskClass ForecasterAidDocumentPanel) is the main window, which displays the content of the documents in the explorer. The ForecasterAidSelectionPanel is a so called toolwindow, displaying a list of all available documents (in the folder linked to the node). The content of this Selection panel depends on which node is selected in the Topology, and is updated automatically when a different node is selected.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<explorerTask name="Document Viewer">
<predefinedDisplay>documents</predefinedDisplay>
</explorerTask>
<explorerTask name="Forecaster help">
<taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidSelectionPanel</taskClass>
</explorerTask> |
| Code Block | ||||
|---|---|---|---|---|
| ||||
<explorerTask name="Documents viewer">
<taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidDocumentPanel</taskClass>
</explorerTask>
<explorerTask name="Forecaster help">
<taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidSelectionPanel</taskClass>
</explorerTask> |
...
When one of the files is selected in this panel the content of the selected file is shown in the document viewer. The document viewer is a dockable window in the centre of the Delft-FEWS Operator Client (or SA) GUI.
When a text file is selected, it can also be edited. To facilitate this an edit and save button are displayed above the document when selecting a text file.
Run info
The run info panel shows detail information of the latest run of the workflow of the selected node. If the workflow of the node has not run yet for the current T0 then the panel will show that there is no current run info available
When the workflow has run. The status can either be successful, failed or partly successful. Only when the workflow was successful than the icon of that node will be set to green. The run status will be shown green in the run info box. 
When the run is partly successful the icon of that node will be set to the red exclamation mark, the run status box in the run info panel will be set to yellow. When the run is failed the icon of the node will be set to the red exclamation mark, the run status box will be set to red. 
Forecaster notes
The forecaster notes panel shows the notes other forecaster have created regarding their previous forecasts for the forecast point. Forecasters can also created their own note and publish them. The display is located at the bottom of the Explorer. All fields in this display can be filtered by clicking the cells.
Each line in this display represents an unique message. An envelope icon at the beginning indicates whether message is new (open) or unacknowledged (closed). After clicking the ‘Acknowledged message’ button on the left side of the display, the icon disappears. The content of the message can be enlarged when clicking the ‘Open message’ button. The same icon is available in the status bar of the Delft-FEWS Explorer, to indicate new messages have arrived.
To add a new message, click the ‘Add message’ button. In the pop-up window, the Event time can be entered, the Log Level selected, as well as a User, Event Code and a Log Template. By default the Current system time is entered as well as the user name. The Log template can be used to assist the forecaster with a new message. The message will be synchronized to the server side and from there to the other users.
A message can be made specific to a node in the Forecasts display, by selecting this node before you add a message. If no node is selected, the message is always visible. All messages are also visible in the System Monitor display, in the Forecaster Notes tab. This tab allows querying of the messages.
How to create a forecast with the IFD
Steps in creating a forecast
...
- Start Delft-FEWS
- Selecting the forecast panel
- Reviewing the topology
- Review the list of available state date/times
- Adjust state and/or forecast length
- Starting the forecast process and selecting the workflow for which the forecast should be made
- Reviewing workflow status
- Reviewing graphs (graph display listens to topology selection)
- Reviewing graphs (graph display is independent from topology selection)
- Continue with the forecast process downstream
- Ending the forecast process
Starting Delft-FEWS
After starting FEWS, the Map display will be displayed in the centre and the Forecast Panel-tab at the left will be selected.
This the default layout. The layout after starting Delft-FEWS is however configurable by creating and saving a custom layout by using the option Save layout in the File menu.
...
It is not possible to create modifiers in a synchronization client until the local datastore is fully synched with the central database.
...
While the Operator Client if synchronizing, it is already possible to view scalar and spatial data. When the initial synchronization is finished the icon will change to a pencil icon to indicate that it is possible to create modifiers.
Selecting the forecast panel
The whole process of creating a forecast by using the IFD is managed by the forecast panel, therefore the first step is selecting the Forecast tab at the left of the display. The Forecast tab will give an list, in computational order of the basins of the region. 
Review the list of available state date/times
The forecast panel also shows at the bottom the currently selected (default) warm state. By clicking on the drop-down box all the available warm states are shown. If the forecaster needs to use a different warm state than the default, a new warm state date may be selected from drop down menu titled Warm State Selection. If the default warm state is not correct another warm state can be selected from the drop-down box.
The selected warm state represents the end of the period the warm state is searched in. The warm state search period begins a day before the end of the search period . This is by default.
While running a workflow, the warm state search period is logged in the log panel. An example:
If t0 = 26-06-2021 20:00:00 and Warm state selection = 25-06-2021 20:00:00 the following search period is logged: : "Warm state selection -2 day to -1 day, 1 day"
Please note:
if the warm state search period cannot be rounded to whole days, the period is logged in hours, for example :
If t0 = 26-06-2021 22:00:00 and Warm state selection = 25-06-2021 20:00:00 the following search period is logged: : "Warm state selection -50 hour to -26 hour, 1 day"
Adjust state and/or forecast length
By pressing the Edit Run Options button at the bottom of the forecast dialog the user will have access to alternative ways of selecting states. After pressing the advanced button a dialog will be shown in which the user can select the state, forecast length and a what-if scenario.
After selecting the OK-button the selected task properties will be applied and used in the runs.
Starting the forecast process
To start the interactive forecast process, the user should select a local run node and run the workflow of that node.
Reviewing run status workflow
The icons in the forecast tree indicate the status of the workflow of a node. A refresh-icon indicate that a workflow is running. An hourglass indicates that a workflow is scheduled to run. More details about the icons can be found in 24 Topology
Review graphs (graph display listens to segment selection)
When a run has finished the results of the run should be reviewed. By selecting the plot overview at the right a list of thumbnails will be displayed. For each graph available for the current node a thumbnail will be shown. To display a graph, the forecaster selects a thumbnail and then this graph is displayed in the main plot window. The plot display will show the selected graph. The Plot Overview panel can be undocked. When the display is expanded the plots are automatically resized.
Creating a mod in the time series display
Mods can be created in the mods display or directly in the plot display. To modify a time series directly in a plot, a time series has to be selected. This can be done by selecting a time series in the legend of the plot.
Creating a mod in the mods display
The modifier display can be started by clicking on the wrench-icon at the toolbar or by using the shortcut ctrl+m. The modifier display will show all the mods which are applied in the currently selected segment. By clicking on the create mod-button a new mod can be created. After pressing the create mod-button a list of available mods will be shown. When the mod is created it can be applied by pressing the apply-button. With the run-buttons (rerun, rerun to selected and rerun all to selected) it is possible to rerun the workflows. Pressing the run-buttons will also automatically apply the mod.
Continue with the forecast process downstream
...
Ending the forecast process
...
Dockable windows
Docking and undocking main displays
All windows in the centre section of Delft-FEWS can be undocked. This can easily be done by clicking on the square-box icon beside the x-icon at the tab of each display.
Undocking the windows allows the forecaster to arrange the windows as they like. After clicking on the icon the display will automatically be undocked. Putting the display back in docking mode can be done by clicking on the double square icon at the top of the display. By clicking on the x-icon the display can be closed.
Save display layout and reload on opening with same user
By default Delft-FEWS will start with the map display opened in the centre section of the display and with the map display, data display and the topology display docked in the center section of Delft-FEWS. It is possible to customize the display layout. First step in customizing the display layout is to manually place the display in the desired display layout. In the example below three displays are undocked and the graph-tab and the display are moved to the left section of the display. In the File-menu the user can store this layout by selecting the option store layout. The next time Delft-FEWS is started it will start with the stored layout.
| Info |
|---|
Keep in mind that the layout manager is only responsible for laying out open windows. It will not open a window by itself. Only once the user opens the window, will the stored layout be applied! |
Save display layout and reload default layout
The file-menu also provides an option default layout. By selecting this option the default layout can be reloaded.