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

Cmip7 Emissions Variables List (v0) #188

Merged

Conversation

jkikstra
Copy link
Contributor

@jkikstra jkikstra commented Oct 25, 2024

Implementing the variable list from here [sheet: IAMC variables]

General context documented under #151 (currently bit outdated).

Should address:

Minimum:

Optional / can leave for future versions:

@jkikstra
Copy link
Contributor Author

@danielhuppmann @phackstock apologies for not fully finishing this today. But probably it's already clear where this should go (just the burning variable definitions are left to do for a v0, I think).

So might be ready for a first review?

Feel free to change things, I don't have anything changed locally right now.

Copy link
Member

@danielhuppmann danielhuppmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jkikstra! A few clarifying questions and corrections inline.

The main issue, for me, is that that the formulations "net of" or "not accounting for" is inherently ambiguous (should the activity be not counted or the emissions from that activity?)...

I suggest to revert to shorter variable description, and the add a "notes" attribute with a clear guide on how to compute it, like this example

notes: This variable should be computed as yearly average additions between the previous

definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
@tmkhsgw
Copy link

tmkhsgw commented Oct 30, 2024

Hi, thank you for your great work! I just let you know Land group would like to have the following variables as gross emissions subcategories for AFOLU (as tier3). Units should be Mt CO2/yr. Thank you.

Gross Emissions|CO2|AFOLU|Deforestation:
description: Gross emissions of CO2 from deforestation
Gross Emissions|CO2|AFOLU|Other Land:
description: Gross emissions of CO2 from forest management
Gross Emissions|CO2|AFOLU|Forest Management:
description: Gross emissions of CO2 from other land-use change

definitions/variable/emissions/emissions.yaml Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 2, 2024

Hi, thank you for your great work! I just let you know Land group would like to have the following variables as gross emissions subcategories for AFOLU (as tier3). Units should be Mt CO2/yr. Thank you.

Gross Emissions|CO2|AFOLU|Deforestation: description: Gross emissions of CO2 from deforestation Gross Emissions|CO2|AFOLU|Other Land: description: Gross emissions of CO2 from forest management Gross Emissions|CO2|AFOLU|Forest Management: description: Gross emissions of CO2 from other land-use change

Added (with minor corrections) here: 3dc5809

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

Feedback from the IAMC SWG Data - Emissions group meeting, which will be discussed a bit more.

Major:

  • Should we report Fires separate from AFOLU? Two reasons were brought up by @shinichirofujimoriKU :
    • Fires are not clearly just anthropogenic, but a mix with also some emissions from natural fires.
    • Fires are gridded separately (from agriculture)
      Upon reflection: I think this is probably a good suggestion.
      Note on harmonization (for SCMs and ESMs): peat fires and deforestation & degradation are represented in the GCB, and are also the ones that should be included in AFOLU-like forcing (but not other fires!) following the guidance of Van Marle et al. (2017) "Climate models should not use the CO2 emissions (or nitrogen emissions if the nitrogen cycle is included in the model), as forcing because in general these emissions are not net emissions to the atmosphere, but a return pathway of previously sequestered carbon just as respiration is. The exceptions are CO2 emissions from deforestation and peat fires.".
  • Can we add a signpost for national accounting vs scientific model reporting? (@gidden offered to come with a suggestion)

Minor:

  • Can it be clarified a bit more cleanly how Harvested Wood Products (HWP) should be reported? Maybe have a look at Chapter 12 of Volume 4 of the 2019 refinement of the reporting guidelines and report on a preferred suggested way?

@gidden
Copy link
Member

gidden commented Nov 5, 2024

Can we add a signpost for national accounting vs scientific model reporting? (@gidden offered to come with a suggestion)

Simple suggestion is to use [tags] like [model] or [nghgi]

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

nghgi

Do we need an extra variable?

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

I just noticed that tier level are currently missing from the emission reporting @jkikstra I think it would be useful to have tier level based on this definition from @danielhuppmann Tier-1: Must-have Tier-2: Important for sensible analysis Tier-3: Nice-to-have

P.S. in the presentation that the SWG Data leads were giving now, they put
Tier 1: Basic variables, keep number as small as possible
Tier 2: Standard reporting
Tier 3: Detailed reporting, enabling in-depth analysis

@gidden
Copy link
Member

gidden commented Nov 5, 2024

nghgi

Do we need an extra variable?

The use case here is that teams would be required to report "LULUCF [model]" and can optionally report in addition "LULUCF [nghgi]"

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

On nghgi:
Suggestion coming from discussion between @gidden @jayfuhrman and me:

  1. add extra AFOLU NGHGI variable (and make clear it is NOT a component of totals)
  2. add a note to the model/scientific AFOLU variable that this is model/scientific accounting, and NOT NGHGI-aligned

This way, we don't break post-processing scripts, but still add the extra reporting detail option.

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

for fires: we try discussing between @shinichirofujimoriKU and @gidden and the CMIP7 fires emissions people for an extra discussion

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

@IAMconsortium/common-definitions-emissions ping to check before we merge?

@znichollscr
Copy link
Contributor

  • Should we report Fires separate from AFOLU?

Another reason is that we can maybe harmonise better if we do this. There are biomass burning emissions from GFED, so if we report separately, we can think about whether we want to do something more sophisticated than just harmonising to GCP at the global level

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

  • Should we report Fires separate from AFOLU?

Another reason is that we can maybe harmonise better if we do this. There are biomass burning emissions from GFED, so if we report separately, we can think about whether we want to do something more sophisticated than just harmonising to GCP at the global level

I think in principle this can be done anywhere where it would be reported, but sure.

Just for everyone @IAMconsortium/common-definitions-emissions (e.g. @strefler ) - since @danielhuppmann wants to send out the new variable template today, I would really like to merge this in before.
Then we can update after.
I think that the current state of the template (+comment) is better than not merging this in before.

And so we'll make a new PR directly afterwards then, to continue discussions?

Copy link
Contributor

@znichollscr znichollscr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last thoughts, looks super nice thanks!

definitions/variable/emissions/emissions.yaml Outdated Show resolved Hide resolved
@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

My suggestion for now:
we take what we have (with final polishing fixes), and leave the changes to Fires reporting for a new PR (see #200).

Thumbs up from people for that?

- Emissions|{Level-3 Species}|AFOLU|Land:
description: Emissions of {Level-3 Species} from forestry and other land use
description: Emissions of {Level-3 Species} from forestry and other land use and
land use change. Removals in this variable include agroforestry, re/afforestation,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks to me like all the removal options are missing as subcategories. Not a showstopper though, can add them later, just need to ensure consistency with the carbon management variables

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right, thanks - I'll note it down for future refinement.

@strefler
Copy link
Contributor

strefler commented Nov 5, 2024

great, thanks! Let's merge this and leave other updates for later PRs

Copy link
Member

@danielhuppmann danielhuppmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @jkikstra

Merging as is so that ScenarioMIP-SSP-submission can proceed, but this will require more discussion in several variables and a harmonization of descriptions.

@danielhuppmann danielhuppmann merged commit 1bc8629 into IAMconsortium:main Nov 6, 2024
5 checks passed
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 this pull request may close these issues.

7 participants