rl-institut / oemoflex

A flexible model structure for creating and analysing multi-regional sector-integrated energy systems with oemof featuring many flexibility options.
https://oemoflex.readthedocs.io
GNU Affero General Public License v3.0
4 stars 1 forks source link

Capacity in postprocessed misses information about which bus it is connected to #53

Open jnnr opened 2 years ago

jnnr commented 2 years ago

Capacity is set to a flow in a component, internally. The postprocessed data does not tell to which bus it is connected.

Suggestion: Do not collect capacity. but rather nominal value of the flow.

https://github.com/rl-institut/oemoflex/blob/cc1a1b903e967f7f614e0f52c7e46b6d4763ba1a/oemoflex/model/postprocessing.py#L610-L614

henhuy commented 2 years ago

The postprocessed data does not tell to which bus it is connected.

As far as I can see, postprocessed data holds values from_bus and to_bus in scalar_params: grafik

Where do you need this information in further steps?

jnnr commented 2 years ago

Thanks for your suggestion! The information is necessary when plotting existing capacities with invested capacities. In its current form, the data is inconsistent, e.g.

from, to, var_name, value
B-biomass-gt, None, capacity, 1
B-biomass-gt, B-electricity, invest, 1

which is finally mapped to

name, var_name, var_value
B-biomass-gt, capacity, 1
B-biomass-gt, invest_to_electricity, 1
henhuy commented 2 years ago

This would only work if capacity is forwarded to flow component within facade component. I see three ways:

jnnr commented 2 years ago

Revisited this issue in preparation for 1st release and decided to postpone it. Application-wise, this is important when optimizing brown-field. More generally, it would be good to find a solution, because the problem may arise with other variables as well.