...

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).

Local and server runs

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. 

This is implemented as follows:

• Local run results are only available in the local OC and are removed from the database when the application is closed.
• 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.

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.

Local and server runs - parent and child nodes

Within the IFD, local run results behave differently based on the topology structure that is chosen. We explain what changes with an example. Typically the server run is the parent node of the local runs, see screenshot below. 

• North Slope is the parent node of KUPA2, SGRA2 and CRKLA2.
• North Slope has a workflow which consists of 3 sub workflows, which are each connected to the child nodes of North Slope.
• The child nodes of North Slope have local run results (blue box), which will be visible instead of the results of the workflow of the parent node. 
• If next the North Slope workflow is run (i.e. a server run), the local run results in the child nodes of North Slope will be removed.  
  Because the local runs are deleted the icon for Local Node A and B will change from Image Removed to Image Removed.
• Note: Only the results in direct child nodes of a parent node are removed. This does not impact local run results elsewhere in the IFD.
  If in this example KUPA2 would also have a child node with a local run (i.e. a nested child node) then this local run would not be deleted. 

Note: This logic is based on the configuration of the Topology (i.e. parent nodes and child nodes) and not the content of the workflows linked to these nodes (i.e. workflows and sub-workflows).

Image Removed                               Image Removed

On the right is a schematic diagrams of a topology with nested nodes, which we will use to describe a different use case.

• First the workflows for Local Node A and B are run (blue squares in diagram).
• Next Server Node C and Server Node D are run (at the server). Because these nodes don’t have any child nodes, no local runs will be deleted after a successful server run.
• Lastly, Server node A is run (at the server). When the run finished the local runs of 
  • Local Node A run will be deleted. 
  • Local Node B run will not be deleted because it is not a direct child node of Server Node A.

Local and server runs - all child nodes

If you want to be able to see local and server runs at the same time, you can configure both the local and server run nodes as child nodes (without a parent node). In the screenshot below, the nodes that start with Save... are server runs, the other nodes are local runs. If you run a server run, the local run results are not removed, since they are not generated in a child node of the server run (as in the example above).

Note: for this to work well, it is necessary for the timeseries produced by all nodes to have unique moduleInstanceId / ensembleId combinations. For example, if you process rainfall for both the local run (e.g. Select Kolan rainfall) and the server run (e.g. Save Kolan), the resulting time series should be different. If they get the same moduleInstanceId, you need to configure different ensembleIds for both (e.g. "ifd" for the local run and "official" for the server run). If you don't do this, the workflows will still run, but the processed rainfall from the first run will be overwritten by the processed rainfall from the second run (since there is nothing different to be able to differentiate the two). 
This is true in general, if you produce timeseries anywhere in Delft-FEWS which result in the same timeseriesSet definition (i.e. moduleInstanceId and ensembleId), the latter run will overwrite the timeseries from a previous run, also if the modules are run as part of different workflows etc. 

Image Removed

Modifiers panel

The modifiers panel allows you to create, modify or delete modifiers. It shows modifiers linked to the the node selected in the IFD, or modifiers for the grid plot for which spatial modifier mode has been activated (since 2019.02). 

The top part lists modifiers created for the currently selected node (modifier table). It allows you to (in)activate, delete and copy modifiers (see below). Modifiers for a local run have a salmon background color. Modifiers for server runs have a green background and are saved to the server. 
The bottom part shows the details of a selected modifier (modifier editor).
The splitter between the overview and the editor is stored in user_settings.ini.  When the application is reopened, the splitter appears at the previously set position.

• Activate - Use check box to (de-)activate a modifier
• Delete - Use cross button to delete a modifier.
  • If you have made a local change to a saved modifier, only the local change will be deleted and the background will change from salmon to green. If you delete it again, the server modifier will be deleted as well.
  • (Note, in a SA the behavior is different. Here a single delete action deletes the entire modifier.)
  • The Run Info panel shows both the server and local modifiers, so you can compare them directly.
    This panel needs to be enabled, see How to define an ExplorerTask - what are the possible taskClass options?
• Copy - Use copy button to copy the modifier.

Image Removed

Spatial display and modifiers

There are spatial modifier types to modify grid time series (since 2019.02), which are created through the spatial display instead of the modifiers panel. See User Guide > 05 Spatial Display > Creating Spatial Modifiers.

Topology panel

The topology panel shows the topology of nodes linked to a selected node, highlighting the box of the selected node. 

• The panel shows the topology, whether you select the parent node or a child node.
• Reversely, you can select a node in the Forecast panel by clicking on a box in the Topology panel. 
• The connections are based on the Topology (nodes and previousNodeIds) and is not influenced by the workflows linked to those nodes. 
• The colors of the boxes correspond to threshold crossings, as configured in 09 Thresholds.

This panel needs to be enabled, see How to define an ExplorerTask - what are the possible taskClass options?

Image Removed

DisplayGroup

...

Modifiers panel

The modifiers panel allows you to create, modify or delete modifiers. It shows modifiers linked to the the node selected in the IFD, or modifiers for the grid plot for which spatial modifier mode has been activated (since 2019.02). 

The top part lists modifiers created for the currently selected node (modifier table). It allows you to (in)activate, delete and copy modifiers (see below). Modifiers for a local run have a salmon background color. Modifiers for server runs have a green background and are saved to the server. 
The bottom part shows the details of a selected modifier (modifier editor).
The splitter between the overview and the editor is stored in user_settings.ini.  When the application is reopened, the splitter appears at the previously set position.

• Activate - Use check box to (de-)activate a modifier
• Delete - Use cross button to delete a modifier.
  • If you have made a local change to a saved modifier, only the local change will be deleted and the background will change from salmon to green. If you delete it again, the server modifier will be deleted as well.
  • (Note, in a SA the behavior is different. Here a single delete action deletes the entire modifier.)
  • The Run Info panel shows both the server and local modifiers, so you can compare them directly.
    This panel needs to be enabled, see How to define an ExplorerTask - what are the possible taskClass options?
• Copy - Use copy button to copy the modifier.

Image Added

Spatial display and modifiers

There are spatial modifier types to modify grid time series (since 2019.02), which are created through the spatial display instead of the modifiers panel. See User Guide > 05 Spatial Display > Creating Spatial Modifiers.

Topology panel

The topology panel shows the topology of nodes linked to a selected node, highlighting the box of the selected node. 

• The panel shows the topology, whether you select the parent node or a child node.
• Reversely, you can select a node in the Forecast panel by clicking on a box in the Topology panel. 
• The connections are based on the Topology (nodes and previousNodeIds) and is not influenced by the workflows linked to those nodes. 
• The colors of the boxes correspond to threshold crossings, as configured in 09 Thresholds.

This panel needs to be enabled, see How to define an ExplorerTask - what are the possible taskClass options?

Image Added

DisplayGroup

A topology node can be connected to a Display Group. If this is the case, the first plot in this displayGroup will be shown automatically when the corresponding topology node is selected. If you switch between nodes with linked displayGroups Delft-FEWS will instead show a plot with the same location and parameter if available.

Image Added

Plot display

Delft-FEWS always at least one plot display, the so-called primary plot display, which doesn't have lock in the toolbar. 
When an additional plot display is opened, it will have a lock icon in the toolbar (see yellow indication below). By default the plot is locked, which means it is locked to that time series shown. When you select another node, the plot will not change accordingly. The timeseries shown will however update if new data for those series comes available. 

Image Added

Plot overview

The plot overview is a panel which shows a thumbnail of each plot of the displayGroup linked to the selected node. If you select a thumbnail, the primary plot display is automatically updated, as are other unlocked plots display (see above).
The 4 buttons at the top of Plot Overview can be used to select the first, the previous, the next plot and the last plot respectively.

Image Added

Forecaster aid selection panel and Document Viewer

The forecaster aid selection panel is a tool window that provides a list documents that can be viewed in the Document Viewer, which is a main panel (see screenshots below). 
The content of the selection panel depends on which node is selected in the Topology, and is updated automatically when a different node is selected.

• The documents are organized in (sub)directories, configured in the topology.xml as a <forecasterHelperDirectories>, see section below. 
  • 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 following formats are supported:
  • text-files,
  • images and
  • pdf-files. 
• These can be documents that are
  • part of the configuration (e.g. user guide),
  • placed there by users for easy access, or
  • created by the report module of Delft-FEWS
  • a list of reports based on an explorer location document attribute (since 2017.02)

ForecasterHelperDirectories examples

We first give an example of forecasterHelperDirectories configured in Topology.xml using <directory>.
Next we show how to link directories to multiple nodes with <multipleNodesDirectory>. Any node which id starts with the <nodeIdPrefix> will be linked to that particular documents folder.

Note: If <forecasterHelperDirectories> is not configured, the INFORMATION_PANEL_FOLDER property defined in the global.properties will be used instead.

<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>

<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>

Configuration of document panels

The Forecaster aid selection panel and document viewer need to be configured as explorerTasks in Explorer.xml. 

<explorerTask name="Document Viewer">                                   
	<predefinedDisplay>documents</predefinedDisplay>                                   
</explorerTask>

<explorerTask name="Forecaster help">                                   
	<taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidSelectionPanel</taskClass>                                   
</explorerTask> 

<explorerTask name="Documents viewer">
	<taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidDocumentPanel</taskClass>
</explorerTask> 

Example of document panels

Below an example of the tool window forecaster help (in this case renamed to: "HowTo Overview"). In this example the forecaster has 15 documents available for information. If multiple directories are configured this window will show all available files for the node from the different predefined directories together.

Image Added

When one of the files is selected in this panel the content of the selected file is shown in the document viewer display. The document viewer is a dockable window in the centre of the Delft-FEWS Operator Client (or SA) GUI.

Image Added

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.

Image Added

Run info

The run info panel shows detail information of the latest run of the workflow of the selected node. 
This panel needs to be enabled, see How to define an ExplorerTask - what are the possible taskClass options?

• (1st screenshot) 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.
• (2nd screenshot) 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.
• (3rd screenshot) 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.
  Image Added Image Added Image Added

Forecaster notes

The forecaster notes panel is a toolwindow that shows notes you or other forecaster have created regarding their previous forecasts for the forecast point.

• All fields in this display can be filtered by clicking the cells.
• Each line in this display represents an unique message.
• Messages with level ERROR and FATAL have an envelope icon to indicate if message is new (open) or unacknowledged (closed).
  • ‘Acknowledged message’ button: removes the envelope icon.
  • Messages with level WARN and INFO do not have this functionality.
• ‘Open message’ button: opens the content of the message. 

• ‘Add message’ button: create a new message in a pop-up window, where you can enter or select the relevant information.
  

  • Event time (default is current system time)

  • Log Level

  • User (default is current user)

  • Event Code and

  • Log Template (can be used to assist the forecaster when writing a new message).

• 'Add': The new message will be synchronized to the server side and from there to the other users.

• A message can be linked to a node in the Forecasts display, by selecting this node before you add the message. 
  If no node is selected, the message is always visible.

• All messages are also visible in the the Forecaster Notes tab of the System Monitor display. This tab allows querying of the messages.

• An envelope icon in the status bar of the Explorer indicates a new message has arrived.

Image Added Image Added

Configuration of Forecaster Notes

Plot display

Delft-FEWS always at least one plot display, the so-called primary plot display, which doesn't have lock in the toolbar. 
When an additional plot display is opened, it will have a lock icon in the toolbar (see yellow indication below). By default the plot is locked, which means it is locked to that time series shown. When you select another node, the plot will not change accordingly. The timeseries shown will however update if new data for those series comes available. 

Image Removed

Plot overview

The plot overview is a panel which shows a thumbnail of each plot of the displayGroup linked to the selected node. If you select a thumbnail, the primary plot display is automatically updated, as are other unlocked plots display (see above).
The 4 buttons at the top of Plot Overview can be used to select the first, the previous, the next plot and the last plot respectively.

Image Removed

Forecaster aid selection panel and Document Viewer

The forecaster aid selection panel is a tool window that provides a list documents that can be viewed in the Document Viewer, which is a main panel (see screenshots below). 
The content of the selection panel depends on which node is selected in the Topology, and is updated automatically when a different node is selected.

• The documents are organized in (sub)directories, configured in the topology.xml as a <forecasterHelperDirectories>, see section below. 
  • 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 following formats are supported:
  • text-files,
  • images and
  • pdf-files. 
• These can be documents that are
  • part of the configuration (e.g. user guide),
  • placed there by users for easy access, or
  • created by the report module of Delft-FEWS
  • a list of reports based on an explorer location document attribute (since 2017.02)

ForecasterHelperDirectories examples

We first give an example of forecasterHelperDirectories configured in Topology.xml using <directory>.
Next we show how to link directories to multiple nodes with <multipleNodesDirectory>. Any node which id starts with the <nodeIdPrefix> will be linked to that particular documents folder.

Note: If <forecasterHelperDirectories> is not configured, the INFORMATION_PANEL_FOLDER property defined in the global.properties will be used instead.

<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>

<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>

Configuration of document panels

...

Code Block
language xml title Explorer.xml (since 2013.02) linenumbers true collapse true
<explorerTask name="Document Viewer"> <predefinedDisplay>documents</predefinedDisplay> </explorerTask> <explorerTask name="ForecasterForecast helpNotes">     <displayConfigFileName>ForecasterNotesDisplay</displayConfigFileName>     <toolbarTask>false</toolbarTask>     <menubarTask>false</menubarTask>     <toolWindow>true</toolWindow>     <taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidSelectionPanel</taskClass> </explorerTask>

Code Block
language xml title Explorer.xml (before 2013.02)
<explorerTask name="Documents viewer"> <taskClass>nl.wldelft.fews.gui.plugin.information.ForecasterAidDocumentPanel</taskClass> </explorerTask>

Example of document panels

...

When one of the files is selected in this panel the content of the selected file is shown in the document viewer display. The document viewer is a dockable window in the centre of the Delft-FEWS Operator Client (or SA) GUI.

Image Removed

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.

Image Removed

Run info

The run info panel shows detail information of the latest run of the workflow of the selected node. 
This panel needs to be enabled, see How to define an ExplorerTask - what are the possible taskClass options?

• (1st screenshot) 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.
• (2nd screenshot) 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.
• (3rd screenshot) 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.
  Image Removed Image Removed Image Removed

Forecaster notes

The forecaster notes panel is a toolwindow that shows notes you or other forecaster have created regarding their previous forecasts for the forecast point.

• All fields in this display can be filtered by clicking the cells.
• Each line in this display represents an unique message.
• Messages with level ERROR and FATAL have an envelope icon to indicate if message is new (open) or unacknowledged (closed).
  • ‘Acknowledged message’ button: removes the envelope icon.
  • Messages with level WARN and INFO do not have this functionality.
• ‘Open message’ button: opens the content of the message. 

• ‘Add message’ button: create a new message in a pop-up window, where you can enter or select the relevant information.
  

  • Event time (default is current system time)

  • Log Level

  • User (default is current user)

  • Event Code and

  • Log Template (can be used to assist the forecaster when writing a new message).

• 'Add': The new message will be synchronized to the server side and from there to the other users.

• A message can be linked to a node in the Forecasts display, by selecting this node before you add the message. 
  If no node is selected, the message is always visible.

• All messages are also visible in the the Forecaster Notes tab of the System Monitor display. This tab allows querying of the messages.

• An envelope icon in the status bar of the Explorer indicates a new message has arrived.

Image Removed Image Removed

Configuration of Forecaster Notes

<explorerTask name="Forecast Notes">
      <displayConfigFileName>ForecasterNotesDisplay</displayConfigFileName>
      <toolbarTask>false</toolbarTask>
      <menubarTask>false</menubarTask>
      <toolWindow>true</toolWindow>
      <loadAtStartup>true</loadAtStartup>
</explorerTask>

...

...

<loadAtStartup>true</loadAtStartup>
</explorerTask>

<forecasterNotesDisplay xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/forecasterNotesDisplay.xsd">
	<title>Forecaster Notes</title>
	<msgTemplate id="Spoke to .... at .... about...">
		<message>Spoke to .... at .... about....</message>
	</msgTemplate>
	<eventCode id="Event.info"/>
	<eventCode id="Model.info"/>
	<eventCode id="Forecast.info"/>
	<eventCode id="System.maintenance"/>
</forecasterNotesDisplay>

Local and server runs

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. 

This is implemented as follows:

• Local run results are only available in the local OC and are removed from the database when the application is closed.
• 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.

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.

Local and server runs - parent and child nodes

Within the IFD, local run results behave differently based on the topology structure that is chosen. We explain what changes with an example. Typically the server run is the parent node of the local runs, see screenshot below. 

• North Slope is the parent node of KUPA2, SGRA2 and CRKLA2.
• North Slope has a workflow which consists of 3 sub workflows, which are each connected to the child nodes of North Slope.
• The child nodes of North Slope have local run results (blue box), which will be visible instead of the results of the workflow of the parent node. 
• If next the North Slope workflow is run (i.e. a server run), the local run results in the child nodes of North Slope will be removed.  
  Because the local runs are deleted the icon for Local Node A and B will change from Image Added to Image Added.
• Note: Only the results in direct child nodes of a parent node are removed. This does not impact local run results elsewhere in the IFD.
  If in this example KUPA2 would also have a child node with a local run (i.e. a nested child node) then this local run would not be deleted. 

Note: This logic is based on the configuration of the Topology (i.e. parent nodes and child nodes) and not the content of the workflows linked to these nodes (i.e. workflows and sub-workflows).

Image Added                               Image Added

On the right is a schematic diagrams of a topology with nested nodes, which we will use to describe a different use case.

• First the workflows for Local Node A and B are run (blue squares in diagram).
• Next Server Node C and Server Node D are run (at the server). Because these nodes don’t have any child nodes, no local runs will be deleted after a successful server run.
• Lastly, Server node A is run (at the server). When the run finished the local runs of 
  • Local Node A run will be deleted. 
  • Local Node B run will not be deleted because it is not a direct child node of Server Node A.

Local and server runs - all child nodes

If you want to be able to see local and server runs at the same time, you can configure both the local and server run nodes as child nodes (without a parent node). In the screenshot below, the nodes that start with Save... are server runs, the other nodes are local runs. If you run a server run, the local run results are not removed, since they are not generated in a child node of the server run (as in the example above).

Note: for this to work well, it is necessary for the timeseries produced by all nodes to have unique moduleInstanceId / ensembleId combinations. For example, if you process rainfall for both the local run (e.g. Select Kolan rainfall) and the server run (e.g. Save Kolan), the resulting time series should be different. If they get the same moduleInstanceId, you need to configure different ensembleIds for both (e.g. "ifd" for the local run and "official" for the server run). If you don't do this, the workflows will still run, but the processed rainfall from the first run will be overwritten by the processed rainfall from the second run (since there is nothing different to be able to differentiate the two). 
This is true in general, if you produce timeseries anywhere in Delft-FEWS which result in the same timeseriesSet definition (i.e. moduleInstanceId and ensembleId), the latter run will overwrite the timeseries from a previous run, also if the modules are run as part of different workflows etc. 

Image Added

How to create a forecast with the IFD

...