-
Notifications
You must be signed in to change notification settings - Fork 21
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 region definitions and mappings for GCAM 7.1 #116
Add region definitions and mappings for GCAM 7.1 #116
Conversation
Hi Daniel, Sorry for the slower response. So after also discussing internally, I think our preference would be to for the moment just go with the names we have been using for a number of years still. The mapping from the internal to the display names is ok if you insist, but it actually would make our lives easier still to keep also those display names to the ones we have internally (only with the GCAM 7.1| prefix, please in any case correct from 7.0 to 7.1). This also how it currently is done for GCAM 6.0 in NGFS... |
Would a python- or R-script that easily converts scenario data from |
Hi Daniel, |
01c46b1
to
b8dbda1
Compare
Bumped to GCAM 7.1 and reverted to the internal GCAM names per your request. When implementing the new regional resolution and new names in GCAM, please make sure that a version-number clearly reflects a specific regional resolution. There is REMIND 3.1 with 12 regions but also with 21 regions, and this creates a lot of headache and scope for error. So please assign a new version number at the same time as adopting a new regional resolution. |
This PR adds the region definitions and mappings for the GCAM 7.0 model.
I renamed a few of the GCAM-region-names displayed in the Scenario Explorer (and used in scenario ensembles) for better readability and for consistency (in naming if not in the countries with REMIND and IMAGE (e.g. Europe_Non_EU: -> Non-EU Europe.
Still to do, either as comments to this PR or as follow-up: