I am trying to process a number of L2 oc (MODIS Aqua) files I ordered and downloaded.
I am running l2bin on individual wavelengths, starting with 207 original scenes (files). The line of code that gets submitted via command line is...
dmwarner$ /Users/dmwarner/Documents/MODIS/scripts/l2bin_lake.sh MODIS Michigan Rrs_443 2016
I am not getting that 207 L3bin files. And I am getting different numbers of L3 bin files depending on the wavelength I process.
I noticed that during the processing that there was the following result multiple times. This happens for each wavelength, some more than others, but none of them provide me with the full 207 L3 binned scenes. This is causing some problems for my processing chain and I would like to understand this behavior.
Working on A2016321182500.L2_LAC_OC.x.nc
Defined A2016321182500.L2_LAC_OC.x.nc
L2BIN 4.0.9 (Apr 27 2016 10:22:37)
INTERP parameter disabled.
Single HDF input
Averaging: standard
Resolution: 1
Max Qual Allowed: 2
prod_avg:
flagusemask: 33559043
required: 0
NetCDF4 input file
-W- /Users/seadas/ocssw/build/src/l2bin/dataday.c line 294: Insufficient valid latitudes found
Consider QC fail for file: A2016321182500.L2_LAC_OC.x.nc
...look at the file though, as I might be lying...
/Users/dmwarner/Documents/MODIS/scripts/l2bin_lake.sh: line 121: 22150 Segmentation fault: 11 l2bin infile=${INFILE} ofile=${ofile} prodtype=${prodtype} l3bprod=${3} resolve=${resolve} flaguse=${flaguse} noext=${noext}
When I open this file in SeaDAS there are clearly lots of valid latitudes (though some data are masked). Does anyone know why this is happening and if it is the cause of the Segmentation fault: 11, whatever that is? Is it possible that I am running out of memory or something? This seems unlikely as the file is 3.6 mb.
I am using a Mac running OSX 10.11, 16GB ram, SeaDAS v7.4. I've attached a png of the scene for reference and the script I am using for reference.
I have determined that processing the example file alone using the GUI is successful. I have also determined, by using a different Mac with 24GB of ram, that this is not a memory issue (in my opinion). Finally, it happens with flaguse ="NONE" or with a number of flags.
Thanks,
Dave
