This is some extensive development for BEV component. This is to be merged in #94 and then merged into dev.
The meta-facade incorporates all three bev-techs (v2g, g2v, inflex).
There is an summary node connecting all techs to the electricity bus and one connecting all techs to the demand bus.
This as especially helpful for implementing a mileage constraint (absolute sum of km driven by all bevtechs together in one year). This way only the sum over all timesteps for the flow between "BEV-total" and "pkm-bus" needs to be equal to this amount.
Description
This is some extensive development for BEV component. This is to be merged in #94 and then merged into dev.
The meta-facade incorporates all three bev-techs (v2g, g2v, inflex). There is an summary node connecting all techs to the electricity bus and one connecting all techs to the demand bus. This as especially helpful for implementing a mileage constraint (absolute sum of km driven by all bevtechs together in one year). This way only the sum over all timesteps for the flow between "BEV-total" and "pkm-bus" needs to be equal to this amount.
The following graph shows a small energy system graph with the BEV-fleet meta facade and was created in the small example case in https://github.com/oemof/oemof-tabular/blob/feature/battery-electric-vehicle_meta-facade/tests/mobility.py
Flex share: is the share between the different bev-techs. The constraint already exists see here
What is still missing:
Type of change
Please tick or delete options that are not relevant.
Checklist:
Please tick or delete options that are not relevant.
pre-commit
hooks