eeco/utils.py line 405 indexes numpy arrays with Pyomo time-set values (floats)
def const_rule(model, t):
return var[t] == expression1[t] * expression2[t]
This assumes model.t is range(0, T) (the documented convention in how_to_cost.rst). It breaks for any other ordered time set. Solution depends on how versatile this needs to be for pyomo users
Note: Please read this guide detailing how to provide the necessary information for us to reproduce your bug.
Description
A clear description of the bug
Expected Behavior
What did you expect to happen instead?
Reproduction
A minimal example that exhibits the behavior.
Environment
Any additional information about your environment
eeco/utils.py line 405 indexes numpy arrays with Pyomo time-set values (floats)
This assumes model.t is range(0, T) (the documented convention in how_to_cost.rst). It breaks for any other ordered time set. Solution depends on how versatile this needs to be for pyomo users
[ x] I have checked that this issue has not already been reported.
[ x] I have confirmed this bug exists on the latest version of eeco.
Note: Please read this guide detailing how to provide the necessary information for us to reproduce your bug.
Description
A clear description of the bug
Expected Behavior
What did you expect to happen instead?
Reproduction
A minimal example that exhibits the behavior.
# Your code hereEnvironment
Any additional information about your environment