You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently allocation is using a derived network that only takes in features that matter for allocation. That means we need to map back and forth. The allocation code will be more maintainable if we stick to a 1:1 mapping. This will also help with implementing #714.
For Terminals we can add a 0 flow constraint instead of pruning the branch.
The text was updated successfully, but these errors were encountered:
Fixes#1388.
This also fixes a bug I found: In allocation the `max_flow_rate` of a
node connecting the main network to a subnetwork was not taken into
account
Currently allocation is using a derived network that only takes in features that matter for allocation. That means we need to map back and forth. The allocation code will be more maintainable if we stick to a 1:1 mapping. This will also help with implementing #714.
For Terminals we can add a 0 flow constraint instead of pruning the branch.
The text was updated successfully, but these errors were encountered: