-
Notifications
You must be signed in to change notification settings - Fork 26
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
CDR under the Emissions|CO2|* : is it clear enough where to report removals from different methods ? #145
Comments
The description on Emissions|CO2|AFOLU, which is "Emissions of fossil carbon dioxide (CO2) from agriculture, forestry and other land use (IPCC category 3)", is a bit confusing since it is unclear whether only "fossil CO2" is considered or not. I would revise as below. |
This was a legacy-issue from NAVIGTE and was fixed in #162. CO2 emission variables clearly refer to all emissions, fossil and non-fossil. |
Thanks for your input @shinichirofujimoriKU; if it is clear that it should fall under AFOLU (I didn't yet manage to find/get clear guidance) then I agree we should add it there. For hamonization, if we would have a constant-based offset (as in AR6), it would make no difference to harmonization (with biochar at 0.25 MtCO2/yr currently; not sure how much soil carbon). But with a multiplicative offset, it could indeed matter. |
This would be my preferred approach. In the RESCUE project, we split out CDR methods from their "parent" category (so, e.g., DACCS is treated separately from Emissions|CO2|Energy), and would suggest we do the same here. The outcome would be that we have separate emissions (removal) trajectories for AFOLU, biochar, EW, etc. This is also important for the ultimate use in CMIP7, where each CDR method will have different land and removal spatial patterns. |
So, for being able to split out each CDR method, I assume/hope we can rely on modelling teams reporting CDR by method here: https://github.com/IAMconsortium/common-definitions/blob/main/definitions/variable/emissions/tag_carbon-removal.yaml But we can update the descriptions for a bit more clarity.
N.B. I now added "Fossil Fuel Fires" explicitly under "Other" (see discussions under #165), which would be a change from last time (but nobody reported the variable before anyway). I tried adding all current options from here, but am not so sure about all, e.g. 'Durable Wood Products'? N.B. EDITED TO CHANGE to "Other Capture and Removal" AND move "fossil fuel fires" to "Other". |
Also, should "Emissions|CO2|Capture and Removal" be changed to "Emissions|CO2|Other Capture and Removal", because there is also lots of CDR in other categories? (just adding #165 as these two issues are very close to each other) |
I concur on both name change to "Emissions|CO2|Other Capture and Removal" as well as most of the suggested definitions in the table above. @gidden @danielhuppmann does this make sense on your end? One minor issue is regarding this one: Emissions|CO2|Industrial Processes | Emissions of carbon dioxide (CO2) from industrial processes (IPCC categories 1A2, 1A5, 2A, B, C, E), net of negative emissions using CCS such as from Cement Production For cement production only the limestone calcination emissions should be reported under Industrial Processes, correct? Any negative emissions from e.g., BECCS for process heat should be reported under Emissions|CO2|Energy. Therefore, I think we should remove the reference to negative emissions from CCS here |
Hi all, thanks for the comments and work on this thread. I'll add specific suggestions in #188. A general/principle thought (which is basically just a summary of the above, but the summary might help). In terms of getting this right in a climate model (simple or ESM, I don't think it matters), what you want to know is where did the carbon start and where did it go. I think the proposal by @jkikstra mostly gets us there, but there is the question of whether we want to refine the nomenclature to really capture this, or whether we leave it mostly as is and just clarify things as best we can and live with some of the imperfect parts (which is also ok, getting this really perfect is hard and we can live with some imperfection). Some specific examples (maybe better discussed in #188)
|
In the first round of ScenarioMIP submissions (for those involved, link), there was some confusion over where negative emissions should be reported under the CO2 variables.
The AIM team had reported some negative emissions under
Emissions|Other
, while other teams tend to report it only* underEmissions|CO2|Energy and Industrial Processes
This is not my expertise, so feel free to point towards clear descriptions if they already exist. I just looked at the template.
If we split up
Emissions|CO2|Energy and Industrial Processes
, looking at 2100 of the "Low Overshoot" scenarios, most modelling teams report most negative emissions underEmissions|CO2|Energy
, with only GCAM reporting net-negative emissions also underEmissions|CO2|Industrial Processes
(in addition to being net-negative inEmissions|CO2|Energy
).There is now also the new variable
Emissions|CO2|Capture and Removal
, which wasn't used by any model in the first round. And alsoEmissions|CO2|Product Use
, where I don't think there would be CDR, but I'm not sure about either the modelling of it or the guidance on reporting CDR (CCS yes, but CDR I don't think so).(Some of) the definitions are now:
I note that there's:
Emissions|CO2|Energy
The complete, up-to-date description of the emissions variables in the current variable template are here:
https://github.com/IAMconsortium/common-definitions/blob/main/definitions/variable/emissions/emissions.yaml
*"Only" here meaning, out of the (presumed additive, and comprehensive) summation set
"Emissions|CO2" = "Emissions|CO2|AFOLU" + "Emissions|CO2|Energy and Industrial Processes" + "Emissions|CO2|Other" + "Emissions|CO2|Waste"
The text was updated successfully, but these errors were encountered: