Open gijsber opened 1 year ago
As discussed with @gijsber: we first look at single inlets to subnetworks. When the allocation implementation is more mature, we can consider multiple inlets. The main question to answer at that point is: If subnetworks are viewed as users in the main water network optimization, how is this modelled when the subnetwork has multiple inlets? This can probably be taken into account in the optimization problem formulation, where the sum of the flows to the multiple inlets together are taken to be the flow to one user.
from @SouthEndMusic
Hi @SouthEndMusic, As long as we only track and add a objective function term (i.e. cost) to the inlet edges, the complexity increase will be limited.
We really will get expensive as soon as all edges in the allocation_subnetwork need to get a cost to enable prioritization over sources, as any small cost factors will make the optimal solution less pronounced
This is the first step in the new plan for allocation development as worked out on 27-5-2024. Steps:
Hi @SouthEndMusic (@visr). I've been think a bit, to limit the complexity and the amount of data to be specified (decisions to be made by the modeller where he doesn't care):
Use Case RWS Linge: Als regionaal watersysteem uit meerdere inlaatpunten kan worden gevoed is er een bepaalde volgordelijkheid. Wanneer bijvoorbeeld 1 inlaatpunt niet volledig kan worden benut vanwege een lagere waterstand in het hoofdwaterysteem, vindt aanvulling plaats.
If a regional watersystem/network can be fed from multiple inlets, a certain sequence of using inlets should be feasible. When the preferred inlet does not have the water available, the request/setpoint of the second inlet should be adjusted.
This was discussed with members from the RTC tools team. They advocate the goal programming approach, i.e. solve for each source separately in order of their preference.