...
The Interactive Forecasting Displays (IFD) consists of several panels, each has a specific role in the process of creating a forecast with the IFD.
Section How to create a forecast with the IFD contains a use case to explain how a forecast can be created with the IFD and its panels.
Forecast panel
The forecast panel (indicated in yellow rectangle above) plays a central role in creating a forecast in the IFD. It shows a tree with all the forecast points for a region and a logical grouping of these forecast points. It can be set up to structure the work process of a forecaster. The forecast panel consists of three main sections: button bar; forecast tree and icons; and task properties panel.
...
The top of the forecast panel shows a button bar. The buttons are explained in more detail in the table below.
| Icon | Action | Visible | Enabled (not greyed out) | Available since | |||||
|---|---|---|---|---|---|---|---|---|---|
|
| Switches to IFD between read-only mode and edit-mode | when <enableAutoRun> is true | always |  | Starts the workflow of the node in IFD-mode (as local run, runs in the Operator Client)). | always | when the node has <localRun> set to true, and | |
| promotes a local IFD run to a server run. | always | when the node has an IFD-run and when <saveLocalRunEnabled> is set to true. | ||||||
| starts a workflow in server mode. | always | when the node has <localRun> set to false, or | ||||||
| starts the secondary workflow of the selected node | when a secondary workflow is configured | when a node with a secondary workflow is selected | 2018.01 | |||||
| If the button is selected the threshold icons will be shown instead of the regular run status icons | by default, unless <hideThresholdsButton> is true | always | 2019.02 | |||||
| If this button is selected a modifier icon will be shown for a topology node if active modifiers are visible in the modifiers panel if that topology node is selected. This means that if you disable for a topology node that modifiers are visible in the modifiers panel that the modifier icon will also not be visible. | by default, unless <hideModifiersButton> is true | always | 2020.01 |
Original button bar (6 buttons)
Optionally, your Delft-FEWS application can be set up to show the original button bar with 6 buttons. The buttons that are different from the new (default) button bar are described in the table below.
| Icon | Action | Visible | Enabled |
|---|---|---|---|
| step to the next leaf node in the topology tree | always | always |
| start a workflow in IFD mode | always | when the node has <localRun> set to true |
| start all the workflows of the children of the group node in IFD-mode | always | when a group node is selected |
| updates the system time to the current time. | always | always |
...
| Status | Icon | Description | Example |
|---|---|---|---|
| Running | Curved arrow | A workflow which is running locally or at the server. | In the example below the workflow of the node ALKA2 is running. |
| Pending |
| A workflow that is pending to run. | In the example above all the nodes below ALKA2 are pending. |
| Failed |
| 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. |
Successful |
| If a workflow was fully successful the node will have a blue for a local run, and green icon for a server run. | The example below shows a successful server run for node North Slope. For the leaf nodes KUPA2, SGRA2 and CRUA2 a successful local run was executed. |
Successful, but T0 is different |
| If the time zero of a node is different than the time zero which was used in the successful run then the icons are grey instead of green and blue and the check marks are now blue and green. | The example below shows a screenshot of the same Delft-FEWS system as shown above but now with a different time zero. |
Successful, but something has changed |
| 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. 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 as well. Likewise if a user increases the forecast length. The results of a node can only be valid if all the previous nodes have run successfully and have a valid status. | In the example below a modifier was made to the node KUPA2. In the example below node TUNA2 has a successful 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. |
Something has changed and previous node is invalid |
| When T0 of the node is different than the T0 of the workflow and one of the following is true
the icon will change into a grey icon with a yellow checkmark (both server runs and local runs). | |
| (Since 2016.01) The IFD status icon can be surrounded by a red outline, to indicate 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. |
...
Grey background: Successful run with different T0; different T0 -and- another item is invalid
Exclamation point: Failed run
Yellow background, things have changed: Modifiers, State selection, Forecast length
Yellow background: Previous node has an invalid status
Red outline: synchronisation issues
Overview of all the combinations which are available for a successful run
...
The majority of these settings can be adjusted in the bottom section of the panel (left screenshot). More options are available in the panel behind the "edit run options" button (right screenshot).
The initial state selection, time zero and forecast length set directly after selecting a node can be determined by the configuration (see 24 Topology for these configuration options).
Modifiers panel
...