Page Comparison

Anchor
ScenarioTransferNode ScenarioTransferNode

The Scenario transfer node (STN) handles the joining of two scenarios and conceptually comprises of two components, the upstream STN and downstream STN (as shown in Figure 1). The node links two scenarios and runs them together. Constituents, orders and ownership are passed between the two scenarios. However, off allocation does not operate over scenarios, instead, the STN operates like an off allocation boundary - similar to the transfer ownership node.

The STN operates in either a connected or disconnected mode:

• When running in connected mode, the upstream STN passes all components of the upstream scenario to the downstream STN, hence linking the two scenarios together; and
• In disconnected mode (ie. scenarios are run independent of each other), the downstream STN acts like a minimum flow requirement node and the upstream STN models an inflow node.

Figure 1. Scenario Transfer node

Configuring an STN

Configuring an STN requires configuring both an upstream STN and a downstream STN. First ensure both upstream and downstream scenarios are in the same project (see Importing Scenarios).

In the upstream scenario:

• Add an STN at an outlet of the model. In a catchment scenario you can change the node model of an existing node at the outlet. In a schematic scenario, you can add an STN and connect it with a straight through link. When connected, the STN node icon will automatically change to become an Upstream STN.
• Open the STN feature editor
• For connected mode, configuring the STN is done at the downstream connector. Therefore, you may leave the configuration blank on the Scenario Transfer menu item.
• In disconnected mode, this node will act as a minimum flow requirement node. If desired, configure the minimum flow requirements by navigating to Scenario Transfer » Disconnected »  Minimum Flow Requirement, see Minimum Flow Requirement node.

In the downstream scenario:

• And an STN at an inlet of the model, it will usually replace an inflow node. When connected, the STN node icon will automatically change to become an Downstream STN.
• Open the STN feature editor.
• Configure for connected mode on the Scenario Transfer menu item:
  
  • Select the upstream scenario as the Scenario Target from the list of all other scenarios in the project
  • Select the name of the downstream connector as the Node Target.
• You can configure mapping of constituents, ownership and orders 
• In disconnected mode, this node will act as an inflow node. Use the STN feature editor to configure the inflow by navigating to Scenario Transfer  see Inflow node.
• In connected mode, this

Constituents

A model will operate even if the constituent processing methodology (lumped or marker) is different for each scenario. For example, consider the pitcher scenario is configured with lumped routing and the catcher scenario with marker routing. Constituents will be passed from the pitcher to the catcher even though the methodology is not the same.

Once constituents are defined in both the pitcher and catcher scenarios, you can map constituents between the two scenarios using the STN feature editor. Choose Connected > Constituent Mapping from the tree and click Add (as shown in Figure 2). 

Figure 2. STN, Constituent mapping

Ownership

Ownership can be set up in linked scenarios using Connected > Ownership in the feature editor (as shown in Figure 3). Configuration of ownership is similar to the Transfer ownership node (when set up as a boundary node). 

Figure 3. STN, Ownership