Closed Renato-Rodrigues closed 1 year ago
Thanks for the suggestion @Renato-Rodrigues. In my opinion it should not be too difficult to implement such a feature. With the tags for the definitions we already have something similar. It makes total sense to me to have such a feature as we introduced the ability to have the same region mapping for multiple models. I would ask you to open an issue on https://github.com/iamconsortium/nomenclature when we can see who is going to take a closer look.
Thanks for the suggestion @Renato-Rodrigues. We might implement this feature at some point in the future, but for now, please
closing this PR as suggested and creating an alternative one that can be found in: https://github.com/openENTRANCE/openentrance/pull/208
This PR intends to add support for additional models from the REMIND group that share the same the same region definition.
Question: @danielhuppmann @phackstock How to proceed with the native regions definition? Right now we expressly write the
REMIND 2.1
string in the native regions definition so we keep the uploaded data saved under the model name. However, as all models included in this pull request share the same regional definition, it would be much better if the model name part of the tagREMIND 2.1|<region name>
would be created automatically by the db code, instead of creating multiple almost identical region mapping files, except for the replaced model name tag in the file. Is this feature possible to be implemented?Suggestion: Instead of using
support a key word like for example:
that would be filled automatically at the data processing time with the model name.
Please let me know if this would be possible or if I would need to go with the multiple files solution, with repeated regions definitions.