Version 11 (modified by mggr, 12 years ago) (diff)

Updates for 2012

Jobs to do before a new flight season starts

Operational manager should ensure all of these actions are completed prior to starting processing a new flight season.

ARSF-DAN software / configuration updates

This section lists all the necessary adjustments that must be made to ensure processing operates correctly.

Update or create:

  1. lever arm file
    • ~arsf/usr/share/leverarm_values.csv
    • Source: survey + ARSF-DAN calculation (see below)
  2. boresight file
  3. hyperspectral calibration files
    • ~arsf/usr/share/calibration_table.csv
    • ~arsf/calibration/YEAR/{eagle|hawk}/
    • Source: Specim or FSF/ARSF radiometric + wavelength calibration
    • Ensure these get sent to Phil at Ops
      • Further ensure that the wls files on the instruments are updated and the old ones on the instruments destroyed beyond recovery.
  4. hyperspectral sample scripts
    • ~arsf/sample_scripts/YEAR
    • Source: ARSF-DAN
  5. LIDAR intensity-based range correction file
    • ~arsf/usr/share/*IBRC* ?
    • ~arsf/calibration/lidar/YYYYMMDD
    • Source: provided by Leica each year
  6. LIDAR .reg file
    • ~arsf/calibration/lidar/YYYYMMDD
    • Source: made by ARSF-DAN following LIDAR boresight flight
  7. RCD calibration files
    • ~arsf/calibration/YEAR/rcd
    • ~arsf/usr/share/camera_parameters.csv
    • Source: provided by Leica each year
  8. Data hierarchy:
    • create arsf/YEAR and subdirs
  9. Delivery templates + letters (hyperspectral, camera, lidar)
    • ~arsf/arsf_data/YEAR/delivery_templates/....
    • update READMEs, etc
  10. Create and update data quality report for new year

Metadata

  1. Acquire application forms, store in ~arsf/arsf_data/YEAR/Applications
    • Source: ARSF SC - ask Steve for copies
  2. Acquire alpha gradings, store on Projects pages

Lever arms

If required, perform a survey of the positions of the instruments relative to the GPS antenna. We need sufficient information to compute the positions of:

  • the GPS antenna(s)
  • the LIDAR scanner (a measurement to the reference point on the case is sufficient)
  • the RCD camera (a measurement to the reference point on the case is sufficient)
  • Eagle
  • Hawk
  • TABI, CASI or any other imaging instrument that is installed
  • IMUs (Liteon and Honeywell)

In all cases, a measurement to a suitable reference point on the casing of the instrument, plus an engineering diagram of the instrument, is sufficient. We have these diagrams for the Specim and Leica instruments.

These values should be recorded at:

Hyperspectral

Boresight calibration

(explanation + insert link to boresight doc here)

Results should be recorded at Processing/BoresightCalibration and ~arsf/usr/share/boresight_values.csv

Radiometric and spectral calibration

There should have been one of these prior to the season starting. It must determine the spectral calibration of the instruments (what wavelength maps to what band) and the radiometric calibration (what gain to apply to map DN to radiance).

  1. Ensure the wavelength files on the Specim are updated to the current season and the old ones are destroyed.

LIDAR

Boresight calibration

Ideally we should use the Gloucester city calibration area as it has much more vertical relief. However, at the time of writing (2011), the area is not yet fully ready. Instead, we can use the Little Rissington site for the time being.

Scan encoder

The scan encoder measures the angle the mirror is at. At the start of the season, we should check the "centre/nadir" position is unchanged.

The procedure to check the scan encoder:

  • Start up the system on the ground (no GPS or installation required)
  • Run BIT mode
  • Turn off 'Position In' switch on the front panel
  • This will snap the mirror to the centre
  • Then read F4's tick column,it should show the real scan offset and it should be within ± 500 ticks from the -10800 value
  • Don't forget to switch on 'Position In' when you finish testing