Opened 17 years ago
Closed 17 years ago
#73 closed bug (fixed)
Specim sync errors
Reported by: | mggr | Owned by: | mggr |
---|---|---|---|
Priority: | immediate | Milestone: | |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description
Many 2007 flight lines have problems with navigation sync (ie. they don't sync!). This appears to be due to missing sync messages in the .nav file, or a totally missing .nav file. A typical error looks like:
-------------------------------------------------------------------------- azimport -- ver: 2.2.10 May 7 2007 (C) Azimuth Systems UK 1996, 2007 File template for Specim sync is: hawk/SWIRsh2007130#.nav Site time limits - day: 130 start: 94341 end: 94609 date: 10 05 2007 jday: 130 utc2gps: 14.0 NAV vgroup exists - updating Specim navigation sync details from image file header..... image lines: 2901 approximate sync time: 35021.46880 (gps SoD) frame inc: 0.05000 secs sensor: Hawk frame rate: 20.00 fps no. of frames to correct for: 3.00 sync time: 35021.5 is NOT on Applanix POSATT file: hawk/SWIRsh2007130a-1.nav start: 35182.8 end: 35403.5 sync time: 35021.5 is NOT on Applanix POSATT file: hawk/SWIRsh2007130a-2.nav start: 35421.1 end: 35565.1 sync time: 35021.5 is NOT on Applanix POSATT file: hawk/SWIRsh2007130a-3.nav start: 35752.3 end: 35869.1 sync time: 35021.5 is NOT on Applanix POSATT file: hawk/SWIRsh2007130a-4.nav start: 36085.1 end: 36243.4 ** NO Specim SYNC found after checking all files ** check file template and directory contents - no data saved
A procedure to correct for this is outlined in the specim processing guide but appears only to apply to azspec 1.1.3. We have azspec 1.1.2.
Change History (3)
comment:1 Changed 17 years ago by mggr
comment:2 Changed 17 years ago by mggr
Asked again ~Nov 20 when Bill asked what if anything was currently delaying us - he's probably working on the calibration issue currently.
comment:3 Changed 17 years ago by mggr
- Resolution set to fixed
- Status changed from new to closed
Fixed by info from Bill in Dec 2007. The option was renamed to hide it - now partially documented in Processing/Flow/azspec. Procedure is otherwise as described in azspec processing supplement.
Note: See
TracTickets for help on using
tickets.
Asked Bill for azspec 1.1.3 on 20/Sept.
Asked again in a phone conversation a week or so later (date not recorded).
In both instances, he was sorting out IPY data and his tax return :)
Asked again on 10/Oct, just before he went on holiday.