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

Handling of Emissions|CO2|Other and Emissions|CO2|Waste - Docs and Warning? #61

Open
2 tasks
jkikstra opened this issue Sep 26, 2024 · 3 comments
Open
2 tasks

Comments

@jkikstra
Copy link
Collaborator

The SCMs are only given two variables as input: Emissions|CO2|AFOLU and Emissions|CO2|Energy and Industrial Processes (after harmonization & infilling).

If Emissions|CO2|Other and Emissions|CO2|Waste are reported as non-zero, they will be added to Emissions|CO2|Energy and Industrial Processes.

To make this more clear, we should do two things:

  • update the docs for Expected Input
  • add a check that gives a warning (or error) if input data might have double-reported for instance Carbon Dioxide Removal (negative emissions), meaning that Emissions|CO2 != Emissions|CO2|AFOLU + Emissions|CO2|Energy and Industrial Processes + Emissions|CO2|Other + Emissions|CO2|Waste
@chrisroadmap
Copy link

This is thorny - it depends on what the source of the waste emissions are. If (some fraction of) the waste emissions are originally from biogenic sources then they shouldn't be counted as contributing to a net input of CO2 into the atmosphere. I guess this only applies to one or two IAMs?

@chrisroadmap
Copy link

chrisroadmap commented Sep 26, 2024

then again if we're talking <2 % of total CO2, then it is a similar or smaller magnitude to the cement carbonation sink, which I'm not sure is handled at all in the reporting of CO2 emissions

@jkikstra
Copy link
Collaborator Author

Let's wait with this until the ScenarioMIP guidance is complete.

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

No branches or pull requests

2 participants