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

Fires Emissions: changing hierarchy #200

Open
wants to merge 42 commits into
base: main
Choose a base branch
from

Conversation

jkikstra
Copy link
Contributor

@jkikstra jkikstra commented Nov 5, 2024

Note: do not merge before #188 .

In commit 01d95a5 there is a first attempt to try to accommodate the suggestion of @shinichirofujimoriKU, as described here: #188 (comment)

ToDo:

  • check consisency of "component" and actual "variable" for Level 1/2/3 species throughout the file

jkikstra and others added 30 commits October 25, 2024 16:24
Clarify for use in climate models
Burning variable descriptions coming from GFED variable mapping.

Land variables coming from https://www.ipcc-nggip.iges.or.jp/public/2019rf/pdf/1_Volume1/19R_V1_Ch08_Reporting_Guidance.pdf
@jkikstra jkikstra mentioned this pull request Nov 5, 2024
23 tasks
@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 5, 2024

Two thoughts:

  1. (major) I'm not sure I'm convinced about placing all GFED-based burning outside of AFOLU, mainly because to me AWB clearly seems related to Agriculture
  2. (minor) I did not touch fossil fuel fires, to keep it aligned with EDGAR&CEDS reporting under "Other", and because no IAM models this AFAIK. (but of course, in principle, this is also Fire/Burning)

@znichollscr
Copy link
Contributor

  1. (major) I'm not sure I'm convinced about placing all GFED-based burning outside of AFOLU, mainly because to me AWB clearly seems related to Agriculture

I agree with this, although I think it's a general problem of the tree approach. We have a category that could have AFOLU or burning as a higher-level. In a tree, there's no easy way to have two parent nodes, so we're just going to have to live with whatever and maybe provide a mapping between the two if we find ourselves doing this conversion a lot.

@shinichirofujimoriKU
Copy link

I am not sure it has been resolved already, but I think AWB is purely anthropogenic which would be OK to be reported under AFOLU. My main point is better to keep the variables which can include non-anthropogenic emissions separate.
At the SWG meeting, I mentioned the downscaling process as one of the reasons to separate fire related emissions, but probably distinguishing treatment of anthropogenic (AWB) or not (other fire) would be useful.
downscaling and MAGICC run can be done regardless of the decision how subcategory is defined.

@jkikstra
Copy link
Contributor Author

jkikstra commented Nov 6, 2024

I am not sure it has been resolved already, but I think AWB is purely anthropogenic which would be OK to be reported under AFOLU. My main point is better to keep the variables which can include non-anthropogenic emissions separate.

So, let me try to hone that suggestion, and check your response to the split now in bf9270b

At the SWG meeting, ...I mentioned the downscaling process as one of the reasons to separate fire related emissions, but probably distinguishing treatment of anthropogenic (AWB) or not (other fire) would be useful. downscaling and MAGICC run can be done regardless of the decision how subcategory is defined.

Agreed. Same holds for (not only for downscaling and MAGICC, but also for) spatial gridding.
I would think we do separate grids for Peat Fires, Forest Fires, and Grassland Fires either way (no matter where we place it).

@danielhuppmann
Copy link
Member

Please rebase this branch to main or start a new branch and carry over the relevant changes.

Also keep in mind that #188 added Emissions|{Level-3 Species}|AFOLU|Land|Fires and subcategories, so these have to be removed if you implement an alternative solution.

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.

4 participants