Ordering priorities allow users in Source to specify how shortfalls are prioritised between different demands in Source. Previously, Source tried to shortfall all demands equally within the model, this functionality provides a solution to address situations encountered in water resource models such as the following:
...
The current behaviour for sharing shortfalls in Source is maintained as the default behaviour (distribute shortfalls equally). This is reflected as all nodes receiving a priority of 1 initially in the priority table.
Priorities are assigned in levels of 0 to n, with the lower n level having the highest priority
...
| Anchor | ||||
|---|---|---|---|---|
|
Scenario | Allow Order | Extract Water | Notes |
1 | True | True | Standard case |
2 | True | False | Just restrict the extraction in the flow phase |
3 | False | True | Water will be extracted independently of the priorities |
4 | False | False | Nothing occurs |
...
Two options at a storage node that have an impact on the prioritisation of orders
Pass Orders Through – simply sum the volumes at each priority level across all outlets and divide by total volume being passed up all outlets to get proportions, assume evap/seepage does not effect storage ratios
Re-regulating the orders
...
...
sumOutletOrder = Sum the total order from all
...
outlets
OutletOrders(p) += dsOrder(p) * OutletOrder
nPriority(p) =
...
OutletOrders(p)/ sumOutletOrder
...
Re-regulating the orders
- Downstream orders
- Storage losses
- Different upstream min order time
- Operational targets being met
User needs to associate a priority level for supply priority (downstream priority) and operational priority
If (usOrder(min) <= dsOrder(min) )THEN
...