Changes between Version 6 and Version 7 of Processing/KnownProblems


Ignore:
Timestamp:
Nov 20, 2007 12:47:09 PM (12 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/KnownProblems

    v6 v7  
    2020This should then process through to level 3, though you may need to correct for navigation timing.
    2121
     22== Errors in aznav interpolation stage ==
     23
     24These can occur (particularly with CASI) when there is a large offset between the site time limits and the ones on the file.  azimport will pull in the section of the navigation data according to the file limits and the actual required navigation may be outside this range.  A typical error looks something like:
     25{{{
     26*** DPspline2D no returned vectors  spl_err: 1  slpp 1: -2.4420659 n: 1.9638544
     27  in  len: 82201   time[0]: 42062.001400  [82200]: 42472.997200
     28  out len: 11667   time[0]: 42603.547100  [11666]: 43011.876100
     29  in time vector:
     30 42062.001400 ...
     31
     32  out time vector:
     33 42603.547100 ...
     34
     35** end of DPspline2D error print
     36
     37** lat+lng interpolation, vectors incomplete
     38** should be from index: 0 to index: 11666
     39** valid data only from idex: 0 to index: 0
     40}}}
     41
     42To fix this, forcibly specify the time range you want to insert navigation data for with `azimport -t JJJ HHMMSS HHMMSS ...` (JJJ = Julian date, then the start and end times from the logsheet, plus a few minutes), e.g. `azimport -t 261 110000 111000 ...` for day 261 11:00:00 to 11:10:00.
     43
    2244---------------------
    2345