Changes between Version 6 and Version 7 of Sensors/LeicaLIDAR/MikesNotes


Ignore:
Timestamp:
Aug 26, 2008 3:38:47 PM (11 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Sensors/LeicaLIDAR/MikesNotes

    v6 v7  
    3333
    3434Consider reflectivity of surface - lighter surfaces need less laser power (too high a power means overflows on the reflection, though AGC should deal with this for the most part..).
     35
     36Recommended to do a figure 8 loop at the start and end of the data acquisitions to make the IMU happy.  Need one at the end for reverse navigation processing.
    3537
    3638== Overall system design and comments of note ==
     
    106108
    107109Lever arm measurements:
    108  * IMU -> sensor head
     110 * IMU -> sensor head (centre of mirror?)
    109111   * Measured in the factory and provided by Leica
    110112 * IMU -> measurement point [front left corner of the casing]
     
    114116
    115117Intensity Based Range Correction (IBRC).
    116  * A correction based on the reflectivity of the target object ("reflections are slower on darker objects"?).
     118 * A range correction based on the reflectivity of the target object ("reflections are slower on darker objects"?  perhaps this is more that a lower intensity return may take longer to be detected - ie. takes longer for enough photons to come back to exceed the detection threshold).
    117119 * Measured in factory and provided by Leica.
    118120
     121= Processing =
     122== Extraction ==
     123
     124Use IPAS Pro to extract GPS, IMU and laser data from the raw files.
     125 * probably worth having the real time navigation info (doesn't add a lot of processing time)
     126 * during extraction, view the listing and verify the lever arms are correct (IMU one should never change).
     127 * look out for data gaps (listed in log)
     128
     129== Navigation processing ==
     130
     131See other pages on navigation processing as they cover this already.