Introduction
...
Confluence node
Refer to the Confluence node/wiki/spaces/SD43/pages/53543657 for configuring ordering at this node. Orders are passed onto the branch depending on the following:
...
Source forecasts the volume of water in storage at the end of the order period so that it can place orders to keep the storage volume within its optimal operating range. Refer to Ordering at storages when configuring ordering at a storage node.
...
Routed links may gain or lose water due to rainfall, evaporation and groundwater (seepage) as flow does not travel from one end to another instantaneously. You can choose which of these lateral fluxes the ordering system takes into account by enabling the relevant checkbox shown in the node’s feature editor (Figure 1). The data for each of the fluxes is taken from its corresponding item in the hierarchical list. For example, if you enable Use Loss/Gain, Source uses the table specified in Loss/Gain. If you choose Groundwater as one of the fluxes, you must specify a time series for it, which can be imported.
The order coming into the routed link is adjusted to cater for the lateral fluxes over each time-step that the ordered flow spends in the link.
Figure 1. Link (Ordering)
| Info | ||
|---|---|---|
| ||
| Note: Changes in link storage volume are not forecasted over the order period, as it does in the storage node. So, where there are significant jumps in the volume ordered, there may be insufficient water stored in the link to achieve the required downstream flow to meet orders. |