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

handle situation of pumps defined as "constant power" #99

Open
jjstickel opened this issue Aug 3, 2020 · 1 comment
Open

handle situation of pumps defined as "constant power" #99

jjstickel opened this issue Aug 3, 2020 · 1 comment

Comments

@jjstickel
Copy link
Collaborator

EPANET input files sometimes specifies pumps as constant power. This is nonphysical and will result in constant-valued objective functions (at least with respect to that pump). We can assume the specified power is the power at the BEP, but more information is needed to get flow and head at the BEP. It seems the way out is to run a few flow-feasibility simulations of the network and examine the flows through the pump.

@jjstickel
Copy link
Collaborator Author

The "Kentucky" test networks largely define pumps as constant power (POWER designation in the inp file). Kentucky network 3 (ky3.inp) seems to be the smallest.

tasseff added a commit that referenced this issue Jan 14, 2021
@tasseff tasseff added this to the Functionality for Solving Maximum Demand Delivery Problems milestone Sep 3, 2021
tasseff added a commit that referenced this issue Sep 3, 2021
@tasseff tasseff removed this from the Functionality for Solving Maximum Demand Delivery Problems milestone Dec 5, 2022
hskkanth pushed a commit to hskkanth/WaterModels.jl that referenced this issue Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants