l2gen failed with exit code 139

[hardguy233]

#I ran l2gen by default settings successfully, but when I changed Calibration Option's mode from "0-forward #processing " to "1 -inverse(calibration) mode, targeting to nLw=0", the problem shown ↓
#I'm using Operating System: Ubuntu 24.04.1 LTS
Kernel: Linux 6.11.0-19-generic
Architecture: x86-64
to run seadas 9.1.0, and my data is JPSS1_VIIRS.20250408T164800.L1B.nc.

execution exception:java.io.IOException:l2gen filed with exit code 139.
Check log for more details.
Loading default parameters from ...
input file ....

loading characteristics for VIIRSJ1
...
...

Using 868.0nm channel for cloud flagging over water.
Using 411.0nm channel for cloud flagging over land.

Processing scan # 0(1 of 3216)after 0 seconds.
...(address)/ocssw/bin/ocssw_runner:line 23:590394 Segmentation fault (core dumped)$*

#I'm trying to figure out how gain's value is calculated by changing different modes while processing L2.
#Thank you for any guidence you can supply on this!
-GH.

[OB SeaDAS - knowles]

Please try upgrading your OCSSW tag version to V2025.0 or later. Also you probably should consider updating to SeaDAS 9.2.0.

[OB.DAAC - SeanBailey]

The l2gen program is a complicated beast, especially when non-standard processing options are involved. The mode option really isn't something that should be changed by user input. What you want to change is vcal_opt. That option will set the mode option appropriately...it uses the same values, so 1 sets target nLw to zero, 2 uses the user-defined target nLw (provided by vcal_nlw) and 3 uses the user-defined target Lw (provided by vcal_lw). Yes, it could be better documented (and the code modified to prevent segfaulting on conditions it knows won't work)...we're slowly working on doing so.

Regards,
Sean