...
The philosophy: Local runs are used by the operator to interactively run a workflow on the operator client, check the results and potentially optimize a forecast by means of modifiers. Once the operator is satisfied with the forecast results, a server run is started and the results can be shared between operators. Local runs will not store any time series in the central Delft-FEWS database, only time series from server runs are stored in the central database.
...
- Local run results are only available in the local OC and are removed from the database when the application is closed/restarted.
- Server run results (and the modifiers of this run) are stored in the central database and are available from any OC.
- Local run results overrule server run results on the operator client. Even when a server run is started after a local run. This means server run results won't be visible in displays as long as the local run exists in the localDataStore.
- When the local runs are configured as child nodes of the server run, the local runs will be removed upon completion of the server run, and thus the results of the server run will be visible.
- When the local runs are configured as separate nodes, and not as child nodes of the server run, the local runs won't be removed and thus the results of the local runs will be visible.
The fact that local run results overrule server run results mean that the server run results won't be visible in graphs or spatial display, even for the operator who started the server run. As this behavior is not always wanted, this can be changed with the topology chosen in the IFD. Below are two different approaches to this.
...