Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add main network inlet penalty when collecting subnetwork demands #1327

Closed
SouthEndMusic opened this issue Mar 27, 2024 · 2 comments
Closed
Labels
allocation Allocation layer improvement Improvements of the usability of existing functionality

Comments

@SouthEndMusic
Copy link
Collaborator

SouthEndMusic commented Mar 27, 2024

I've noticed that collecting subnetwork demands is not fully deterministic for the subnetwork with ID 7 in the main_network_with_subnetworks model. My first guess as to why this is is that because this subnetwork contains a loop, there are multiple ways to obtain the same objective function value, which differ in how much water they require from the main network inlet. To favor the one with the smallest requirement, a small penalty can be added to the objective function for flows coming from the main network. I'm quite sure that as long as the weight of this penalty is smaller than 1, all demands within the subnetwork will still be properly collected.

This makes the optimization more predictable and explainable.

@SouthEndMusic SouthEndMusic added allocation Allocation layer improvement Improvements of the usability of existing functionality labels Mar 27, 2024
@gijsber
Copy link
Contributor

gijsber commented Mar 27, 2024

sounds good to me

@SouthEndMusic
Copy link
Collaborator Author

Superseded by #1504.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
allocation Allocation layer improvement Improvements of the usability of existing functionality
Projects
Archived in project
Development

No branches or pull requests

2 participants