ERROR ABORT in subroutine FORMLIST

Hello,

I am trying to run ptnonipm SMOKE run for 2023gf (2016v3 modeling). When I attempt to run ‘onetime’ script, I am getting error.

I checked the /intermed/ptnonipm/logs/smkinven_ptnonipm_2023gf_16j.log, and the error is

" ERROR: Problem processing formula 1: “PMC=PM10-PM2_5”
*** ERROR ABORT in subroutine FORMLIST

I am using all the input files as it is from EPA’s 2016v3 modeling except for EMIS file.

Would you please help me with this?

Thanks in advance

Can you please attach your log file and stdout?

Hi @eyth.alison

Please see the attached files
Terminal_out.txt (4.8 KB)
smkinven_ptnonipm_2023gf_16j.txt (11.0 KB)

Thanks in advance

Have you run with the inventories that come with the 2016v3 platform as a first cut to make sure that works before substituting in your own inventory?

The error suggests that your provided inventory doesn’t have any PM. If no PM is expected for your work, then you should set SMKINVEN_FORMULA to blank (“”).

If there is PM in your inventory, then there is something wrong with the inventory and we suggest attaching at least a portion of the inventory so we can take a look.

Can you upload a portion of your FLATFILE.csv inventory file?

I see in the log it says: WARNING: No kept pollutants found at line 29 . The source will be dropped.

Does the inventory have PM sources?

Hi @eyth.alison

I checked my FLATFILE, where I don’t have PM. I only have NOx. So, I used

SMKINVEN_FORMULA “”

Then I ran the onetime script, where I can see segmantation fault core dumped error with
message " ERROR detected in Smkreport". Then I checked the smkreport file, I don’t see any error. the last line is " Selecting records" then nothing else. Which looks to me, run is incomplete?

Would you please look at it?
smkreport_ptnonipm_2023gf_16j_inv.txt (7.3 KB)

Please see the part of the terminal output

Blockquote You will need to enter the logical names for the input and
output files (and to have set them prior to program start,
using “setenv ”).

 You may use END_OF-FILE (control-D) to quit the program
 during logical-name entry. Default responses are given in
 brackets [LIKE THIS] and can be accepted by hitting the
 <RETURN> key.

Segmentation fault (core dumped)
0.3u 0.0s 0:01.01 31.6% 0+0k 25760+24io 21pf+0w
now checking log file /Air/emismod/2016/v3/FOLDER/2023gf_16j/intermed/ptnonipm/logs/smkreport_ptnonipm_2023gf_16j_inv.log


  • ERROR detected in logfile:
  • /Air/emismod/2016/v3/FOLDER/2023gf_16j/intermed/ptnonipm/logs/smkreport_ptnonipm_2023gf_16j_inv.log

ERROR detected in Smkreport
ERROR: Running qa_run for inv
log analyzer
Getting message data (might take some time)…
grep: /Air/emismod/2016/v3/FOLDER/2023gf_16j/intermed/ptnonipm/logs: Is a directory
grep: /Air/emismod/2016/v3/FOLDER/2023gf_16j/intermed/ptnonipm/logs: Is a directory
Finished getting data
Classifying message types…
Total number of known messages: 24
Total number of unknown messages: 0
Level 3 analysis…
Finished classifying message types
log analyzer
Getting message data (might take some time)…
grep: /Air/emismod/2016/v3/FOLDER/2023gf_16j/intermed/ptnonipm/logs: Is a directory
grep: /Air/emismod/2016/v3/FOLDER/2023gf_16j/intermed/ptnonipm/logs: Is a directory
Finished getting data
Classifying message types…
Total number of known messages: 24
Total number of unknown messages: 0
Level 1 analysis…
Finished classifying message types
Testing for exit priority

It could conceivably be useful to compile for one of the debug/traceback/check-everything binary types (I/O API $BIN binary compile types for Makeinclude.$BIN of the form Makeinclude.*dbg).

That will give you “traceback” info that should tell you at what line of what subroutine the seg-fault happened. Then at least you’ll have some idea where the problem is…

1 Like

Smkreport is crashing on the reports that generate emissions by speciation profile for PM2.5 and VOC, since neither of those pollutants is in the inventory.

The easiest thing to do would be to skip Smkreport altogether by adding this line to run_settings.txt:

ptnonipm, 12US1, smkreport, ALL, 0, 0, N

Or, if you want to run Smkreport, you could:

  • Use the same REPCONFIG_INV as the canada_ag sector

  • Remove REPCONFIG_INV3 from the ptnonipm run script

Hi @eyth.alison

As your suggestions,

I added a line in the run_settings.txt,
run_settings.txt (1.1 KB)
But still same error. If I add that line, shouldn’t it remove smkreport file?:

NOTES TO CONSIDER WHEN BUILDING THIS DATASET:

1) If running the Temporal program for multiple dates, you can either turn

off all or none of the dates per run. To do this, make sure that the

date range given includes the FIRST date of each Temporal program run.

2) Entries do not need to be here for a “Yes”, since the defaults in the

main run script are assumed to be “Yes”. However, including “Y” entries

will not hurt anything.

3) Sector-specific “Y” entries will override Sector = “all” “N” entries

for the same grid, program, part, and date range.

4) (Added by C. Allen) If you set Temporal to Y, then this induces a bug

where the Temporal files are deleted after they are created. To avoid,

never set Temporal to Y to override an “all=N” setting (only use N settings).

5) (Added by C. Allen) The domain totals program (“domain”) doesn’t work for

files larger than 2 GB. Therefore, it is turned off for 12EUS1.

Column labels:

Sector, Grid, Environment Variable Name, Part, Start Date, End Date, Value

ptnonipm, 12US2, smkreport, ALL, 0, 0, N

Hi @eyth.alison

Using REPCONFIG_INV as the canada_ag sector and removing REPCONFIG_INV3 works for the ‘onetime’ script for ptnonipm.

But when I tried run ‘daily’ script
Annual_ptnonipm_daily_12US1_2023gf_16j_WC.txt (6.6 KB)

I get the too many arugements error in terminal. What could be the reason?. Please see below terminal output

Linux2_x86_64ifort
NOTE: Default MONTH setting to ‘jan’
/bin/ls: No match.
/bin/ls: No match.
/bin/ls: No match.
/bin/ls: No match.
source: Too many arguments.

Thanks in advance

Can you please upload your standard output?

Also, try removing /bin/ before ls, to see if that makes a difference

Was this issue resolved by using tcsh instead of csh?

1 Like

Yes, i solved the issue using tcsh.