Daniel Huppmann
Daniel Huppmann
This should be discussed by the @IAMconsortium/common-definitions-land group.
I guess something like the pydantic error collection would be nice...
I mean, an easy way would be to just write all error messages to a string and then include the string in the error message?
You mean ```yaml - Primary Energy|{Primary Fossil Fuel}|{Source}: description: Primary energy consumption of {Primary Fossil Fuel} unit: EJ/yr ``` and both the Primary-Fossil-Fel and Source tag lists have an attribute...
After some more bilateral discussion with @dc-almeida, I realized that this feature could have some unintended consequences with e.g. the "weight" attribute or mapping to legacy projects.
I think that the current implementation with the tiers satisfies the requirements I had in mind, so fine for me to close this issue.
Good catch, I agree that the renaming should be skipped in such cases.
@dc-almeida can you please look at this issue in the next days?
Agree, mappings and definitions shouldn't be configurable. And using the "root" of repo for initialization would also be better because that would intuitively refer to the `nomenclature.yaml` file (and only...
Sorry for not being sufficiently clear in my proposal - in my understanding, `validate-scenarios` should do the following: 1. check that the scenario data conforms to the codelists (either specified...