Add region and mapping for REMIND 3.0 #210
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Renato-Rodrigues
approved these changes
Jul 29, 2022
|
Permissions to upload to the ECEMF-internal Scenario Explorer instance granted to all REMIND modelers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the discussion from #208 about REMIND 3.0 regions as separate files keeping the existing model-mapping for REMIND 2.1 unchanged (to not alter behavior for existing model submissions to the IIASA database infrastructure).
We will also add guidance on region-naming conventions, see IAMconsortium/nomenclature#142