# SMOKE using HTAPv3 emission **URL:** \ **Category:** SMOKE\ **Created:** [December 7, 2024, 11:06pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421 "2024-12-07T23:06:39Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Heomin](https://avatars.discourse-cdn.com/v4/letter/h/9fc348/32.png) [@Heomin](https://forum.cmascenter.org/u/Heomin)\ **Post date:** [December 7, 2024, 11:06pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/1 "2024-12-07T23:06:39Z")
Hello, I am working on creating CMAQ-ready emissions using SMOKE with the HTAPv3 inventory. However, since HTAPv3 is provided as monthly data, I encounter errors during the Smkinven process. I would appreciate it if you could provide a solution to this issue. The error message I received is as follows: Value for WKDAY\_NORMALIZE: N returning FALSE NOTE: Setting inventory to use full-week normalizer for weekly profiles Bad NDIMS for “emi\_bc” in “TMPFILE” Could not read “emi\_bc” from gridded inventory file \*\*\* ERROR ABORT in subroutine RDGRDNCF Problem reading gridded inventory file ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [December 9, 2024, 3:12pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/2 "2024-12-09T15:12:53Z")
If you are trying to use a configuration originally designed for HTAPv2, the file organization has changed. The HTAPv2 gridded data is structured with the monthly files separated by sector and pollutant, so the EMISLST input for SMOKE would look like this: #LIST GRID #SCC, Pollutant, Variable\_Name, Month, File\_location\_name “ENERGY”,“PEC”,“emi\_bc”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_BC\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“CO”,“emi\_co”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_CO\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“NH3”,“emi\_nh3”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_NH3\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“NOX”,“emi\_nox”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_NOx\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“POC”,“emi\_oc”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_OC\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“PM10”,“emi\_pm10”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_PM10\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“SO2”,“emi\_so2”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_SO2\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“VOC”,“emi\_nmvoc”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_NMVOC\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“PM2\_5\_OTH”,“emi\_pm2.5\_other”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_PM2.5\_OTHER\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” “ENERGY”,“PM2\_5”,“emi\_pm2.5”,6,“/work/EMIS/em\_v6.3/global/2011\_BaseA/inputs/work/HTAP/ENERGY/edgar\_HTAP\_PM2.5\_emi\_ENERGY\_2010\_6.0.1x0.1.nc” However for HTAPv3 the data is structured as such, with separate monthly files per pollutant, but each file contains all the sectors as variables. So, EMISLST input to SMOKE for HTAPv3 would look like this: #LIST GRID #SCC, Pollutant, Variable\_Name, Month, File\_location\_name “ENERGY”,“PEC”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_BC.nc” “ENERGY”,“CO”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_CO.nc” “ENERGY”,“NH3”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_NH3.nc” “ENERGY”,“VOC”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_NMVOC.nc” “ENERGY”,“NOX”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_NOx.nc” “ENERGY”,“POC”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_OC.nc” “ENERGY”,“PM10”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_PM10.nc” “ENERGY”,“PM2\_5”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_PM2.5.nc” “ENERGY”,“PM2\_5\_OTH”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_PM2.5\_OTHER.nc” “ENERGY”,“SO2”,“Energy”,4,“/work/MOD3DEV/ktalgo/WR713/work/inputs/HTAPv3/data/fluxes/monthly/edgar\_HTAPv3\_2018-04\_SO2.nc” Therefore, for HTAPv3 the third column in the EMISLST input should be the sector (e.g. “Energy” in the example above) instead of the pollutant. ---
**Author:** ![Heomin](https://avatars.discourse-cdn.com/v4/letter/h/9fc348/32.png) [@Heomin](https://forum.cmascenter.org/u/Heomin)\ **Post date:** [December 10, 2024, 1:24am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/3 "2024-12-10T01:24:40Z")
Thank you for your response ! I have another question. 1. If there are no memory issues, is it okay for the `arinv*.lst` file to include multiple sectors? for example: #LIST GRID #SCC,InvPollName,EDGAR\_VarName,Month,FileName #DESC Sample test case for htap sector based on HTAP version 3.1 AGRICULTURE,PEC,emi\_bc,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_BC\_AGRICULTURE.nc AGRICULTURE,POC,emi\_oc,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_OC\_AGRICULTURE.nc AGRICULTURE,CO,emi\_co,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_CO\_AGRICULTURE.nc AGRICULTURE,NOX,emi\_nox,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_NOx\_AGRICULTURE.nc AGRICULTURE,VOC,emi\_nmvoc,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_NMVOC\_AGRICULTURE.nc AGRICULTURE,PM10,emi\_pm10,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_PM10\_AGRICULTURE.nc AGRICULTURE,PM2\_5,emi\_pm2.5,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_PM2.5\_AGRICULTURE.nc AGRICULTURE,SO2,emi\_so2,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_SO2\_AGRICULTURE.nc AGRICULTURE,NH3,emi\_nh3,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_NH3\_AGRICULTURE.nc RESIDENTIAL,PEC,emi\_bc,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_BC\_RESIDENTIAL.nc RESIDENTIAL,POC,emi\_oc,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_OC\_RESIDENTIAL.nc RESIDENTIAL,CO,emi\_co,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_CO\_RESIDENTIAL.nc RESIDENTIAL,NOX,emi\_nox,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_NOx\_RESIDENTIAL.nc RESIDENTIAL,VOC,emi\_nmvoc,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_NMVOC\_RESIDENTIAL.nc RESIDENTIAL,PM10,emi\_pm10,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_PM10\_RESIDENTIAL.nc RESIDENTIAL,PM2\_5,emi\_pm2.5,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_PM2.5\_RESIDENTIAL.nc RESIDENTIAL,SO2,emi\_so2,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_SO2\_RESIDENTIAL.nc RESIDENTIAL,NH3,emi\_nh3,0,/EMIS/EDGAR\_HTAPv3\_1/SMK/2020/edgar\_HTAPv3\_2020\_NH3\_RESIDENTIAL.nc 1. If the run period is from 20200525 to 20200705, should I split the runs by months (May, June, July) and run three separate runs? Or can I just run it once with the June inventory? ---
**Author:** ![Heomin](https://avatars.discourse-cdn.com/v4/letter/h/9fc348/32.png) [@Heomin](https://forum.cmascenter.org/u/Heomin)\ **Post date:** [December 11, 2024, 1:37am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/4 "2024-12-11T01:37:51Z")
1. If the inventory corresponds to a specific month, will the monthly factor still be applied? If not, how should it be configured? ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [December 13, 2024, 4:04am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/5 "2024-12-13T04:04:16Z")
In response to your query: ---
**Author:** ![Heomin](https://avatars.discourse-cdn.com/v4/letter/h/9fc348/32.png) [@Heomin](https://forum.cmascenter.org/u/Heomin)\ **Post date:** [December 14, 2024, 9:12am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/6 "2024-12-14T09:12:50Z")
Could you please say it again ? ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [December 16, 2024, 1:29am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/7 "2024-12-16T01:29:36Z")
Apologies, some how it did not get pasted properly: - We’ve always split the ARINV files by sector. I’m not sure if it matters if all sectors are listed in a single ARINV input. - All three months should be run. From a scripting standpoint it’s probably easier to just run the full May 1st through July 31st period in SMOKE and disregard the May and July dates that you don’t need - Since all the HTAPv3 inventories are monthly, the monthly profiles are not used, however I believe the Temporal program in SMOKE still expects monthly profiles as input (ATPRO\_MONTHLY) so we pass them in anyway. I hope that helps. ---
**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:** [December 16, 2024, 2:30pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/8 "2024-12-16T14:30:48Z")
Based on the issues observed in a previous thread I recommend running one HTAP sector per SMOKE sector and then merging. See the following thread for more information: > [@SMOKEv4.8 SMKMERGE ERROR: Gridding matrix dimension is inconsistent with records count! Delete gridding matrix and recreate it](https://forum.cmascenter.org/t/smokev4-8-smkmerge-error-gridding-matrix-dimension-is-inconsistent-with-records-count-delete-gridding-matrix-and-recreate-it/5307/12): > > Unfortunately I was not able to reproduce the error shown in the original post using the datasets that you shared. I’ve attached the smkmerge log from my test run with the MEIC transportation inventory if you’d like to compare. [smkmerge.txt](https://forum.cmascenter.org/uploads/short-url/x490D7O0Cfj61vfrOwp5bv0Ix8X.txt) (51.9 KB) How is you arinv configured? Have you tried running each MEIC or MIX sector separately? ---
**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:** [December 16, 2024, 3:36pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/9 "2024-12-16T15:36:25Z")
In theory, since each sector has its own SCC ID (i.e., TRANSPORT,) defined in the ARINV file, multiple sectors can be processed as a single sector as long as you create the master speciation profiles and temporal profiles input files for all sectors. However, I would also suggest for you to run them individually as @james.beidler suggested since it requires significant amount of memory to process all sectors as a single sector. ---
**Author:** ![Heomin](https://avatars.discourse-cdn.com/v4/letter/h/9fc348/32.png) [@Heomin](https://forum.cmascenter.org/u/Heomin)\ **Post date:** [December 19, 2024, 5:32am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/10 "2024-12-19T05:32:52Z")
Thank you for your response ! @eyth.alison @james.beidler @bbaek ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [December 25, 2024, 9:33am UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/11 "2024-12-25T09:33:30Z")
Hi Mr.alison, Merry Chrismas! I am wondering why HTAP V3 should be treated monthly rather than yearly since I noticed that there are also yearly data for HTAPv3. ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [December 30, 2024, 5:16pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/12 "2024-12-30T17:16:23Z")
It would be more accurate to use the actual monthly data than to try to approximate the monthly splits from the yearly data using temporal profiles. ---
**Author:** ![yan2024](https://avatars.discourse-cdn.com/v4/letter/y/59ef9b/32.png) [@yan2024](https://forum.cmascenter.org/u/yan2024)\ **Post date:** [December 30, 2024, 5:20pm UTC](https://forum.cmascenter.org/t/smoke-using-htapv3-emission/5421/13 "2024-12-30T17:20:19Z")
Thank you so much！ I have already splited integrated HTAP v3 monthly file into 12 seperated one but I encounted some problems when processing edgar htap3 v3 data…could you please browse my latest thread in SMOKE and provide some suggestions？