Closed FLomb closed 1 week ago
Yes, pyomo considers .inf
as there being no upper bound. We might pass it .inf but it stores it as None. If there was a problem with parsing, the parser would complain. This shouldn't be an issue when solving the model as it's pyomo's decision to store it as None and it handles sending it to the solver just fine (in your case, it just wouldn't send it at all - it's a constraint that isn't constraining anything).
I see, ok, then maybe we can consider the issue closed?
What happened?
If using
.inf
in the math syntax in yaml files (e.g.,- expression: sum(cost, over=[nodes, techs]) <= .inf
), this is apparently not correctly parsed. It appears asNone
in the backend.Which operating systems have you used?
Version
v0.7.0dev3
Relevant log output
No response