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

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

Open
jnnr opened this issue Feb 21, 2022 · 4 comments
Milestone

Comments

@jnnr
Copy link
Collaborator

jnnr commented Feb 21, 2022

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.

capacity = filter_by_var_name(scalar_params, "capacity")
from_to_capacity = filter_by_var_name(scalar_params, "from_to_capacity")
to_from_capacity = filter_by_var_name(scalar_params, "to_from_capacity")

@henhuy
Copy link
Collaborator

henhuy commented Feb 23, 2022

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
Copy link
Collaborator Author

jnnr commented Feb 28, 2022

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
Copy link
Collaborator

henhuy commented Feb 28, 2022

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

  • Either use nominal value as you said above
  • Use inconsistent capacity from (node, None) entry, or
  • forward capacity to flow component in facades component if this is possible and derive entry like investment from there.

@jnnr jnnr added this to the v0.0.1 milestone Sep 13, 2022
@jnnr jnnr modified the milestones: v0.0.1, Someday Sep 26, 2022
@jnnr
Copy link
Collaborator Author

jnnr commented Sep 26, 2022

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.

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

No branches or pull requests

3 participants