Using SmartDrone's Pulse Desktop Processor
      Back to home
      1. Knowledge Base
      2. Using SmartDrone's Pulse Desktop Processor

      How to validate your Discovery 2 data

      A formal process for flying a test mission and validating the accuracy and performance of your Discovery 2 drone after each flight.

      On Landing Check All Files Present

      The following items should be present after each flight - make it a habit to check for all of these files before leaving the field. Missing files can occur when we don't give the drone a full 2-3 minutes after power on, and can also be bugs or corrupted missions that need to be reported to SmartDrone.

      1. Collect data and confirm all file types are present after each mission. Desired files are:
        1. Folder with date and time label matching drone time zone
        2. Folders Present: Images, Raw, Logs
          1. File Present: Processor.exe
        3. Raw Contents:
          1. .boresight file
          2. .meta file
          3. Two .dat files LiDAR and lidar_dual
          4. .t04 file
        4. Logs Contents
          1. A and B log
        5. Images
          1. Multiple Photos and camera.json text file

      Test Field or Project Validation Procedures

      1. Setup base station on known OPUS position.
        1. Take 15-30 check shots throughout the test field and export them as a text file. 
        1. Discovery 2 LiDAR/RGB - perform mission collecting images and LiDAR for quality comparison
        2. Discovery 2 LiDAR ONLY - perform mission with photos turned off by increasing photo spacing to 999Plane drone flight over your Accuracy Field - perform 2-3 missions over the same area.

      Processing Data and Evaluating GNSS Reports

      We compare data against check shots to confirm elevations and ensure we are controlling for any drone performance issues, such as vegetation which may be difficult to penetrate. In addition, we review GNSS satellite connection and noise reports to ensure the internal positioning systems are functioning.

      1. Process the data with your check shots and base file
      2. Accuracy report desired values:
        1. Average offset < .2’
        2. Std deviation < .25’
          image
      3. GNSS report desired values:
        1. Page 4, L1 Satellite Lock/Elevation, look for no breaks in the lines - in particular finding breaks across multiple lines that happen vertically together
          image (1)
      4. Page 5, L1 SNR, don’t want any dips below 30 in the left hand bar
        1. Usually you see values as high as 45-50 at the peaks
        2. Don’t want to see big dips that last below 30 for all lines - a single random line dipping may not be critical
          image (2)