The Scenario transfer node (STN) handles the joining of two scenarios and conceptually, comprises of two components (as shown in Figure 1). The node links two scenarios and runs them together.
The STN operates in either a connected or disconnected mode. When processing a connected execution, the pitcher passes all components of the pitcher scenario to the catcher, hence linking the two scenarios together. For a disconnected execution (ie. scenarios are run independent of each other), the pitcher acts like a minimum flow requirement node and the catcher models an inflow node.
Figure 1. Scenario Transfer node
Constituents
If constituents are defined in both the pitcher and catcher scenarios, you can choose which constituent in pitcher will match to which constituent in the catcher in the STN feature editor. Choose Connected > Constituent Mapping from the tree and click Add (as shown in Figure.
Figure STN, Constituent mapping
