Daniel Huppmann

A current workaround is to open the underlying database and, in table `RUN`, set the `status` column in the row for the `id` to `1`.

All other imports on my machine work fine. And it seems that our test suite including an integration test with wbdata works fine on Mac OS and python 3.12, see...

Closing as no further comment, please reopen if still relevant

One use case encountered in openENTRANCE and several IAM projects is to convert combined units, like `2010-USD/kW` (for investment cost) to `2020-EUR/kW` or `EJ/2010-USD` (for energy per GDP) to `GWh/2020-EUR`....

Note that you edited a file that has as its first line "# DO NOT ALTER THIS FILE MANUALLY!"...

Thanks for raising this issue, happy to contribute to the implementation! For clarification of purposes of our infrastructure and tools: - a **common data** format established by the IAMC and...

Nice idea, and we already do this for codelists... https://github.com/IAMconsortium/nomenclature/blob/48dc9e1c487deac23ff1c074c6677b61104887a2/nomenclature/codelist.py#L57 Question is whether that should be used on columns that are not explicitly checked as part of `DataStructureDefinition.validate()`.

Agree, @phackstock... The current official list of NUTS regions is available at https://ec.europa.eu/eurostat/web/nuts/overview In the **openENTRANCE** project, I developed a prototype here: https://github.com/openENTRANCE/openentrance/blob/main/definitions/region/nuts3.yaml, where three files (one for each NUTS-level)...

This looks great, but I'm wondering about two issues. 1. Wouldn't be more intuitive to have the filters as an attribute of the repository, instead of repeating the repository-attribute many...

I guess we will quickly run into a use case like "give me primary energy, final energy, CO2 emissions, GDP, ..." from an upstream-repo, so repeating the "name" attribute many...