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

Fix/battery in out flow #237

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from
Open

Fix/battery in out flow #237

wants to merge 4 commits into from

Conversation

j-ti
Copy link
Contributor

@j-ti j-ti commented Feb 11, 2021

branched from #113

initially developed for model predictive control update to fix #218

@j-ti j-ti changed the title Fix/batery in out flow Fix/battery in out flow Feb 11, 2021
j-ti added 2 commits March 10, 2021 15:25
- 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
@j-ti j-ti force-pushed the fix/batery_in_out_flow branch from 2a3ad8e to d491c65 Compare March 10, 2021 17:30
@j-brendel j-brendel mentioned this pull request Mar 16, 2021
25 tasks
@j-brendel
Copy link
Contributor

As I understand it, the problem prevails with this fix:
battery_circle_flow

When setting "incorrect" variable costs, the battery charges and is beeing charged in the same timestep

@j-ti
Copy link
Contributor Author

j-ti commented Mar 30, 2021

As I understand it, the problem prevails with this fix:
When setting "incorrect" variable costs, the battery charges and is beeing charged in the same timestep

I constructed it in the way that you have to add a parameter to the model description in order to use it
'constraint_flow_keyword': 'battery_flow',

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:
# TODO: Extract keyword list of constraint flows from model description keywords = ["battery_flow"]

@j-brendel
Copy link
Contributor

j-brendel commented Apr 8, 2021

I made a new commit, where I moved the keyword to the general component.py initialization as I think this could be useful for all components.
Here is an example: I used 2 Batteries, in the left picture the constraint_flow_keyword ist equal for both, in the right they differ. I think this makes the use well visible.
grafik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Battery Component profits from simultaneous in- and outflow
2 participants