-
Notifications
You must be signed in to change notification settings - Fork 49
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
OnSSET variables #320
base: main
Are you sure you want to change the base?
OnSSET variables #320
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @mvittorio-unh for the very comprehensive pull request.
A couple of general points from my side:
- The blank lines between variables are not needed. You can remove them for consistency with the rest of the template.
- The variables that contain
Baseline
orEnd year
are not necessary in my opinion since we report annual data anyway. If I understand your variable definitions correctlyBaseline
andEnd year
would simply be the first and last value in your timeseries. - Out of convention, the unit for money we typically use is
US$2010
(example: https://github.com/IAMconsortium/legacy-definitions/blob/d55beb19b80368d0676261da678ede296b9b615c/definitions/variable/variable.yaml#L524-L532). This would need to be changed for all your units involving money. You are obviously free to adjust the year for the dollar value that your model uses, e.g.US$2020
. - The unit
people
I would suggest either replacing withunti: million
or going fully dimensionless, i.e.unit:
.
Please find some more comments in line below.
at the end of the study. | ||
unit: us$ | ||
|
||
- Population|Connected|Total: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can leave out the total and rename the variable to:
- Population|Connected|Total: | |
- Population|Connected: |
the total is implied by the hierarchy with the |
character.
@mvittorio-unh, I fixed some of the issues and now we're getting close to finishing this PR. Re-defined variablesCurrently you re-defined 8 variables. This is an issue since a variable must only be defined once. These are the 8 in question: ValueError: Collected 8 errors:
1. Duplicate item in variable codelist: Population|Electricity access|Share
2. Duplicate item in variable codelist: Network|Electricity|Expansion Cost
3. Duplicate item in variable codelist: Population|Connected|Grid|Existing
4. Duplicate item in variable codelist: Population|Connected|Grid|New
5. Duplicate item in variable codelist: Population|Connected|PV
6. Duplicate item in variable codelist: Population|Connected|Hybrid|PV
7. Duplicate item in variable codelist: Population|Connected|Hybrid|Wind
8. Duplicate item in variable codelist: Population|Connected|Hydro I could just remove the ones that you added but at least for some of them you use different units to what was already there. Please take a look to make sure that your model outputs conform to the variables and remove your variables accordingly.
|
@mvittorio-unh, thanks for your answers via email. I've addressed all the open points mentioned above. The following variables are used as 'weight' for aggregation but are not defined in the variable codelist:
'Final Energy|Diesel' used for 'Price|Final Energy|Diesel|Low' in: variable/energy/energy-prices.yaml
'Final Energy|Diesel' used for 'Price|Final Energy|Diesel|High' in: variable/energy/energy-prices.yaml
'Primary Energy|Electricity' used for 'Price|Primary Energy|Electricity' in: variable/energy/energy-prices.yaml
'Primary Energy|Electricity' used for 'Price|Primary Energy|Electricity|Expansion' in: variable/energy/energy-prices.yaml these errors mean that as an aggregation weight you've used a variable that does currently not exist.
Option 1. is preferable for me since it does not introduce new variables. If you can't find a good fit though adding new variables is totally fine as well. |
@mvittorio-unh @phackstock removed the variables as per the email, and resolved a merge conflict with the original repo regarding economy.yaml variables (the fork was behind main). Please double-check it's all good there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Region aggregation needs to be skipped for a number of variables.
See reasoning in-line below.
skip-region-aggregation: true | ||
- Capital Cost|Batteries: | ||
description: Expected hybrid mini-grid component costs batteries. | ||
unit: US$2020/kWp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have to set skip-region-aggregation: true
here. Reason being that the default region aggregation simply adds up all the values for across different regions. For a variable with a unit like US$2020/kWp
this would lead to wrong values.
We do offer the possibility of using a weighted average but for now, for simplicity let's skip region aggregation.
The same logic applies for all variables with US$2020/kWp
and US$2020/km
as a unit.
New variables for OnSSET