-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix/battery in out flow #237
base: dev
Are you sure you want to change the base?
Conversation
- use new constraint feature from oemof 0.4 - make Battery flows nonconvex to be able to use its status of activity - add the limited flow count constraint to the oemof model Resolves simultanious in and out flow of #218
2a3ad8e
to
d491c65
Compare
I constructed it in the way that you have to add a parameter to the model description in order to use it each component needs an individual keyword such as "battery_flow" in order to identify the group of flows of the model which should just have one active flow. Currently, I have a fixed list ['battery_flow'] for test purposes but it there is a todo in run_smooth: |
branched from #113
initially developed for model predictive control update to fix #218