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

Update electricity-grid.yaml #336

Merged
merged 2 commits into from
Jun 18, 2024

Conversation

sandrinecharousset
Copy link
Collaborator

add unit EUR_2020/MW to allow using this variable for extension not only of the line length but also of the line capacity

We could also create a new variable whcih I would have named Network|Electricity[Capital Cost for consistance with the investment costs in other technologies which are named Capcital Cost

add unit EUR_2020/MW to allow using this variable for extension not only of the line length but also of the line capacity
@erikfilias
Copy link
Collaborator

add unit EUR_2020/MW to allow using this variable for extension not only of the line length but also of the line capacity

We could also create a new variable whcih I would have named Network|Electricity[Capital Cost for consistance with the investment costs in other technologies which are named Capcital Cost

Hello, the capital cost variables are in the technology.yaml file. I suggest moving these variables to the electricity-expansion.yaml file and adding this new variable as Capital Cost|Electricity|Network. Finally, I would rename the electricity-expasion.yaml file to invesment.yaml in order to keep the coherence that this file also comprises investment variables related to heat and hydrogen. @sandrinecharousset , @phackstock , How do you see it?

@sandrinecharousset
Copy link
Collaborator Author

@erikfilias sounds good to me
The variable name you propose is more consistent with other variable names
I am not fully satisfied with having only one capital cost for network expansion in capacity and in length , would be better to separate but could not find a good way of doing it
Regarding moving variables from technologies not sure it is a good idea as lots of other models do use these variables and not those in electricity focused yaml files so I would put the new variable maybe in technologies
Regarding electricity-expansion from what I remember this is describing variables that are results of electricity capacity expansion models no? No pb to rename it though but I wouldn’t put the capital cost there
@danielhuppmann ypu may have an opinion there also?
Best

@phackstock
Copy link
Collaborator

Thanks @sandrinecharousset and @erikfilias for the discussion and the inputs.
@sandrinecharousset I very much agree with you that we should split the variable in two to differentiate between line length and capacity.
For naming things I always like to err on the side of verbose but immediately obvious rather than trying to be clever but potentially misleading. Therefore I'd propose something like:

  • Capital Cost|Electricity|Network Capacity
  • Capital Cost|Electricity|Network Length

or something along those lines.

Copy link
Member

@danielhuppmann danielhuppmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the discussion. One point of caution (re the suggestion by @phackstock): the cost are not "per length", but in "capacity per length", so the suggested variable names can also be misleading.

So for simplicity, I suggest to go with the simple suggestion by @sandrinecharousset (but with a minor formatting fix to make sure that the nomenclature package parses the units correctly).

definitions/variable/technology/electricity-grid.yaml Outdated Show resolved Hide resolved
Co-authored-by: Daniel Huppmann <dh@dergelbesalon.at>
@sandrinecharousset
Copy link
Collaborator Author

@phackstock could you merge this so that we can upload datasets for the ws with the good unit?

@phackstock phackstock merged commit 5970bf4 into openENTRANCE:main Jun 18, 2024
2 checks passed
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.

4 participants