Ocean Color Forum - Not logged in
Forum Ocean Color Home Help Search Login
Previous Next Up Topic SeaDAS / SeaDAS 6.x - General Questions / "Invalid pixel" error from out_track? (1951 hits)
By blesht Date 2012-07-30 16:58
Hi - I'm testing a script that applies a user-defined function, maps the result, and then uses out_track to extract a set of points from the mapped band.  While running it on a group of SeaWiFS L2 files, I've encountered an error that seems to suggest that there may be a problem with the input L2 file.  Here is an annotated (my comments to the right of the <- ) sample from the console as the script runs, including the error (which occurs after many images have been processed successfully.

bash-3.2$ ./extract_SWF_GLF.sh Ontario 1997 5                                                                         <- Invoke the script
IDL Version 8.0.1, Mac OS X (darwin i386 m32). (c) 2010, ITT Visual Information Solutions
Installation number: 230343.
Licensed for use by: Computer Sciences Corporation

SeaDAS Version 6.4 (pid = 10422)
         158
/Volumes/3TBDrive/SeaWiFS/L2/Ontario/1997/S1997262173835.L2.x.hdf         346                     <- First file
grp_name=Geophysical Data
Getting navigation data from HDF file...
Getting special lat/lon from HDF file...
Getting - "Rrs_443" data from HDF file...
Getting - "Rrs_490" data from HDF file...
Getting - "Rrs_510" data from HDF file...
Getting - "Rrs_555" data from HDF file...
Getting - "l2_flags" data from HDF file...
SeaDAS Projection -          128 out of          167 lines processed
SeaDAS Projection -          167 out of          167 lines processed
/Volumes/3TBDrive/SeaWiFS/L2/Ontario/1997/S1997264172940.L2.x.hdf         317                   <- Second file
grp_name=Geophysical Data
Getting navigation data from HDF file...
Getting special lat/lon from HDF file...
Getting - "Rrs_443" data from HDF file...
Getting - "Rrs_490" data from HDF file...
Getting - "Rrs_510" data from HDF file...
Getting - "Rrs_555" data from HDF file...
Getting - "l2_flags" data from HDF file...
SeaDAS Projection -          128 out of          167 lines processed
SeaDAS Projection -          167 out of          167 lines processed

[Many more successfully processed files snipped]                                                     <- Lines snipped out

/Volumes/3TBDrive/SeaWiFS/L2/Ontario/1997/S1997298181533.L2.x.hdf         207   <- File that causes error
grp_name=Geophysical Data
Getting navigation data from HDF file...
Getting special lat/lon from HDF file...
Getting - "Rrs_443" data from HDF file...
Getting - "Rrs_490" data from HDF file...
Getting - "Rrs_510" data from HDF file...
Getting - "Rrs_555" data from HDF file...
Getting - "l2_flags" data from HDF file...
SeaDAS Projection -          128 out of          167 lines processed
SeaDAS Projection -          167 out of          167 lines processed
SDP_BAND_PXVAL : Invalid pixel, line values :       79.0000      168.000
% Specified offset to array is out of range: PXRAW.
% Execution halted at: CHECK_BIT_DATA     43 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/check_bit_data.pro
%                      OUT_TRACK         317 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/out_track.pro
%                      $MAIN$         
% CLOSE: Variable is undefined: LUN.
% Execution halted at: CHECK_BIT_DATA     43 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/check_bit_data.pro
%                      OUT_TRACK         317 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/out_track.pro
%                      $MAIN$         

Can you explain what generates this error?  Note that the invalid pixel, line values appear to point to a location outside of the map limits.  The mapped files have dimensions 327x167.  The same map parameter file and same station location file are used in every iteration of the script.  I guess I could just delete the offending input file, but I'd like to understand what is happening if I've made some error in coding that causes this.

Thanks, Barry
By blesht Date 2012-07-30 17:52
Update - I deleted the original file that generated the error and tried again.  I encountered a different (non fatal error) and then the fatal error occurred again with a different file.  Here is the output.  Clearly, I need to either find the source of the error (if its my coding) and correct it, or add a trap of some sort - if this is possible.  Suggestions?    Thanks, Barry

/Volumes/3TBDrive/SeaWiFS/L2/Ontario/1997/S1997299171820.L2.x.hdf         247
grp_name=Geophysical Data
Getting navigation data from HDF file...
Getting special lat/lon from HDF file...
Getting - "Rrs_443" data from HDF file...
Getting - "Rrs_490" data from HDF file...
Getting - "Rrs_510" data from HDF file...
Getting - "Rrs_555" data from HDF file...
Getting - "l2_flags" data from HDF file...
hereto
SeaDAS Projection -          128 out of          167 lines processed
SeaDAS Projection -          167 out of          167 lines processed
PAUTOINCR: ERROR: DATAMM range is 0: [0.00000,0.00000]
MINMAXI:       0.00000      0.00000
SDS_PAUTOVEC: Error for range of MINMAXI to equal 0.
CBAR: Error.  Increment is LE zero. Infinite loop will result.
PAUTOINCR: ERROR: DATAMM range is 0: [0.00000,0.00000]
MINMAXI:       0.00000      0.00000
SDS_PAUTOVEC: Error for range of MINMAXI to equal 0.
CBAR: Error.  Increment is LE zero. Infinite loop will result.
/Volumes/3TBDrive/SeaWiFS/L2/Ontario/1997/S1997300180255.L2.x.hdf         275
grp_name=Geophysical Data
Getting navigation data from HDF file...
Getting special lat/lon from HDF file...
Getting - "Rrs_443" data from HDF file...
Getting - "Rrs_490" data from HDF file...
Getting - "Rrs_510" data from HDF file...
Getting - "Rrs_555" data from HDF file...
Getting - "l2_flags" data from HDF file...
hereto
SeaDAS Projection -          128 out of          167 lines processed
SeaDAS Projection -          167 out of          167 lines processed
SDP_BAND_PXVAL : Invalid pixel, line values :       101.000      171.000
% Specified offset to array is out of range: PXRAW.
% Execution halted at: CHECK_BIT_DATA     43 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/check_bit_data.pro
%                      OUT_TRACK         317 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/out_track.pro
%                      $MAIN$         
% CLOSE: Variable is undefined: LUN.
% Execution halted at: CHECK_BIT_DATA     43 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/check_bit_data.pro
%                      OUT_TRACK         317 /Volumes/1TBSATDATA/sw/seadas6.4/idl_lib/out_track.pro
%                      $MAIN$         
By blesht Date 2012-07-30 19:36
Further update - Sorry to have bothered you with this.  It turns out to have been a simple coding error on my part.  I was specifying the wrong band to the out_track procedure.  The problem is resolved.

Barry
Previous Next Up Topic SeaDAS / SeaDAS 6.x - General Questions / "Invalid pixel" error from out_track? (1951 hits)



Responsible NASA Official: Gene C. Feldman
Curator: OceanColor Webmaster
Authorized by: Gene C. Feldman
Updated: 27 November 2007
Privacy Policy and Important Notices NASA logo