# FINN fire emission process **URL:** \ **Category:** SMOKE\ **Tags:** admin\ **Created:** [June 24, 2021, 8:48am UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450 "2021-06-24T08:48:01Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [June 24, 2021, 8:48am UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/1 "2021-06-24T08:48:01Z")
Hello CMAQ community, I am trying to figure out using FINN fire emission with my CMAQ modeling over CONUS but I have no clues how SMOKE could process the FINN. Any comments are highly appreciated! Could you please find a free moment to reply to me? @wyat.appel @bbaek ---
**Author:** ![bbaek](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/bbaek/32/22_2.png) [@bbaek](https://forum.cmascenter.org/u/bbaek)\ **Post date:** [June 24, 2021, 12:40pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/2 "2021-06-24T12:40:22Z")
You need to process FINN fire emissions and convert them into SMOKE-ready FF10 formats. I do believe there are scripts that could assist you to covert them into these FF10 formatted files. @eyth.alison probably can assist you on that. [Point annual FF10 file](https://www.cmascenter.org/smoke/documentation/4.8.1/html/ch08s02s08.html#sect_input_ptinv_ff10) and [Point daily FF10 file](https://www.cmascenter.org/smoke/documentation/4.8.1/html/ch08s02s06.html#sect_input_ptday_ff10) ---
**Author:** ![barronh](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@barronh](https://forum.cmascenter.org/u/barronh)\ **Post date:** [June 24, 2021, 5:43pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/3 "2021-06-24T17:43:09Z")
I have also tinkered with FINN for CMAQ in the past to create a non-SMOKE system. The goal was to create a simple pathway to go from publicly available data to make CMAQ-ready emissions. I call it finn2cmaq[1]. It is probably not as good as the SMOKE approach, but it might be useful for users without SMOKE because it is a quick method that can be run in the cloud. To date, I have primarily used the 2D data as an alternative data source for comparison. There is no warranty expressed or implied… An example Jupyter Notebook that applies the system is available in the github project. Look in the examples folder. Right now, the PM speciation is a little simplistic. The EC, OC, SO4 and NO3 are explicit, but all the rest is in PMOTHR. This could certainly be improved, and should be QA’d during any application… [1] [GitHub - barronh/finn2cmaq: Fire emission pre-processor for CMAQ.](https://github.com/barronh/finn2cmaq) ---
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [June 24, 2021, 6:47pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/4 "2021-06-24T18:47:23Z")
Thanks so much for providing this and it is super helpful. May I ask whether there are any species mapping for GEOS-Chem to SAPRC mechanism? Because I find that currently, it supports the CB mechanism. Thanks again! ---
**Author:** ![barronh](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@barronh](https://forum.cmascenter.org/u/barronh)\ **Post date:** [June 24, 2021, 8:18pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/5 "2021-06-24T20:18:22Z")
The finn2cmaq processor uses the GEOS-Chem speciated inputs by default, but it is mechanism agnostic. You could instead use the SAPRC99 speciated inputs. You’d just have to replace the speciation converter file used by the `daily2hourly3d.py` script. By default, it uses the `aux/gc12_to_cb6r3_ae7.txt` file. Assuming you want to speciate for SAPRC07TC with AE6, you would basically create a similar file `aux/saprc99_to_saprc07tc_ae6.txt` where the species names match the names used by CMAQ.[1,2] If you do, please make an issue on the github issue site and share your script. I’ll include it in the distribution. [1] [CMAQ/saprc07tc\_ae6\_aq\_species\_table.md at master · USEPA/CMAQ · GitHub](https://github.com/USEPA/CMAQ/blob/master/CCTM/src/MECHS/mechanism_information/saprc07tc_ae6_aq/saprc07tc_ae6_aq_species_table.md) [2] [CMAQ/saprc07tc\_ae6\_aq\_species\_table\_aerosol.md at master · USEPA/CMAQ · GitHub](https://github.com/USEPA/CMAQ/blob/master/CCTM/src/MECHS/mechanism_information/saprc07tc_ae6_aq/saprc07tc_ae6_aq_species_table_aerosol.md) ---
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [June 24, 2021, 8:32pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/6 "2021-06-24T20:32:57Z")
Thanks for your quick reply! Sure, I would like to write the txt file with SAPRC07TC with AE6 (it is also the mechanism which we currently used.) I will post the issue on GitHub when I finish. ---
**Author:** ![bandaoshutiao](https://avatars.discourse-cdn.com/v4/letter/b/9fc348/32.png) [@bandaoshutiao](https://forum.cmascenter.org/u/bandaoshutiao)\ **Post date:** [March 21, 2022, 1:39pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/7 "2022-03-21T13:39:58Z")
**hi barronh** **An error occurred when I used your method.** **This is a domain I set up myself** (base) [/data2/sunzhixu/CMAQv5.3.2/PREP/finn/finn2cmaq-master/scripts]$ python3 txt2daily.py …/aux/GRIDDESC CN36KM 2018 FINNv1.5\_2018.GEOSCHEM.tar.gz /data4/sunzhixu/outdata/emis/finn/mid/FINNv1.5\_2018.GEOSCHEM.nc \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: SDATE was -635; using 1970001 Traceback (most recent call last): File “txt2daily.py”, line 118, in gf = pnc.pncopen(args.GRIDDESC, format=‘griddesc’, GDNAM=args.GDNAM) File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/\_getreader.py”, line 153, in pncopen outfile = reader(\*args, \*\*kwds) File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_griddesc.py”, line 132, in **init** self.setgrid(withcf=withcf) File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_griddesc.py”, line 185, in setgrid grd = self.\_grd[key] KeyError: ‘CN36KM’ **When I use domian in example, it also report an error** (base) [/data2/sunzhixu/CMAQv5.3.2/PREP/finn/finn2cmaq-master/scripts]$ python3 txt2daily.py …/aux/GRIDDESC 108NHEMI2 2018 /data4/sunzhixu/outdata/emis/finn/FINNv1.5\_2018.GEOSCHEM.tar.gz /data4/sunzhixu/outdata/emis/finn/mid/FINNv1.5\_2018.GEOSCHEM.nc \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: SDATE was -635; using 1970001 \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: IOAPI\_ISPH is assumed to be 6370000.; consistent with WRF \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: IOAPI\_ISPH is assumed to be 6370000.; consistent with WRF Traceback (most recent call last): File “txt2daily.py”, line 119, in outf = process(gf, args) File “txt2daily.py”, line 102, in process outf.updatemeta() File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_ioapi.py”, line 746, in updatemeta self.getVarlist(update=True) File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_ioapi.py”, line 593, in getVarlist varliststr\_old = getattr(self, ‘VAR-LIST’) AttributeError: ‘griddesc’ object has no attribute ‘VAR-LIST’ **What’s the problem** **I look forward to your reply** **zhixu** ---
**Author:** ![barronh](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@barronh](https://forum.cmascenter.org/u/barronh)\ **Post date:** [March 24, 2022, 4:13pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/8 "2022-03-24T16:13:19Z")
I replied to this in the finn2cmaq issues. > > > \*\*This is a domain I set up myself\*\* > (base) \[/data2/sunzhixu/CMAQv5.3.2/PREP/fi…nn/finn2cmaq-master/scripts\]$ python3 txt2daily.py …/aux/GRIDDESC CN36KM 2018 FINNv1.5\_2018.GEOSCHEM.tar.gz /data4/sunzhixu/outdata/emis/finn/mid/FINNv1.5\_2018.GEOSCHEM.nc > \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: > SDATE was -635; using 1970001 > Traceback (most recent call last): > File “txt2daily.py”, line 118, in > gf = pnc.pncopen(args.GRIDDESC, format=‘griddesc’, GDNAM=args.GDNAM) > File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/\_getreader.py”, line 153, in pncopen > outfile = reader(\*args, \*\*kwds) > File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_griddesc.py”, line 132, in init > self.setgrid(withcf=withcf) > File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_griddesc.py”, line 185, in setgrid > grd = self.\_grd\[key\] > KeyError: ‘CN36KM’ > > \*\*When I use domian in example, it also report an error\*\* > (base) \[/data2/sunzhixu/CMAQv5.3.2/PREP/finn/finn2cmaq-master/scripts\]$ python3 txt2daily.py …/aux/GRIDDESC 108NHEMI2 2018 /data4/sunzhixu/outdata/emis/finn/FINNv1.5\_2018.GEOSCHEM.tar.gz /data4/sunzhixu/outdata/emis/finn/mid/FINNv1.5\_2018.GEOSCHEM.nc > \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: > SDATE was -635; using 1970001 > \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: > IOAPI\_ISPH is assumed to be 6370000.; consistent with WRF > \*\*PNC:/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/pncwarn.py:24:UserWarning: > IOAPI\_ISPH is assumed to be 6370000.; consistent with WRF > Traceback (most recent call last): > File “txt2daily.py”, line 119, in > outf = process(gf, args) > File “txt2daily.py”, line 102, in process > outf.updatemeta() > File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_ioapi.py”, line 746, in updatemeta > self.getVarlist(update=True) > File “/data/home/sunzhixu/.local/lib/python3.8/site-packages/PseudoNetCDF/cmaqfiles/\_ioapi.py”, line 593, in getVarlist > varliststr\_old = getattr(self, ‘VAR-LIST’) > AttributeError: ‘griddesc’ object has no attribute ‘VAR-LIST’ > > \*\*I can't find out the cause of this error report，I would appreciate it if you could help me > I also asked you on CMAS forum\*\* ---
**Author:** ![bandaoshutiao](https://avatars.discourse-cdn.com/v4/letter/b/9fc348/32.png) [@bandaoshutiao](https://forum.cmascenter.org/u/bandaoshutiao)\ **Post date:** [July 26, 2023, 11:29am UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/9 "2023-07-26T11:29:31Z")
Hi Sorry to bother you. Have you finished SAPRC07TC speciated inputs?~~ ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [April 4, 2025, 3:31pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/10 "2025-04-04T15:31:07Z")
Hi barronh, I am using program you coded to process FINN to pre-CMAQ data. But I met some problems. I tried to merged this file with other emis files processed by layalloc program from SMOKE which uses height for layering rather than sigma value. I am wondering can I change way of layering to height rather than sigma with your program code? ---
**Author:** ![barronh](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@barronh](https://forum.cmascenter.org/u/barronh)\ **Post date:** [April 4, 2025, 4:47pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/11 "2025-04-04T16:47:41Z")
yan2024, Conceptually, layalloc and finn2cmaq both output 3D files on the native layers. It should not matter whether they allocation to layers was based on height, pressure, sigma, or something else. Once the files are on layers, if the structures match, they should be mergable. I’m not sure, but I would guess that the outputs have different vertical structures which is complicating the merge process. To better understand, I would need at a minimum: - the script that is failing, - the error from the script, - the `ncdump -k` output from the files that are failing to merge, - the `ncdump -h` output from the files that are failing to merge. Even better would be for you to post a minimum example where it can be downloaded. A minimum example would include: - a script that is failing to merge just two files, - the two files that are failing to merge, - the error that the script outputs. ---
**Author:** ![pork](https://avatars.discourse-cdn.com/v4/letter/p/8e7dd6/32.png) [@pork](https://forum.cmascenter.org/u/pork)\ **Post date:** [April 7, 2025, 4:00am UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/12 "2025-04-07T04:00:24Z")
Hi Barron, I am also working on this topic. I have two questions regarding the FINN data. If you have also encountered before, I would like to have your suggestions. 1. The current FINN provides FRP. What is the FRP detection time in the FINN dataset? Since FINN uses both MODIS and VIIRS, which have different overpass times, I’m wondering what a good way would be to estimate detection time for FINN product. Additionally, does the product include nighttime FRP detections in its reported values? 2. Are the daily total emissions reported in FINN based on local day or UTC day? Thanks, Zongrun ---
**Author:** ![james.beidler](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@james.beidler](https://forum.cmascenter.org/u/james.beidler)\ **Post date:** [April 7, 2025, 12:55pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/13 "2025-04-07T12:55:06Z")
The FRP value included in FINN is an average of the FRP associated with a fire for the day, which indicates that the value could include data points from multiple overpass times and instruments. To get the overpass times you will need to pair the source data with the inventory. The timing information is documented in the FINNv2.5 manuscript ([GMD - The Fire Inventory from NCAR version 2.5: an updated global fire emissions model for climate and chemistry applications](https://doi.org/10.5194/gmd-16-3873-2023)): “The active fire products report the time of acquisition in Coordinated Universal Time (UTC). In contrast to previous versions of the model, **the FINNv2.5 preprocessor uses local time** in the specification of the date of a fire detection in order to facilitate comparisons of emissions estimates with observational data.” ---
**Author:** ![pork](https://avatars.discourse-cdn.com/v4/letter/p/8e7dd6/32.png) [@pork](https://forum.cmascenter.org/u/pork)\ **Post date:** [April 10, 2025, 11:46pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/14 "2025-04-10T23:46:14Z")
> [@james.beidler](#): > > “The active fire products report the time of acquisition in Coordinated Universal Time (UTC). In contrast to previous versions of the model, **the FINNv2.5 preprocessor uses local time** in the specification of the date of a fire detection in order to facilitate comparisons of emissions estimates with observational data.” Thanks a lot for your comment. I also asked the same questions to FINN. However, it seems they use the UTC time rather than local time when they create the data. Here is the discussion: > > > Dear FINN Developer Team, > > I have two questions regarding the FINN data: > > \* What… is the FRP detection time in the FINN dataset? I would like to interpolate FRP values to generate a diurnal plume height profile using hourly FRP. The detection time could be critical for the interpolation. Since FINN uses both MODIS and VIIRS, which have different overpass times, I’m wondering what would be a good way to estimate detection time. Additionally, does the product include nighttime FRP detections in its reported values? > > \* Are the daily total emissions reported in FINN based on local day or UTC day? > > Thank you very much for your help! > > Thanks, > Zongrun As they also mentioned, the FRP is averaged value from different products. ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [May 5, 2025, 3:54pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/15 "2025-05-05T15:54:49Z")
Hi barronh, Sorry for late reply. After that, I tried to merge all layers from this emisstion file to one layer and use SMOKE to do vertical layer alloc again to meet merging with other files. I think I resolved by this way. ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [September 21, 2025, 9:24am UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/16 "2025-09-21T09:24:11Z")
Hi barronh, Since your program distributes wildfire emissions with fixed vertical fractions, how could we adjust or improve this scheme to better approximate a dynamic plume rise approach like GBBEPx + Sofiev ([Dominance of Wildfires Impact on Air Quality Exceedances During the 2020 Record‐Breaking Wildfire Season in the United States - Li - 2021 - Geophysical Research Letters - Wiley Online Library](https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2021GL094908)), where injection heights respond to FRP, boundary layer height, and stability, which is critical for accurately representing plume height distribution? ---
**Author:** ![james.beidler](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@james.beidler](https://forum.cmascenter.org/u/james.beidler)\ **Post date:** [September 22, 2025, 1:08pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/17 "2025-09-22T13:08:33Z")
Both SMOKE and CMAQ can apply a dynamic fire plume rise scheme based on Briggs ( [4.6. Laypoint](https://www.cmascenter.org/smoke/documentation/5.2/html/ch04s06.html) ). This requires specifying sensible heat flux (HFLUX) for each fire, which can be calculated either from the biomass consumed in FINN or estimated from the FRP using a conversion factor. EPA emissions modeling platforms use FINN to provide fire emissions for non-US areas. FINN inventories formatted for SMOKE can be found in the 2022 modeling platform fire inventory package ([https://gaftp.epa.gov/Air/emismod/2022/v1/2022emissions/2022hc\_fires\_inventory\_20dec2024.zip](https://gaftp.epa.gov/Air/emismod/2022/v1/2022emissions/2022hc_fires_inventory_20dec2024.zip)). Heat output is calculated from the biomass consumed and passes through SMOKE to the CMAQ model ready emissions files as hourly HFLUX. The same group at George Mason that authored the manuscript you referenced also implemented Sofiev into CMAQ ( [ACP - Impacts of estimated plume rise on PM2.5 exceedance prediction during extreme wildfire events: a comparison of three schemes (Briggs, Freitas, and Sofiev)](https://acp.copernicus.org/articles/23/3083/2023/) ). They may have code that allows you to apply the Sofiev scheme directly in CMAQ. ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [September 23, 2025, 3:28pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/18 "2025-09-23T15:28:29Z")
![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/1/17d7534373233d4c46c59406508fdcde75fddd23.png) Thank you for your reply! I am using SMOKE v4.7 but it seems this version does not directly process fire inventories (ptinv/ptday → HFLUX → NetCDF)? I am wondering which version of SMOKE should be used to work properly with the EPA 2022 emissions platform fire data? Does the EPA platform include a customized SMOKE different from the public release? Besides, after processing with SMOKE, are the resulting point-source NetCDF files (with hourly HFLUX) the same inputs expected by CMAQ under the _point source emissions input directory_ （as shown in the figure）? ---
**Author:** ![james.beidler](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@james.beidler](https://forum.cmascenter.org/u/james.beidler)\ **Post date:** [September 23, 2025, 3:46pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/19 "2025-09-23T15:46:46Z")
SMOKEv4.7 works directly with the ptinv and ptday inventories to generate the daily CMAQ emissions inputs (the stack\_groups and inln files highlighted) for fires as shown with both HFLUX and ACRESBURNED variables. A ptfire\_othna script for processing the FINN FF10s inventories this way can be found in the 2022 EMP scripts package ([https://gaftp.epa.gov/Air/emismod/2022/v1/smoke\_2022v1\_platform\_2022-2026\_core\_24jan2025.zip](https://gaftp.epa.gov/Air/emismod/2022/v1/smoke_2022v1_platform_2022-2026_core_24jan2025.zip)). The other option is to run the plume rise algorithm in SMOKE with laypoint. This will use the HFLUX, ACRESBURNED, and MCIP meteorology in SMOKE to create 3D-gridded files for CMAQ. ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [September 23, 2025, 4:13pm UTC](https://forum.cmascenter.org/t/finn-fire-emission-process/2450/20 "2025-09-23T16:13:32Z")
Thank you for your reply. I will try the script you mentioned to handle the file. Besides, I’m curious if you mentioned that implementing an algorithm in SMOKE requires you to modify the source code and embed the algorithm yourself? [Next page](https://forum.cmascenter.org/t/finn-fire-emission-process/2450.md?page=2)