Turn on additional fire variables by default?

[wwieder]

it seems like additional fire variables would be helpful to have on by default (sum of all fire C fluxes)? Otherwise this seems difficult to calculate.

Also include:

• FireEmis_TOT (This seems to correspond to the CMIP variable fFire)
• SOMFIRE
• LITFIRE
• TOTFIRE * Note, this seems like it may be a misleading variable, as it's seemingly the sum of SOMFIRE and LITFIRE, see

  CTSM/src/biogeochem/CNVegCarbonFluxType.F90

  Line 5411 in 53f021b

  ! total ecosystem fire losses (TOTFIRE)

[wwieder]

see totfire%emis calculated here:

CTSM/src/biogeochem/CNFireEmissionsMod.F90

Line 283 in d393088

totfire%emis(p) = fire_flux ! gC/m2/sec

[ekluzek]

Yeah, it looks like all the fire emissions history variables are inactive even when emissions are turned on. Having at least this one would be good to do.

[wwieder]

I'm assuming this can go to B4B-dev?
Let's decide when this should come it and assign who should do the work.

[samsrabin]

SE meeting:

• Turning on the variables can go to b4b-dev if the merger agrees, as it will create DIFFs due to new fields.
• @slevis-lmwg will file a separate issue about TOTFIRE being misleading.

slevis note to self: Started branch mkactive_firevars on izumi in prep for downtime next wk

[wwieder]

@slevis-lmwg are there other CMIP7 variables requested that include lots of individual history fields to be written out? If so, I wonder if we should include any other new diagnostics to facilitate CMIP7 workflows?