-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add Useful Energy variables to the template #270
Comments
What about Non-Energy Use and Bunkers? Probably we can leave them out. For the 3 sectors you mention above, the most important question would be whether or not to report in fuel-equivalent or not...? And I guess we do not need the subcomponents, or do we? |
Hmm yes that's the question, we need to have a comprehensive set of reporting. E.g., Agriculture, if reported separately under Final Energy, should it come under "Residential and Commercial" or "Industry"? On 'whether or not to report in fuel-equivalent'; probably yes, but not sure, need to continue discussion with MESSAGE colleagues |
So OK, my proposal for now is this. Maybe @OFR-IIASA and/or @khaeru weigh in if you would think that there is a better way? We follow:
|
As far as I can see you have at least the following:
…wherein that the code list for SECTOR has the items, inter alia:
…and the code list for SUBSECTOR (or whatever ID) has, inter alia:
In terms of coherence, some notes:
I usually find writing out the keys in their entire dimensionality and then constructing the variable names from those leads to less confusion. However, if these are shadowing other variable names that also have the same issues, then I guess there is a choice between coherence and consistency. Either way it's always good to record the full key as an annotation to the variable name. |
As an additional comment, I just noticed that under "sdg.yaml" we also already have a few per-capita variables:
|
Thanks for the comment with your considerations, @khaeru Indeed, I agree that the Final Energy tree is problematic; it should can be more clear in the variable naming (as you noted regarding bunkers) and should still specify I had no interest to open that now, hence my suggestion for consistency (over coherence). However, happy to hear other opinions still, if someone:
Note that, if we want reporting from IAM teams by March 1 (not sure that this is critical, but would be nice), we should make the decision and implement by Monday. |
Per discussion in IAMconsortium#270
As discussed in energy breakout of ScenarioMIP today.
Ping amongst others @gunnar-pik @vruijven
Requirements:
Should include at least:
Probably better full list: directly the same as the Final Energy tree (which is not having the full 'components' list currently): https://github.com/IAMconsortium/common-definitions/blob/main/definitions/variable/energy/final-energy.yaml
The text was updated successfully, but these errors were encountered: