-
Notifications
You must be signed in to change notification settings - Fork 124
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
The OffsetConverter
is broken in the new implementation
#1067
Comments
Never mind, I think my example is just missing the |
Does that mean this issue is closed, then? |
Kind of yes, the linked pull requests is still valid. Now it is more of a complete rework of the |
So, this was not a real bug, only the API was very inviting to put unreasonable parameters. I will close this, as it can be seen as a duplicate of the "mislieading documentation" issue. |
Describe the bug
With the current formulation, the
OffsetConverter
can produce the outputs at the level of each respectiveoffset
without consuming anything from the input.I am preparing a PR to solve the issue.
To Reproduce
Consider the following example of an electrolyzer producing hydrogen and heat. The electrolyzer follows a fixed hydrogen demand, a slack source is available in case the demand cannot be supplied due to part load restrictions.
The minimum hydrogen production should be at
12
, but due to the offset it is at2.5
.The reason for that is, that the
status_nominal
is multiplied with the output binary variable instead of the input binary variable.The text was updated successfully, but these errors were encountered: