- a natural system; and
- a system where the flow down the effluent can be controlled by some kind of regulating structure.
A controlled splitter node does not consider what happens to a flow after splitting. In the case of anabranches, there may be multiple order paths and orders may be subject to optimisation.
In a modelled water system where includes a section of the unregulated water network, the splitter node has the ability to respond to orders and allow ordering water from the unregulated water network in Rules Based Ordering.
Modelling systems
To model a system using the controlled splitter node, use the piecewise linear editor or an expression to to describe the relative proportions of water that either continue along the main branch or enter the effluent. Values can be entered either manually or imported from a comma-separated value (.CSV) file using the format shown in Table 1.Table 1. Controlled splitter node (data file format)
| Row | Column (comma-separated) |
|---|
| 1 | 2 | 3 | |
| 1 | Upstream flow (ML/d) | Minimum Effluent Flow (ML/d) | Maximum Effluent Flow (ML/d) |
| 2 | 0 | 0 | 0 |
| 3..n | flow | min | max |
| Info | ||
|---|---|---|
| ||
| Note: A controlled splitter node can only model cases where the regulating structure governs the effluent. More complex cases that include regulating structures on the main channel and/or multiple effluents should be modelled using a Storage node. |
A controlled splitter node is operated to minimise the increase in orders for the main channel, while
ensuringensuring that orders generated for the effluent are still met. Refer to the Source Scientific Reference Guide for details on setting up the node for this. To minimise loss on the main channel, the initial position is that the
regulatorregulator is considered to be fully closed. Next, the regulator is opened sufficiently to meet the orders on the effluent. Additional orders are then generated (if required) to ensure that there is sufficient upstream flow to meet the combined requirements of the main channel and effluent.
There are three possible ordering scenarios in the regulated water network:
- Orders on the main channel will generate sufficient effluent flow to meet orders on the effluent. In this case, no additional orders need to be generated;
- Orders on the effluent are greater than or equal to the minimum effluent flow generated by main channel orders but less than or equal to the maximum effluent flow for the combined main channel and effluent orders. In this case, additional orders need to be generated; or
- Orders on the effluent are greater than the maximum effluent flow for the combined main channel and effluent orders. In this case, the requirements can not be satisfied by adding more water to the system.
In the water system where includes a section of the unregulated water network, the splitter node can be used to order water from the network of the unregulated section in Rules Based Ordering. The configuration details are described in the section of Ordering behaviour in the unregulated network.
| Info | ||
|---|---|---|
| ||
| Note: This functionality will operate in rules-based ordering only. |
- 0 represents the regulator being fully operational so that the minimum effluent relationship will remain the same as what is entered;
- 100 represents the regulator being removed so that the minimum effluent flow relationship will equal the maximum effluent relationship and the controlled splitter no longer has any regulation capabilities; and
- A value between 0% and 100% will alter the minimum effluent flow relationship so that the capability of regulation is reduced. Refer to the Source Scientific Reference Guide for details on setting up the node for this.
Defining splitter behaviour
A simple splitter is one that models the behaviour of a natural system, whereas a controlled splitter node models the behaviour of a system where flow down the effluent can be controlled by some kind of regulating structure. You can To configure the basic behaviour of a splitter using the Splitter Characteristics tab (Feature editor 1). To configure the splitter, first ensure that each branch has been linked to a downstream node. Then Then, define which downstream link represents the effluent. By default, the other link represents the main channel. To do this, refer to the radio buttons near the top of the Splitter Characteristics tab. Then enter a relationship between flow upstream of the node and flow down the effluent. The flow down the main channel is calculated automatically at run time.Feature editor 1. Controlled splitter node (Splitter characteristics)
| Info | ||
|---|---|---|
| ||
| Note: If both downstream links are not connected, a fatal error will occur preventing the scenario from running. |
Figure 1. Controlled splitter node
Ownership of unallocated flows from a controlled splitter can be distributed according to owned amounts or by selecting different proportions to the owned amounts. Refer to Controlled splitte<span style="color: rgb(34,30,31);font-size: small;">r</span>.It is also possible for the user to operate the regulator on the effluent of a controlled splitter independently of the ordering system. The user is able to specify the percentage opening of the regulator via the function editor which will adjust the minimum effluent flow relationship. A function value of 0% represents the regulator being fully operational so that the minimum effluent relationship will remain the same as what is entered by the user.
A function value of 100% represents the regulator being removed so that the minimum effluent flow relationship will equal the maximum effluent relationship and the controlled splitter no longer has any regulation capabilities. A function value between 0% and 100% will alter the minimum effluent flow relationship so that the capability of regulation is reduced. Refer to the Source Scientific Reference Guide for details on setting up the node for this.An example of where this functionality may be used is on an effluent connected to a wetland which has no orders but where the regulator is operated to prevent water flowing down the effluent during high regulated flows during summer, but during winter/spring the regulator is opened to allow more natural wetting behaviour of the wetland.
Ordering behaviour in the unregulated network
For Rules Based Ordering algorithm, the splitter node can be configured to allow ordering water ordered out from unregulated networks that come in via Splitters. The user can tick the checkbox of Treat Splitter as a Regulated Supply Node in Rules Based Ordering to enable this function (Figure 2). However, this function may require mor setup to pass the order to the upstream of an unregulated water network.
Figure 2. Treat Splitter as a Regulated Supply Node in Rules Based Ordering
The explanation is illustrated using a splitter, a confluence upstream of the splitter, and a confluence (last downstream node in unregulated water network) downstream of the splitter.
Without Constraints, confluence downstream of the splitter will not send orders up to the splitter and the splitter also needs Constraints passed from upstream to propagate further Constraints down the network. In the unregulated network, Confluences upstream of the splitter will not produce Constraints because both its branches are unregulated, even the checkbox of Treat Splitter as a Regulated Supply Node in Rules Based Ordering in the splitter is enabled. To solve the problem, one solution is that confluence upstream of the splitter configures its forecast values (such as 10 in Figure3) and then can generate its Constraints, and the splitter has Constraints from the upstream to propagate Constraints for the downstream network. The confluence downstream of the splitter can then send orders up to the splitter ( and further) when the Regulated in confluence‘s Brach Setup is ticked for the link between this conference and its upstream splitter.
Note that in a complex network system, the forecast flow is required only for the last confluence upstream of the splitter to generate above Constraints.
Figure 3. Confluence configuration of forecast values for Constraints
