# Issues in running ptfire (2018 inventory) **URL:** \ **Category:** Emissions Inventory\ **Created:** [April 14, 2021, 1:17pm UTC](https://forum.cmascenter.org/t/issues-in-running-ptfire-2018-inventory/2250 "2021-04-14T13:17:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![huangj1311](https://avatars.discourse-cdn.com/v4/letter/h/8edcca/32.png) [@huangj1311](https://forum.cmascenter.org/u/huangj1311)\ **Post date:** [April 14, 2021, 1:17pm UTC](https://forum.cmascenter.org/t/issues-in-running-ptfire-2018-inventory/2250/1 "2021-04-14T13:17:46Z")
Hi all, I downloaded 2017 emission modeling platform from EPA FTP (ftp://newftp.epa.gov/air/emismod/2017/), and configured and ran ptfire for 2017 Jan ptfire. It went fine for onetime and daily scripts without any issue. All VOC and toxics can be recognized and there was no problem to create VOC.ncf. I then downloaded the most current 2018 fire inventory from ftp://newftp.epa.gov/air/emismod/2018/2018emissions/ and used similar configuration to run 2018 ptfire. onetime script was finished without ERROR, but VOC.ncf cannot be created ```auto WARNING: no sources with data for output of data variable "VOC" File will not be written. --->> Normal Completion of program SMKINVEN --->> Normal Completion of program SPCMAT --->> Normal Completion of program GRDMAT ``` When I ran daily for 2018 Jan, the fatal error is ```auto *** ERROR ABORT in subroutine GENPDOUT Problem with input file ``` However, there are tons of errors before this fatal error, ```auto Timestep written to PDAY for date and time 2018001:110000 Timestep written to PDAY for date and time 2018001:120000 Timestep written to PDAY for date and time 2018001:130000 Timestep written to PDAY for date and time 2018001:140000 Timestep written to PDAY for date and time 2018001:150000 Timestep written to PDAY for date and time 2018001:160000 Timestep written to PDAY for date and time 2018001:170000 Timestep written to PDAY for date and time 2018001:180000 Timestep written to PDAY for date and time 2018001:190000 Timestep written to PDAY for date and time 2018001:200000 Timestep written to PDAY for date and time 2018001:210000 Timestep written to PDAY for date and time 2018001:220000 Timestep written to PDAY for date and time 2018001:230000 Timestep written to PDAY for date and time 2018002:000000 Timestep written to PDAY for date and time 2018002:010000 Timestep written to PDAY for date and time 2018002:020000 Timestep written to PDAY for date and time 2018002:030000 Timestep written to PDAY for date and time 2018002:040000 ERROR: Both VOC|TOG and toxics are not found for the sourc: Region: 000000013021 Plant: 1307920180102 Char1: 1307920180102276 Char2: 0102 Char3: 1283 Char4: 00000000002811015001 ``` but I did check the VOC and HAPs for this source are in both ptinv and ptday files. Here are my runscripts and logs [Annual\_ptfire\_onetime\_12US1\_2018.csh](https://forum.cmascenter.org/uploads/short-url/26PGiG9Uft4dwhkAWwGvDI4ZopH.csh) (7.3 KB) [smkinven\_ptfire\_2017gb\_17jlog.txt](https://forum.cmascenter.org/uploads/short-url/cBbPKyYbCRqA2KH1y5Qnw1mcL4X.txt) (29.1 KB) [grdmat\_ptfire\_2017gb\_17j\_12US1log.txt](https://forum.cmascenter.org/uploads/short-url/r5ewpJzXUTXvwH7liIzjbPGd825.txt) (20.6 KB) Uploading: spcmat\_ptfire\_2017gb\_17j\_cmaq\_cb6ae7log.txt… [Annual\_ptfire\_daily\_12US1\_2018.csh](https://forum.cmascenter.org/uploads/short-url/xidYrofLezLpKW3jGiAbq7Dw10h.csh) (7.5 KB) the file I cannot upload here is the jan smkinv log here it is > **[smkinven\_ptfire\_jan\_2017gb\_17jlog.txt](https://drive.google.com/file/d/1Z6G68co66JVrdw3b_NsKFV1pMLpmy3-0/view?usp=sharing)** > > Google Drive file. any suggestions are very helpful I have also tried different pre-compiled smoke version(v4.5) and different platform (2014v2), but all gave me same error. @bbaek maybe you know some potential solutions? thank you Joey ---
**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:** [April 14, 2021, 1:31pm UTC](https://forum.cmascenter.org/t/issues-in-running-ptfire-2018-inventory/2250/2 "2021-04-14T13:31:39Z")
A different NHAPEXCLUDE file called nhapexclude \__2018gc\_ptfire_\_31mar2021\_v0.txt is needed to run 2018 fires. Have you used this file? ---
**Author:** ![huangj1311](https://avatars.discourse-cdn.com/v4/letter/h/8edcca/32.png) [@huangj1311](https://forum.cmascenter.org/u/huangj1311)\ **Post date:** [April 14, 2021, 1:37pm UTC](https://forum.cmascenter.org/t/issues-in-running-ptfire-2018-inventory/2250/3 "2021-04-14T13:37:32Z")
Alison, thanks, no I am still using nhapexclude\_2017\_ptfire\_17apr2020\_v0.txt, I will try that now. ---
**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:** [April 14, 2021, 2:09pm UTC](https://forum.cmascenter.org/t/issues-in-running-ptfire-2018-inventory/2250/4 "2021-04-14T14:09:03Z")
@eyth.alison is Right. Based on the error message, you need to use the paired NHAPEXCLUDE input file. If you still have a problem of generating VOC, I would suggest you to update the INVTABLE file as well. ---
**Author:** ![huangj1311](https://avatars.discourse-cdn.com/v4/letter/h/8edcca/32.png) [@huangj1311](https://forum.cmascenter.org/u/huangj1311)\ **Post date:** [April 14, 2021, 3:38pm UTC](https://forum.cmascenter.org/t/issues-in-running-ptfire-2018-inventory/2250/5 "2021-04-14T15:38:40Z")
@eyth.alison @bbaek this works, thank you both !