Segmentation fault occurred in laypoint (SMOKE v5.1)

SMOKE
1

Hi,

I’m running the ptfire-rx sector with the self-compiled SMOKE V5.1 (Intel compiler) and the 2018v2 NEI platform.
I have successfully run the inline mode, however, I’d like to have plume rise with layering / Laypoint instead of inline.
After turning off the inline mode, the “onetime” script finished with no problem. However, the “daily” one always failed with the following errors:

./scripts/emf/smk_pt_daily_emf.csh 4SE2 2018_4SE -m 5 6 7 8 9 10 0 daily
/bin/ls: No match.
/bin/ls: No match.
/bin/ls: No match.
/bin/ls: No match.
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source
laypoint           00000000009D9E3A  Unknown               Unknown  Unknown
libpthread-2.28.s  000014CAAA83ECF0  Unknown               Unknown  Unknown
laypoint           0000000000419FE0  fire_plmris_              216  fire_plmris.f
laypoint           000000000040FE8F  MAIN__                   1515  laypoint.f
laypoint           0000000000407122  Unknown               Unknown  Unknown
libc-2.28.so       000014CAAA29DD85  __libc_start_main     Unknown  Unknown
laypoint           000000000040702E  Unknown               Unknown  Unknown
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source
laypoint           00000000009D9EDE  Unknown               Unknown  Unknown
libpthread-2.28.s  000014CAAA83ECF0  Unknown               Unknown  Unknown
laypoint           0000000000B7087A  Unknown               Unknown  Unknown
laypoint           0000000000B705D2  Unknown               Unknown  Unknown
laypoint           0000000000B72372  Unknown               Unknown  Unknown
laypoint           0000000000B1C287  Unknown               Unknown  Unknown
laypoint           0000000000B1777B  Unknown               Unknown  Unknown
laypoint           0000000000B17648  Unknown               Unknown  Unknown
laypoint           0000000000B1730D  Unknown               Unknown  Unknown
laypoint           0000000000B17C3E  Unknown               Unknown  Unknown
laypoint           0000000000ACDF5B  Unknown               Unknown  Unknown
libc-2.28.so       000014CAAA2B426C  Unknown               Unknown  Unknown
libc-2.28.so       000014CAAA2B43A0  on_exit               Unknown  Unknown
laypoint           00000000009D4FFB  Unknown               Unknown  Unknown
laypoint           00000000009D9E3A  Unknown               Unknown  Unknown
libpthread-2.28.s  000014CAAA83ECF0  Unknown               Unknown  Unknown
laypoint           0000000000419FE0  fire_plmris_              216  fire_plmris.f
laypoint           000000000040FE8F  MAIN__                   1515  laypoint.f
laypoint           0000000000407122  Unknown               Unknown  Unknown
libc-2.28.so       000014CAAA29DD85  __libc_start_main     Unknown  Unknown
laypoint           000000000040702E  Unknown               Unknown  Unknown
grep: /work/chflab/jthuang/SMOKE/2018v2/2018gg_18j/intermed/ptfire-rx/logs: Is a directory
grep: /work/chflab/jthuang/SMOKE/2018v2/2018gg_18j/intermed/ptfire-rx/logs: Is a directory
grep: /work/chflab/jthuang/SMOKE/2018v2/2018gg_18j/intermed/ptfire-rx/logs: Is a directory
grep: /work/chflab/jthuang/SMOKE/2018v2/2018gg_18j/intermed/ptfire-rx/logs: Is a directory

I did not see any obvious errors in the laypoint log as the SMOKE laypoint program was killed suddenly. I have tried to increase the memory and
add “limit stacksize unlimited” at the beginning of the script, but the same errors cannot stop.
I have uploaded the related files for your review. Any help is appreciated!
Annual_ptfire-rx_daily_highactivity_4SE2_2018gg_18j.csh (8.4 KB)
laypoint_ptfire-rx.log.txt (30.3 KB)
rep_logs_ptfire-rx_2018gg_18j_4SE2_daily_level1.csv (8.8 KB)

2

Thank you for posting all of the logs and scripts. This is a very odd location for the fire plume rise to fail.

There is a recent bugfix for laypoint on the SMOKE github (GitHub - CEMPD/SMOKE: Create emissions inputs for multiple air quality modeling systems with unmatched speed and flexibility) that may resolve the issue. Please try to build laypoint from the latest source on github and let us know if whether or not you are successfully able to get 3D emissions.