...
Overview of all the combinations which are available for a successful run
Server runs and local runs
The result of a local run will always overrule the result of a server run. Even when a server run is started later than a local run then the local run will still overrule the server run which means that the results won't be visible in the graphs or the spatial display.
When a forecaster has finished the process of running local runs and possibly creating modifiers the optimize the results of the forecast then a server run is started.
The IFD will then also automatically upload the modifiers which are related to the server run. By doing this the forecaster will make the results of his local runs available for all other forecasters in the FEWS system. But because local runs always overrule server runs the result
of the server run will not be visible in the OC of the forecaster who started the server run until the OC is restarted (a restart will remove the local runs).
This problem is solved in the following way in the IFD. The server run is usually the parent node of the local runs.
In the example above North Slope is the parent node of KUPA2, SGRA2 and CRKLA2. The parent node North Slope has a workflow which consists of 3 sub workflows. These 3 sub workflows are each connected to the child nodes of North Slope,
Because the child nodes of North Slope all have a local run the results of these workflows are visible instead of the results of the workflow of the parent node. However when the workflow of the North Slope is run again then the results of local runs will
automatically be removed when the server run of North Slope finished. When a server run finishes then the local runs of the child nodes will automatically be removed when the IFD notices that a server run for North Slope is finished. Note that this logic is based on the configuration
of the topology and not on the fact the workflow of North Slope consists of sub workflows of its child nodes. In addition only the local runs of child nodes which are directly below North Slope will be removed. If, for example, KLPA2 would also have a child node with a local run then this local run would not be deleted.
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:
...