Data Set Overview
  =================
    A Range (distance) file contains 1 band of 32-bit floating point
    numbers. The pixels in a Range image represent Cartesian distances
    from a reference point (defined by the RANGE_ORIGIN_VECTOR keyword
    in the PDS label) to the XYZ position of each pixel. This reference
    point is normally the camera position as defined by the C point of
    the camera model. A Range image is derived from an XYZ image and
    shares the same pixel geometry and XYZ coordinate system. As with
    XYZ images, range images can contain holes, defined by
    MISSING_CONSTANT. For Phoenix, this value is 0.0.

    More information is found in ALEXANDERETAL2008, BOSETAL2007, and
    KELLERETAL2008.

  Processing
  ==========
    Phoenix RAC RDRs are considered Level 3 (Calibrated Data equivalent 
    to NASA Level 1-A), Level 4 (Resampled Data equivalent to NASA Level 
    1-B), or Level 5 (Derived Data equivalent to NASA Level 1-C, 2 or 3). 
    The RDRs are to be reconstructed from Level 2 edited data, and are 
    to be assembled into complete images that may include radiometric 
    and/or geometric correction.

    Phoenix RAC instrument EDRs and RDRs will be generated by JPL's 
    Multimission Instrument Processing Laboratory (MIPL) as part of the 
    OPGS subsystem of the Phoenix GDS. RDRs will also be generated by 
    the RAC science instrument team at the SOC facility at the 
    University of Arizona, as well as at its home institution, Texas 
    A&M.

    RDR data products will be generated by, but not limited to, MIPL 
    using the Mars Suite of VICAR image processing software at JPL, and 
    the RAC science instrument team using TAMCAL and RACCAL software at 
    the SOC facility at the University of Arizona and at the team's home 
    institution at Texas A&M Univerisity. The RDRs produced will be 
    'processed' data. The input will be one or more Camera EDR or RDR 
    data products and the output will be formatted according to the data 
    product SIS [ALEXANDERETAL2008]. Additional meta-data may be added by
    the software to the PDS label.

  Data
  ====
    RDR products generated by MIPL will have a VICAR label wrapped by a
    PDS label, and their structure can include the optional EOL label
    after the binary data. RDR products not generated by MIPL may
    contain only a PDS label. Or, RDR products conforming to a standard
    other than PDS, such as JPEG compressed or certain Terrain products,
    are acceptable without a PDS header during mission operations, but
    may not be archivable.

    The RDR data product is comprised of radiometrically decalibrated
    and/or camera model corrected and/or geometrically altered versions
    of the raw camera data, in both single and multi-frame (mosaic)
    form. Most RDR data products will have PDS labels, or if generated
    by MIPL (OPGS), dual PDS/VICAR labels. Non-labeled RDRs include JPEG
    compressed products and the Terrain products.

  Software
  ========
    The MIPL Mars Program Suite was used to generate these RDRs.

  Media/Format
  ============
    The data set will initially be delivered and kept online.  Upon
    Mission completion, the RAC Operations RDRs will be delivered to PDS 
    on DVD.

NULL