Skip to content
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

Potential conflicts with overlapping region-aggregation instructions #290

Open
danielhuppmann opened this issue Nov 9, 2023 · 0 comments · May be fixed by #315
Open

Potential conflicts with overlapping region-aggregation instructions #290

danielhuppmann opened this issue Nov 9, 2023 · 0 comments · May be fixed by #315
Assignees

Comments

@danielhuppmann
Copy link
Member

It's not clear how the following configuration would work:

- Price|Carbon:
    description: Price of carbon (as reported by the model)
    unit: USD_2010/t CO2
    region-aggregation:
      - Price|Carbon (mean):
          method: mean
- Price|Carbon (mean):
    description: Price of carbon (computed as unweighted mean across regions)
    unit: USD_2010/t CO2

In particular, if a scenario has data for the variable "Price|Carbon (Mean)" at a native-region resolution, which of two instructions (aggregation from "Price|Carbon" or from "Price|Carbon (Mean)") would take priority?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants