Hello,
I'm trying to run l3mapgen, and getting an error message:
execution exception: java.io.IOException: l3mapgen failed with exit code 139.
Check log for more details.
/Applications/seadas-7.3.2/ocssw/run/scripts/ocssw_runner: line 22: 27388 Segmentation fault: 11 $*
The log isn't much more helpful:
Execution log for
[/Applications/seadas-7.3.2/ocssw/run/scripts/ocssw_runner, --ocsswroot, /Applications/seadas-7.3.2/ocssw, l3mapgen, par=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/L3_Bin_q0/Jul_19-26/tmpParFile6713909679778664835.par]
/Applications/seadas-7.3.2/ocssw/run/scripts/ocssw_runner: line 22: 26881 Segmentation fault: 11 $*
I'd previously run l3mapgen on binned l3 files with success. I reran my files through l2bin with a more strigent quality level (qual_max=0) than previously. I also set the suite to "SST", whereas I previously left this field blanks. As far as I can figure out, this is the only difference.
Can't find any notation on what exit code 139 means.
Any ideas?
Thanks in advance!
l3mapgen error
-
- Posts: 7
- Joined: Mon Jan 30, 2017 2:13 pm America/New_York
-
- Posts: 1519
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 9 times
l3mapgen error
This is the error:
Which means l3mapgen was REALLY unhappy for some reason (also suggests that there's a lurking bug)
Can you provide more details on what you passed to l3mapgen? If you used the GUI to set it up, retrace your steps, save the parameter file and attach it to your post.
Also, can you provide your OS version?
Sean
Segmentation fault: 11
Which means l3mapgen was REALLY unhappy for some reason (also suggests that there's a lurking bug)
Can you provide more details on what you passed to l3mapgen? If you used the GUI to set it up, retrace your steps, save the parameter file and attach it to your post.
Also, can you provide your OS version?
Sean
-
- Posts: 7
- Joined: Mon Jan 30, 2017 2:13 pm America/New_York
l3mapgen error
Hi Sean,
Sure, no problem.
The par file for l3mapgen is as follows:
ifile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/L3_Bin_q0/wholecruise/A2016193.L3bTEST
ofile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/L3_Bin_q0/wholecruise/output
resolution=1km
interp=area
The primary difference between this attempt, and the attempt that worked fine was during the l2bin stage.
l3mapgen failed when I used the following parameters for l2bin:
infile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/A2016193134500.L2_LAC_SST.nc
ofile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/test.nc
resolve=1
suite=SST
flaguse=LAND,HISOLZEN
prodtype=
night=
qual_max=0
verbose=1
Also of note: I loaded the par file each time - didn't fill it out.
When I process using l2bin using these parameters, the l3mapgen stage works fine:
infile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/A2016193134500.L2_LAC_SST.nc
ofile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/test2
resolve=1
flaguse=ATMFAIL,LAND,HILT,HISATZEN,STRAYLIGHT,CLDICE,COCCOLITH,LOWLW,CHLWARN,CHLFAIL,NAVWARN,MAXAERITER,ATMWARN,HISOLZEN,NAVFAIL,FILTER,HIGLINT
prodtype=
night=
qual_max=0
verbose=1
The primary difference being: in the case that did not work, I specified qual_max, resolve and used the SST suite option (and associated flags). In the case that did work, I only specified qual_max and resolve, and used the flags that auto-loaded when I selected my file.
No issues using l3bin in either case.
My macOS is 10.12.3.
I've got everything I need now, so no stress here. But I hope this helps you track down any bugs!
Sure, no problem.
The par file for l3mapgen is as follows:
ifile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/L3_Bin_q0/wholecruise/A2016193.L3bTEST
ofile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/L3_Bin_q0/wholecruise/output
resolution=1km
interp=area
The primary difference between this attempt, and the attempt that worked fine was during the l2bin stage.
l3mapgen failed when I used the following parameters for l2bin:
infile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/A2016193134500.L2_LAC_SST.nc
ofile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/test.nc
resolve=1
suite=SST
flaguse=LAND,HISOLZEN
prodtype=
night=
qual_max=0
verbose=1
Also of note: I loaded the par file each time - didn't fill it out.
When I process using l2bin using these parameters, the l3mapgen stage works fine:
infile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/A2016193134500.L2_LAC_SST.nc
ofile=/Users/alysiaherr/Dropbox/ALYSIA/MATLAB_alysia/Sat_SST/RAW_L2/test2
resolve=1
flaguse=ATMFAIL,LAND,HILT,HISATZEN,STRAYLIGHT,CLDICE,COCCOLITH,LOWLW,CHLWARN,CHLFAIL,NAVWARN,MAXAERITER,ATMWARN,HISOLZEN,NAVFAIL,FILTER,HIGLINT
prodtype=
night=
qual_max=0
verbose=1
The primary difference being: in the case that did not work, I specified qual_max, resolve and used the SST suite option (and associated flags). In the case that did work, I only specified qual_max and resolve, and used the flags that auto-loaded when I selected my file.
No issues using l3bin in either case.
My macOS is 10.12.3.
I've got everything I need now, so no stress here. But I hope this helps you track down any bugs!