...
- 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.
Below an overview of all the combinations which are available for a successful run (local or server).
The status of the workflow of the workflow nodes is indicated by an icon. The icon can indicate the following statuses:
- Running,
- Pending,
- Failed,
- Successful
- Successful but the time zero of the run is different then the time zero of the IFD,
- Successful 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 successful 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.
...
| 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 | grey background | 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. |
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 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). | ||
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 |
...
. |
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 |
...
Forecast length
...
as well. Likewise if a user increases the forecast length |
...
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 |
...
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 |
...
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
...
. | |||
| Red outline | (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. |
All systems normal: Running , successful run
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
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:
...