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

Implement fire trace gas emissions in FATES #1088

Open
7 tasks
rosiealice opened this issue Sep 22, 2023 · 0 comments
Open
7 tasks

Implement fire trace gas emissions in FATES #1088

rosiealice opened this issue Sep 22, 2023 · 0 comments

Comments

@rosiealice
Copy link
Contributor

There are a couple of issues related to this already. One which has evolved into a discussion of how to allow FATES and the fire emissions from CTSM to the atmosphere to operate concurrently here and another looking at the combustion of C and N (#485)

Here I wanted to focus on actually calculating the fire emissions in the context of FATES.

In the original SPITFIRE code, the emissions were calculated as the 'emissions factor' per species of trace gas, multiplied by the carbon burned (see exceprt from the original Thonicke 2010 SPITFIRE paper:

Image

For refererence, a link to whole Thonicke SPITFIRE paper is here

The emission factors are PFT specific, as described below. Their provenance was updated for CLM5.

Image

Also for reference, this is the table of EFs from the original SPITFIRE model, depicted in their table 1:

Image

It is worth noting that the CLM5 fire model works in a similar way
https://github.com/ESCOMP/CTSM/blob/2e2434d10e35404be5284022270f474d50d2db26/src/biogeochem/CNFireEmissionsMod.F90#L292

It seems like as of the CLM5 release, actually getting the emissions into the atmosphere was a 'research topic' (this from the CLM5 paper).

Image

I guess that Maria vM has probably continued with this effort since the release, Someone can update this thread if they know the status of that. It might be a good idea to involve her in this discussion. The canopy injection height calculations happen here. The emission heights are hard-coded:
https://github.com/ESCOMP/CTSM/blob/2e2434d10e35404be5284022270f474d50d2db26/src/biogeochem/CNFireEmissionsMod.F90#L324

There are potential some duplication issues that we would need to navigate here. My suspicion is that we should just have FATES handle its own emissions factors and code. The amount of actual physics involved is very small (it's only really 2-3 very straightforward equations) and (most importantly) the principle of FATES is that it handles everything with a PFT identity. Having to map a new PFT back onto an existing set of fire emissions would be a world of pain in the long run when we wanted to introduce new things into FATES. Plus there is a lot of potentially interesting science to be done with the links between e.g. plant trait and their emissions which we don't want to rule out.

Anyone have any thoughts on this? Here is a strawman list of tasks..

Tasks

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

No branches or pull requests

1 participant