<?xml version="1.0" encoding="UTF-8"?>
<?xml-model 
    href="https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1O00.sch"
    schematypens="http://purl.oclc.org/dsdl/schematron"?>

<Ingest_LDD 
    xmlns="http://pds.nasa.gov/pds4/pds/v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:pds="http://pds.nasa.gov/pds4/pds/v1"
    xsi:schemaLocation="http://pds.nasa.gov/pds4/pds/v1
                        http://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1O00.xsd">
    <name>MRO</name>
    <ldd_version_id>1.4.0.0</ldd_version_id>
    <dictionary_type>Mission</dictionary_type>
    <full_name>Jennifer Ward</full_name>
    <steward_id>geo</steward_id>
    <namespace_id>mro</namespace_id>
    <comment>
        The MRO dictionary contains classes that describe aspects of the 
        Mars Reconnaissance Orbiter mission and related instruments.
        
        MRO version 1.4.0.0
        PDS Build 1.19.0.0, 1.20.0.0, 1.21.0.0, 1.22.0.0, 1.23.0.0, 1.24.0.0
        LDDTool version 15.2.4
        
        Built with lddtool -plJ PDS4_MRO_IngestLDD.xml
        
        2022-09-27 JGW. Revised SCLK pattern to allow between 3 and 6 fractional digits.
        Added release_id.
        
        2022-09-29 JGW. Added SHARAD_Parameters class.
        Reorganized attribute definitions.
        
        2022-12-02 DVP. Added CRISM_ATO_Parameters class.
        
        2022-12-06 DVP. Bumped to version 1.1.0.0 because of addition of class.
	
	    2022-12-22 PG (pgeissler@usgs.gov) added HiRISE parameters, bumped to 1.2.0.0
	            
        2023-03-23 PG (pgeissler@usgs.gov) added HiRISE RDR class

	    2023-08-16 DVP. Modifications to some parameters of CRISM_ATO_Parameters class
	    following urn:nasa:pds:crism_ato_s_iof_lml peer review; bumped to 1.2.1.0

        2023-08-31 PG (pgeissler@usgs.gov) added observation_rationale attribute for HiRISE, 
        bump to 1.2.2.0
        
        2024-01-09 JGW. Added SHARAD_Observation_Parameters class, bump to 1.3.0.0
        
        2024-02-27 PG fixes to HiRISE, 1.3.1.0
        
        2024-09-16 JGW. Revised SCLK pattern to allow between 1 and 6 fractional digits, 1.3.2.0
        
        2025-12-16 TMH. Added BADCAL enumeration to special_processing_flag_* for HiRISE, 1.3.3.0
        
        2025-06-27 JGW. Added CRISM TRDR parameters. Added CRISM VRDR product types, 1.4.0.0.
        
    </comment>
    <last_modification_date_time>2025-06-27</last_modification_date_time>

<!--Hierarchy of classes and attributes 
    mro:MRO_Parameters
        mro.HiRISE_Time_Parameters
            [Defined below]
        mro.HiRISE_Instrument_Setting_Parameters
            [Defined below]
        mro.HiRISE_Temperature_Parameters
            [Defined below]
        mro.HiRISE_Power_Parameters
            [Defined below]
        mro.HiRISE_RDR_Parameters
            [Defined below]	    
        mro:CRISM_Parameters
            [Defined below]
        mro:SHARAD_Parameters
            [Defined below]
        mro:CRISM_ATO_Parameters
            [Defined below]

-->               
    <!-- Begin definitions of MRO Mission Dictionary attributes -->
    <!-- Attributes for the MRO_Parameters class, in alphabetical order:
        
        line_prefix_bytes
        line_suffix_bytes
        mission_phase_name
        observation_rationale
	    orbit_number
	    producer_institution_name
	    product_type
	    product_version_id
	    release_id	    
	    spacecraft_clock_count_partition
	    spacecraft_clock_start_count
	    spacecraft_clock_stop_count
 
    --> 
    
    <DD_Attribute> <name>mission_phase_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.mission_phase_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The mission_phase_name attribute provides the mission-defined name of 
            a time period within the mission.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>Launch</value>
                <value_meaning>2005-08-12 to 2005-08-12</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Cruise</value>
                <value_meaning>2005-08-12 to 2006-01-10</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Approach and Orbit Insertion</value>
                <value_meaning>2006-01-10 to 2006-03-10</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Aerobraking</value>
                <value_meaning>2006-03-17 to 2006-11-07</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Primary Science</value>
                <value_meaning>2006-11-08 to 2008-11-08</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Science</value>
                <value_meaning>2008-11-09 to 2010-09-30</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Mission 1</value>
                <value_meaning>2010-10-01 to 2012-09-30</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Mission 2</value>
                <value_meaning>2012-10-01 to 2014-09-30</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Mission 3</value>
                <value_meaning>2014-10-01 to 2016-09-30</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Mission 4</value>
                <value_meaning>2016-10-01 to 2019-09-30</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Mission 5</value>
                <value_meaning>2019-10-01 to 2022-09-30</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Extended Mission 6</value>
                <value_meaning>2022-10-01 to 2025-09-30</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> 
        <name>observation_rationale</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.observation_rationale</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The observation_rationale attribute identifies the name of the specific 
            feature on Mars that was targeted by the observation. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>orbit_number</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.orbit_number</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The orbit_number attribute identifies the orbit number when the observation was taken.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_NonNegative_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>producer_institution_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.producer_institution_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The producer_institution_name attribute identifies the name of the institution that created the data product. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>product_type</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.product_type</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The product_type attribute identifies the type of data product.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>EDR</value>
                <value_meaning>Experiment Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>RDR</value>
                <value_meaning>Reduced Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CDR</value>
                <value_meaning>Calibrated Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>DDR</value>
                <value_meaning>Derived Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MTRDR</value>
                <value_meaning>Map-Projected Targeted Reduced Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TER</value>
                <value_meaning>Targeted Empirical Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TRDR</value>
                <value_meaning>Targeted Reduced Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>LDR</value>
                <value_meaning>Limb Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MRDR</value>
                <value_meaning>Multispectral Reduced Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MTRDR_Browse</value>
                <value_meaning>Map-Projected Targeted Reduced Data Record - Browse</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MTRDR_Extras</value>
                <value_meaning>Map-Projected Targeted Reduced Data Record - Extras</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TER_Browse</value>
                <value_meaning>Targeted Empirical Record - Browse</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TER_Extras</value>
                <value_meaning>Targeted Empirical Record - Extras</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TRDR_Extras</value>
                <value_meaning>Targeted Reduced Data Record - Extras</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TRDR_Browse</value>
                <value_meaning>Targeted Reduced Data Record - Browse</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>VRDR</value>
                <value_meaning>VNIR Hyperspectral Reduced Data Record</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>VRDR_Browse</value>
                <value_meaning>VNIR Hyperspectral Reduced Data Record - Browse</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>DTM</value>
                <value_meaning>Digital Terrain Model</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>ORTHOIMAGE</value>
                <value_meaning>Image orthorectified to a digital terrain model</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>product_version_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.product_version_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The product_version_id element identifies the version of an individual data product.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>release_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.release_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Susan Slavney</submitter_name>
        <definition>release_id is the identifier of a scheduled release of MRO data from PDS. The
            first MRO data release has release_number "0001". The release_number for a given product is always the
            first release in which it appears, and does not change if the product is revised
            later.</definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <minimum_characters>1</minimum_characters>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>spacecraft_clock_count_partition</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spacecraft_clock_count_partition</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The spacecraft_clock_count_partition attribute indicates the clock
            partition active for the spacecraft_clock_start_count and
            spacecraft_clock_stop_count attributes.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_NonNegative_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>        
    <DD_Attribute> <name>spacecraft_clock_start_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spacecraft_clock_start_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The spacecraft_clock_start_count attribute provides the value 
            of the spacecraft clock at the beginning of a time period of 
            interest.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <pattern>([0-9]{1,2}/)?[0-9]{1,10}(:[0-9]{1,6})?</pattern>
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute> <name>spacecraft_clock_stop_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spacecraft_clock_stop_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The spacecraft_clock_stop_count attribute provides the value of the spacecraft 
            clock at the end of a time period of interest.
        </definition>    
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <pattern>([0-9]{1,2}/)?[0-9]{1,10}(:[0-9]{1,6})?</pattern>
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute> 
        <name>line_prefix_bytes</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.line_prefix_bytes</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The line prefix bytes attribute reports the number of bytes that precede the 
            observational data for each line of a HiRISE or CTX image. For HiRISE, the prefix 
            includes 6 bytes of line identification information and the values of 12 buffer pixels,
            which contain the value of empty pixels after going through the instrument electronics.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_NonNegative_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>        
    <DD_Attribute> 
        <name>line_suffix_bytes</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.line_suffix_bytes</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The line suffix bytes attribute reports the number of bytes that follow the 
            observational data for each line of a HiRISE or CTX image. For HiRISE, the suffix 
            contains 16 dark reference pixel values produced by masked detectors.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_NonNegative_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>   
    
    <!-- End attribute definitions for the MRO_Parameters class. -->
    
    <!-- Attribute definitions for the CRISM_Parameters class, in alphabetical order:
    
        activity_id
        band_name
        band_sequence_number
	    detector_temperature
	    exposure_parameter
	    fpe_temperature
	    fram_stat_iqr_conf_lvl
	    fram_stat_median_box_width
	    fram_stat_median_conf_lvl
	    fram_stat_min_deviation 
	    frame_rate	     	    
	    hdf_software_name
	    hdf_software_version_id
	    if_max_value
	    if_min_value
	    ikf_confidence_level_r1
	    ikf_confidence_level_r2
	    ikf_kernel_size_x_r1
	    ikf_kernel_size_x_r2
	    ikf_kernel_size_y_r1
	    ikf_kernel_size_y_r2
	    ikf_kernel_size_z_r1
	    ikf_kernel_size_z_r2
	    ikf_model_order_x_r1
	    ikf_model_order_x_r2
	    ikf_model_order_y_r1
	    ikf_model_order_y_r2
	    ikf_model_order_z_r1
	    ikf_model_order_z_r2
	    ikf_num_regions
	    ikf_start_channel_r1
	    ikf_start_channel_r2
	    ikf_stop_channel_r1
	    ikf_stop_channel_r2
	    ikf_weighting_stddev_r1
	    ikf_weighting_stddev_r2
	    instrument_pointing_mode
	    inv_lookup_table_file_name
	    log_xform_neg_clip_value
        observation_id
	    observation_number
	    observation_type
	    optical_bench_temperature
	    pixel_proc_file_name
	    refz_median_box_width
	    refz_smooth_box_width
	    rsc_ref_xy_median_width
	    rsc_ref_xy_smooth_width
	    rsc_ref_yz_median_width
	    rsc_ref_yz_smooth_width
	    rsc_ratio_xy_median_width
	    rsc_ratio_xy_smooth_width
	    rsc_res_xy_ply_order
	    rsc_res_xy_ply_extnd_width
	    sampling_mode_id
	    scaling_factor
	    scan_mode_id
	    sensor_id
	    spectrometer_housing_temperature
	    sphere_temperature
	    trace_max_value
	    trace_min_value
	    value_offset
	    wavelength_file_name
	    wavelength_filter
	    
    -->

    <DD_Attribute> <name>activity_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.activity_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The activity_id attribute describes the type of measurement contained in 
            a CRISM EDR or other data product, and provides indication of how the 
            observation is commanded. The format of the value is AC### where AC is a 
            2-letter designation of the type of measurement made, and ### is a 
            3-numeral designation of the instrument command macro that was executed 
            to acquire the data. Macro numbers are in the range 0-255.
            
            For EDRs, BI is measurement of detector bias, DF is a measurement of
            background including dark current and thermal background, LP is
            measurement of a focal plane lamp, SP is measurement of the internal
            integrating sphere, and SC is measurement of an external scene. TP
            indicates that the EDR contains any test pattern produced by instrument
            electronics. T1 through T7 specify the test pattern, test pattern 1
            through test pattern 7. UN indicates that the EDR contains data in
            which housekeeping does not match the commanded instrument
            configuration.
            
            For an RDR, RA indicates that the file contains values in units of
            radiance (W m^-2 nm^-1 sr^-1). IF indicates that the file contains
            values in units of I/F, or radiance divided by solar flux scaled for
            heliocentric distance.  AL indicates that the file contains values as
            estimated Labert albedo, which is I/F corrected for cosine of incidence
            angle and for atmospheric and thermal effects.  SU indicates that the
            files contains summary parameters, unitless values derived from Lambert
            albedo.
            
            For an RDR or a DDR, DE indicates that the files contains derived values
            related to observation geometry or independently characterized
            properties of the scene.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>band_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.band_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Susan Slavney</submitter_name>
        <definition>Identifies the name of the CRISM band associated with the specific scaling and
            offset parameters used in a CRISM browse product.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>band_sequence_number</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.band_sequence_number</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Susan Slavney</submitter_name>
        <definition>Defines the order of the CRISM bands along the Axis_Array when axis_name is band.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>1</minimum_value>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>detector_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.detector_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The detector_temperature attribute provides the temperature of the
            CRISM IR detector (if sensor_id = 'L'), or the VNIR detector (if
            sensor_id = 'S'). On each detector there are two temperature
            sensors. The primary source of IR detector temperature is IR temperature
            sensor 1 (column 50 in the EDR list file). The backup source of IR
            detector temperature is IR temperature sensor 2 (column 51 in the EDR
            list file). The primary source of VNIR detector temperature is VNIR
            temperature sensor 2 (column 65 in the EDR list file). The backup source
            of VNIR detector temperature is VNIR temperature sensor 1 (column 64 in
            the EDR list file).
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>K</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>exposure_parameter</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.exposure_parameter</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The exposure_parameter attribute identifies the value supplied to the CRISM 
            instrument to command the exposure time. At a given frame rate identified in 
            frame_rate, there are 480 possible exposure times ranging from 1 to 480. An 
            exposure parameter of 480 yields an exposure time equal to the inverse of the 
            frame rate. An exposure time parameter of 1 yields an exposure time 1/480 as 
            large. For example, at a frame rate of 3.75 Hz, an exposure time parameter of 
            480 yields an exposure time of 0.26667 sec, whereas an exposure time parameter 
            of 1 yields and exposure time of 0.00056 sec. This parameter is included 
            independently of the exposure time itself because some of the Calibration Data 
            Records (CDRs) are applicable to data taken at a particular exposure parameter.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>1</minimum_value>
            <maximum_value>480</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>fpe_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fpe_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The fpe_temperature attribute provides the temperature of the
            HiRISE or CRISM instrument's Focal Plane Electronics in degrees
            Celsius. For HiRISE, see Figure 2.3, MRO HiRISE EDR SIS, REFKEYID
            JPLD-32004. For CRISM, the value refers to the focal plane
            electronics board mounted in the base of the gimbal. The values
            represents IR focal plane electronics if sensor_id = 'L', and
            to the VNIR focal plane electronics if sensor_id = 'S'. The
            source of CRISM IR focal plane electronics temperature is column
            60 in the EDR list file. The source of VNIR focal plane
            electronics temperature is column 71 in the EDR list file.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>K</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>fram_stat_iqr_conf_lvl</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fram_stat_iqr_conf_lvl</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The fram_stat_iqr_conf_lvl attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the confidence level parameter 
            associated with the Grubb's Test used for outlier detection of attributes of the normalized median profile 
            of the frame interquartile range in the detection of bad frames during the preprocessing steps. Typical 
            values are near 0.95.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>1</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>fram_stat_median_box_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fram_stat_median_box_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The fram_stat_median_box_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a median 
            filter used on the frame median profile in the computation of bad frames during preprocessing steps.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>fram_stat_median_conf_lvl</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fram_stat_median_conf_lvl</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The fram_stat_median_conf_lvl attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the confidence level parameter 
            associated with the Grubb's Test used for outlier detection of attributes of the normalized median frame 
            profile in the detection of bad frames during the preprocessing steps. Typical values are near 0.95.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>1</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>fram_stat_min_deviation</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fram_stat_min_deviation</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The fram_stat_min_deviation attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the minimum deviation from 
            the mean of an attribute of the normalized frame median profile necessary to be classified as a bad frame 
            during the preprocessing steps.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>1</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>frame_rate</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.frame_rate</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The frame_rate attribute identifies the rate at which frames of data in a CRISM EDR were returned. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Frame_Rate</unit_of_measure_type>
            <specified_unit_id>Hz</specified_unit_id>
            <DD_Permissible_Value>
                <value>1.0</value>
                <value_meaning>The frame rate is 1.0 Hz.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>3.75</value>
                <value_meaning>The frame rate is 3.75 Hz.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>5.0</value>
                <value_meaning>The frame rate is 5.0 Hz.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>15.0</value>
                <value_meaning>The frame rate is 15.0 Hz.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>30.0</value>
                <value_meaning>The frame rate is 30.0 Hz.</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>hdf_software_version_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.hdf_software_version_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The hdf_software_version_id attribute indicates the version of the software used by the CRISM hyperspectral data 
            filter application. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>hdf_software_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.hdf_software_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The hdf_software_name attribute provides the name of the CRISM hyperspectral data filter software used to 
            process radiance TRDR data into I/F. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>if_max_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.if_max_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The if_max_value attribute is one of the control parameters for the CRISM hyperspectral data filtering 
            application used to convert TRR3 radiance data to I/F and indicates the maximum valid value in units of I/F.
            Values outside of the valid range of I/F values are ignored during preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>if_min_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.if_min_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The if_min_value attribute is one of the control parameters for the CRISM hyperspectral data filtering 
            application used to convert TRR3 radiance data to I/F and indicates the minimum valid value in units of I/F.
            Values outside of the valid range of I/F values are ignored during preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_confidence_level_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_confidence_level_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_confidence_level_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the confidence level parameter 
            associated with the Grubb's Test used for outlier detection of attributes of the model residuals in the 
            Iterative Kernel Filter procedure. Spectral region 1. Typical values are near 0.95. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>1</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_confidence_level_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_confidence_level_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_confidence_level_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the confidence level parameter 
            associated with the Grubb's Test used for outlier detection of attributes of the model residuals in the 
            Iterative Kernel Filter procedure. Spectral region 2. Typical values are near 0.95. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>1</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_kernel_size_x_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_kernel_size_x_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_kernel_size_x_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the size of the kernel in the 
            X direction used in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_kernel_size_x_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_kernel_size_x_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_kernel_size_x_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the size of the kernel in the 
            X direction used in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_kernel_size_y_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_kernel_size_y_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_kernel_size_y_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the size of the kernel in the 
            Y direction used in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_kernel_size_y_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_kernel_size_y_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_kernel_size_y_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the size of the kernel in the 
            Y direction used in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_kernel_size_z_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_kernel_size_z_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_kernel_size_z_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the size of the kernel in the 
            Z direction used in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_kernel_size_z_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_kernel_size_z_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_kernel_size_z_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the size of the kernel in the 
            Z direction used in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_model_order_x_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_model_order_x_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_model_order_x_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the dimensionality of the 
            model in the X direction used in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_model_order_x_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_model_order_x_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_model_order_x_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the dimensionality of the 
            model in the X direction used in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_model_order_y_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_model_order_y_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_model_order_y_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the dimensionality of the 
            model in the Y direction used in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_model_order_y_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_model_order_y_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_model_order_y_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the dimensionality of the 
            model in the Y direction used in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_model_order_z_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_model_order_z_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_model_order_z_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the dimensionality of the
            model in the Z direction used in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_model_order_z_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_model_order_z_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_model_order_z_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the dimensionality of the
            model in the Z direction used in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_num_regions</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_num_regions</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_num_regions attribute is one of the control parameters for the CRISM hyperspectral data filtering 
            application used to convert TRR3 radiance data to I/F and indicates the number of spectral regions 
            identified for the application of the Iterative Kernel Filter procedure. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_start_channel_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_start_channel_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_start_channel_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the first channel number for 
            spectral region 1 of the Iterative Kernel Filter procedure. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>437</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_start_channel_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_start_channel_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_start_channel_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the first channel number for 
            spectral region 2 of the Iterative Kernel Filter procedure. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>437</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_stop_channel_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_stop_channel_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_stop_channel_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the last channel number for 
            spectral region 1 of the Iterative Kernel Filter procedure. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>437</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_stop_channel_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_stop_channel_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_stop_channel_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the last channel number for 
            spectral region 2 of the Iterative Kernel Filter procedure. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>437</maximum_value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_weighting_stddev_r1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_weighting_stddev_r1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_weighting_stddev_r1 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the weighting parameter for 
            the final model evaluation in the Iterative Kernel Filter procedure. Spectral region 1. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>ikf_weighting_stddev_r2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ikf_weighting_stddev_r2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The ikf_weighting_stddev_r2 attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the weighting parameter for 
            the final model evaluation in the Iterative Kernel Filter procedure. Spectral region 2. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>instrument_pointing_mode</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.instrument_pointing_mode</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The instrument_pointing_mode element identifies the pointing mode of the CRISM gimbal. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>FIXED POINTING</value>
                <value_meaning>The instrument remains at a single gimbal position while taking data. FIXED POINTING is the nominal mode for multispectral survey data.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>DYNAMIC POINTING</value>
                <value_meaning>The gimbal tracks a target and typically superimposes a very slow constant-rate scan. DYNAMIC POINTING is the nominal mode for targeted observations.</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>inv_lookup_table_file_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.inv_lookup_table_file_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The inv_lookup_table_file_name element identifies the name of the CRISM file that gives the 12-bit DN value 
            replacing each 8-bit DN value if lossy compression was performed (if compression_type=8_BIT). The inverse 
            lookup table file is a nine-column, 4095-row text file. Column 1 gives each 8-bit value, 0 through 255. 
            Columns 2 through 9 give the 12-bit values that replace them if lookup tables 0 through 7, respectively,
            were selected for data acquisition. Lookup tables are selected on a line by line basis. Which table is used 
            for each line is indicated in the pixel-processing descriptive file named in pixel_proc_file_name. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>log_xform_neg_clip_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.log_xform_neg_clip_value</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The log_xform_neg_clip_value attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the value used for any 
            negative I/F value in the log base 10 transform. This effectively represents the minimum possible pixel 
            value for the Iterative Kernel Filter procedure. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>observation_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.observation_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The observation_id attribute is a 8-byte hexadecimal integer uniquely identifying the observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>observation_number</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.observation_number</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The observation_number attribute gives the monotonically increasing ordinal counter of the EDRs generated 
            for a particular CRISM observation_id. CRISM generates several EDRs for a given observation_id.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>observation_type</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.observation_type</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The observation_type attribute identifies the general type of observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>FRT</value>
                <value_meaning>Full Resolution Targeted Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>HRL</value>
                <value_meaning>Half Resolution Long Targeted Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>HRS</value>
                <value_meaning>Half Resolution Short Targeted Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>FRS</value>
                <value_meaning>Full Resolution Short Targeted Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>ATO</value>
                <value_meaning>Along-track Oversampled Targeted Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>ATU</value>
                <value_meaning>Along-track Undersampled Targeted Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>EPF</value>
                <value_meaning>Atmospheric Survey Emission Phase Function</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>TOD</value>
                <value_meaning>Tracking Optical Depth Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>LMB</value>
                <value_meaning>Limb Scan Observation</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MSP</value>
                <value_meaning>Multispectral Survey, losslessly compressed</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>HSP</value>
                <value_meaning>Hyperspectral Survey, losslessly compressed</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>HSV</value>
                <value_meaning>Hyperspectral Survey, VNIR only, pixels 10x-binned</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MSV</value>
                <value_meaning>Hyperspectral Survey, VNIR only, pixels 5x-binned</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MSW</value>
                <value_meaning>Multispectral Window</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>FFC</value>
                <value_meaning>Flat Field Calibration</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CAL</value>
                <value_meaning>Radiometric Calibration</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>ICL</value>
                <value_meaning>Calibration source intercalibration</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>FUN</value>
                <value_meaning>Functional test</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>UNK</value>
                <value_meaning>No valid EDRs within observation that indicate class type</value_meaning>
            </DD_Permissible_Value>            
            <DD_Permissible_Value>
                <value>STO</value>
                <value_meaning>Star Observation</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>optical_bench_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.optical_bench_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The optical_bench_temperature attribute provides the temperature of the CRISM optical bench. It is a backup 
            to sphere_temperature for modeling the output radiance of the onboard integrating sphere as a function of 
            sphere temperature.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>K</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>pixel_proc_file_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.pixel_proc_file_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The pixel_proc_file_name attribute gives the name of the file that documents the CRISM onboard compression 
            options selected. Onboard compression converts a 14- bit DN with a value of 0-16383 to a 12-bit- 0-4095 
            value or 8-bit 0-255 value for downlink. Corrections are done on a line by line basis. The pixel processing 
            file is a 4- column, 480-row text file. The four attributes in each row are the row number, the gain 
            correction performed, the offset correction performed, and the 12 to 8 bit lookup table used if lossy 
            compression is performed. Both gain and offset corrections are always performed to convert 14-bit to 12-bit 
            values prior to downlink. First the offset is subtracted from the 14-bit value. Then the difference is 
            multiplied by the gain to shorten the result to a 12-bit value. If lossy compression is being performed 
            (if compression_type = 8_BIT), then the 12- to 8-bit lookup table value gives the table in the file named 
            by lookup_table_file_name that was used to convert the 12-bit value to an 8- bit value. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>refz_median_box_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.refz_median_box_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The refz_median_box_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a median 
            filter used in the spectral direction in the computation of the reference cube during the preprocessing 
            steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>refz_smooth_box_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.refz_smooth_box_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The refz_smooth_box_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a boxcar 
            smoothing filter used in the spectral direction in the computation of the reference cube during the 
            preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_ref_xy_median_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_ref_xy_median_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_ref_xy_median_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a median 
            filter used as part of the application of the ratio shift correction procedure in the XY direction while 
            computing the reference cube during the preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_ref_xy_smooth_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_ref_xy_smooth_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_ref_xy_smooth_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a boxcar 
            smoothing filter used as part of the application of the ratio shift correction procedure in the XY direction 
            while computing the reference cube during the preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_ref_yz_median_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_ref_yz_median_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_ref_yz_median_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a median 
            filter used as part of the application of the ratio shift correction procedure in the YZ direction while 
            computing the reference cube during the preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_ref_yz_smooth_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_ref_yz_smooth_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_ref_yz_smooth_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a boxcar 
            smoothing filter used as part of the application of the ratio shift correction procedure in the YZ direction 
            while computing the reference cube during the preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_ratio_xy_median_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_ratio_xy_median_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_ratio_xy_median_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a median 
            filter used as part of the application of the ratio shift correction procedure in the XY direction while 
            computing the ratio cube during the preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_ratio_xy_smooth_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_ratio_xy_smooth_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_ratio_xy_smooth_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the kernel size of a boxcar 
            smoothing filter used as part of the application of the ratio shift correction procedure in the XY direction 
            while computing the ratio cube during the preprocessing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_res_xy_ply_order</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_res_xy_ply_order</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_res_xy_ply_order attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the order of the polynomial 
            used to model low frequency content in the XY direction used as part of the application of the ratio shift 
            correction procedure while computing the resolve cube during the post processing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>rsc_res_xy_ply_extnd_width</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.rsc_res_xy_ply_extnd_width</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The rsc_res_xy_ply_extnd_width attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the number of pixels used to 
            extend the trend of the column profiles when computing the polynomial used to model low frequency content in 
            the XY direction used as part of the application of the ratio shift correction procedure while computing 
            the resolve cube during the post processing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>sampling_mode_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sampling_mode_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The sampling_mode_id attribute identifies the resolution mode of a wavelength or frequency channel. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>HYPERSPECTRAL</value>
                <value_meaning>Wavelength filter used returns contiguous rows.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>MULTISPECTRAL</value>
                <value_meaning>Wavelength filter used does not return contiguous rows.</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>scaling_factor</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.scaling_factor</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Susan Slavney</submitter_name>
        <definition>The scaling_factor attribute is the scaling factor to be applied to each stored value in order to 
            recover an original value. The observed value (Ov) is calculated from the stored value (Sv) thus: 
            Ov = (Sv * scaling_factor) + value_offset. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>scan_mode_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.scan_mode_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The scan_mode_id attribute identifies one of several internal rates for data acquisition by an 
            instrument. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>SHORT</value>
                <value_meaning>For full-resolution or half-resolution short central swath, or limb scan observation.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>LONG</value>
                <value_meaning>For half-resolution long central swath.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>EPF</value>
                <value_meaning>For EPF even if part of a different class of observation.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>N/A</value>
                <value_meaning>For targeted observations since 2012, when truncated central scans without EPF images were adopted.</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>sensor_id</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sensor_id</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The sensor_id attribute identifies the CRISM focal plane from which data in an EDR or RDR were returned; 
            S = short-wavelength or VNIR, L = long-wavelength or IR, J = joint where a data product is applicable to 
            either.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute> <name>spectrometer_housing_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spectrometer_housing_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The spectrometer_housing_temperature attribute gives the temperature of the CRISM spectrometer housing. 
            This is a backup to direct determination, using measurements with the shutter closed, of the thermal 
            background measured by the IR detector. The primary source of this temperature is a measurement digitized 
            by the VNIR focal plane electronics, column 58 in the EDR list file. The backup source of this temperature 
            is a measurement digitized by the IR focal plane electronics, column 69 in the EDR list file.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>K</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>   
    <DD_Attribute> <name>sphere_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sphere_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>
            The sphere_temperature attribute gives the temperature of the CRISM onboard integrating sphere. It is used 
            for modeling the output radiance of the sphere as a function of sphere temperature.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>K</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute> 
    <DD_Attribute> <name>trace_max_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.trace_max_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The trace_max_value attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the maximum valid value of a 
            ratio computed for the Ratio Shift Correction algorithm. Values outside of the valid range of ratio values 
            are ignored during this processing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>trace_min_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.trace_min_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The trace_min_value attribute is one of the control parameters for the CRISM hyperspectral data 
            filtering application used to convert TRR3 radiance data to I/F and indicates the minimum valid value of a 
            ratio computed for the Ratio Shift Correction algorithm. Values outside of the valid range of ratio values 
            are ignored during this processing steps. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>value_offset</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.value_offset</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Susan Slavney</submitter_name>
        <definition>The value_offset attribute is the offset to be applied to each stored value in order to recover an 
            original value. The observed value (Ov) is calculated from the stored value (Sv) thus: 
            Ov = (Sv * scaling_factor) + value_offset. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>wavelength_file_name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.wavelength_file_name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The wavelenth_file_name attribute identifies the name of the file that describes wavelength 
            sampling in a CRISM EDR, RDR, or CDR. There are two aspects to the wavelength sampling. One is the 
            wavelength of light falling on each attribute of the 480-row detector. The second is the selection of 
            which rows are included in downlink. For each detector there is a menu of four options; which option is 
            selected is given in wavelength_filter, which has a value of 0, 1, 2, or 3. For an EDR, the wavelength 
            file is a 5-column, 480-row text file. The five attributes in each row are the row number and a 0 or 1 
            for wavelength_filter 0, 1, 2 and 3, indicating if the row is included in the EDR when that option is 
            selected in wavelength_filter. For an RDR or CDR, the wavelength file is an image whose value at the 
            location of a detector attribute is the center wavelength of that attribute, in nanometers. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>wavelength_filter</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.wavelength_filter</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>GEO</submitter_name>
        <definition>The wavelength_filter attribute identifies which of four CRISM onboard menus of rows was 
            selected for downlink. The four choices are 0, 1, 2, or 3. Each filter is a vector of 480 0's or 1's, 
            one per row of the detector. 0 indicates that data are not saved; 1 indicates that data are saved. The 
            values in the four vectors are in the file named by wavelength_file_name. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <DD_Permissible_Value>
                <value>0</value>
                <value_meaning>Menu 0.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>1</value>
                <value_meaning>Menu 1.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>2</value>
                <value_meaning>Menu 2.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>3</value>
                <value_meaning>Menu 3.</value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>
   
    <!-- End attribute definitions for the CRISM_Parameters class. -->

    <!-- Attribute definitions for the SHARAD_Parameters class, in alphabetical order:
 
	    array_first_value
	    array_interval
	    array_last_value       
        array_scale
        array_unit
        azimuth_processing_window
        chirp_frequency envelope
        multilook_doppler_bandwidth
        name
        number_of_looks
        range_compression_window
        synthetic_aperture_duration
	    
    -->
    <DD_Attribute> <name>array_first_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.array_first_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The array_first_value element provides the first value in an ascending 
            series and is therefore the minimum value at which a given data item was sampled. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>array_interval</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.array_interval</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The array_interval attribute provides the spacing of points at which data 
            are sampled and at which values for an instrument or other parameter are available. 
            If x1 and xn are the first and last sampling parameter values, respectively, xn 
            is larger than x1, n is the number of sampling parameters, the caret symbol (^) 
            denotes exponentiation, and b, a positive real number, is the base for 
            exponentiation, then the value of sampling_parameter_interval is: (xn-x1)/(n-1) 
            (for sampling_parameter_scale = Linear), (xn/x1)^(1/(n-1)) (for 
            sampling_parameter_scale = Logarithmic), (b^xn-b^x1)/(n-1) (for 
            sampling_parameter_scale = Exponential). 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>array_last_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.array_last_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The array_last_value element provides the last value in an ascending 
            series and is therefore the maximum value at which a given data item was sampled. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>array_scale</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.array_scale</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The array_scale attribute specifies whether the sampling interval is linear or 
            something other such as logarithmic. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>Linear</value>
                <value_meaning>Values of Uniformly Sampled are given at uniform (linear) spacings 
                    of an independent variable - for example, 1, 2, 3, 4, ...
                </value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Exponential</value>
                <value_meaning>The values of the independent variable in exponential uniformly 
                    sampled data are given at uniform spacing of the exponential of some base b, 
                    a positive real number. That is, for independent variable x in the range [x1, 
                    xn], the sampling points xj satisfy: b^xj = b^x1 + (j-1)(b^xn - b^x1)/(n-1) 
                    for j = 1 ... n where the caret symbol (^) denotes exponentiation. For 
                    example, if the independent variable has values 0., 0.30103, 0.47712, 
                    0.60206, ... and the base is 10, then the Exponential Uniformly Spaced data 
                    are given at 10^0., 10^0.30103, 10^0.47712, 10^0.60206, ... or 1, 2, 3, 4, ...
                </value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>Logarithmic</value>
                <value_meaning>The values of the independent variable, x, in logarithmic uniformly 
                    sampled data are given at uniform spacing of the logarithm of x in some base, 
                    b, a positive real number. That is, for independent variable x in the range 
                    [x1, xn], the sampling points xj satisfy: log_b(xj) = log_b(x1) + 
                    (j-1)(log_b(xn) - log_b(x1))/(n-1) for j = 1 ... n where log_b(x) is the log 
                    of x in base b. For example, if the independent variable has values 1, 10, 
                    100, 1000, ... and the base is 10, then the Logarithmic Uniformly Spaced data 
                    are given at 0, 1, 2, 3 ...
                </value_meaning>
            </DD_Permissible_Value>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>array_unit</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.array_unit</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The array_unit element specifies the unit of measure of associated data 
            sampling parameters. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>azimuth_processing_window</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.azimuth_processing_window</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The windowing function used to reduce sidelobes resulting from azimuth 
            (along-track) synthetic aperture processing of the raw echo records. All 
            radargrams in the SHARAD radargram archive use a Hann function.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>chirp_frequency_envelope</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.chirp_frequency_envelope</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The frequency-dependent amplitude variation used in range compression of the 
            raw echo data. All radargrams in the SHARAD radargram archive use a 
            uniform-amplitude model.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>multilook_doppler_bandwidth</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.multilook_doppler_bandwidth</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The frequency span over which radar echoes are averaged, following 
            synthetic aperture processing for each spatial footprint along the ground 
            track. This frequency span is measured to either side of the zero-frequency 
            component of the Doppler spectrum.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Frequency</unit_of_measure_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>name</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.name</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The name element provides the name of the parameter which determines the 
            sampling interval of a particular instrument or dataset parameter. For example, 
            magnetic field intensity is sampled in time increments, and a spectrum is sampled 
            in wavelength or frequency. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>number_of_looks</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.number_of_looks</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The number of frequency-resolved cells included in the multi-look averaging. 
            This varies with the chosen frequency span and the Doppler resolution set by 
            the inverse of the coherent integration time.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>range_compression_window</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.range_compression_window</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The windowing function used to reduce sidelobes resulting from range 
            compression of the raw echo records. All radargrams in the SHARAD radargram
            archive use a Hann function.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>synthetic_aperture_duration</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.synthetic_aperture_duration</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>The coherent integration time for SHARAD signals processed using 
            the synthetic aperture technique. Multiplication of this value by the MRO 
            tangential velocity tabulated in the SHARAD radargram *GEOM.TAB files yields an 
            approximate physical length of the aperture.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Time</unit_of_measure_type>
        </DD_Value_Domain>
    </DD_Attribute>
    
    <!-- End attribute definitions for the SHARAD_Parameters class. -->
    
    <!-- Attribute definitions for the CRISM_ATO_Parameters class, in alphabetical order:
 
	    max_sample
	    max_line
	    min_sample
	    min_line
	    
    -->

    <DD_Attribute> <name>max_sample</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ato.max_sample</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Daniel Politte</submitter_name>
        <definition>The index of the highest-numbered sample/column of this product relative to the original CRISM scene. The first sample of the original CRISM scene corresponds to a value of 1.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>max_line</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ato.max_line</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Daniel Politte</submitter_name>
        <definition>The index of the highest-numbered line/row of this product relative to the original CRISM scene. The first line of the original CRISM scene corresponds to a value of 1.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>min_sample</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ato.min_sample</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Daniel Politte</submitter_name>
        <definition>The index of the lowest-numbered sample/column of this product relative to the original CRISM scene. The first sample of the original CRISM scene corresponds to a value of 1.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>min_line</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ato.min_line</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>Daniel Politte</submitter_name>
        <definition>The index of the lowest-numbered line/row of this product relative to the original CRISM scene. The first line of the original CRISM scene corresponds to a value of 1.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>

    <!-- End attribute definitions for the CRISM_ATO_Parameters class. -->
    
    <!-- Attribute definitions for the HiRISE_Time_Parameters class, in alphabetical order:

        analog_power_start_count
        analog_power_start_time
        calibration_start_count
        calibration_start_time
	    observation_start_time 
        readout_start_count           
        readout_start_time
               
    -->
    <DD_Attribute><name>analog_power_start_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.analog_power_start_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The analog_power_start_count attribute provides the spacecraft clock count
            when power to the CPMM units was applied. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>analog_power_start_time</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.analog_power_start_time</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The analog_power_start_time attribute provides the UTC time 
            when power to the CPMM units was applied. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Date_Time_YMD_UTC</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>calibration_start_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.calibration_start_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The calibration_start_count attribute provides the spacecraft clock count
            at the beginning of the first calibration image line.  
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>calibration_start_time</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.calibration_start_time</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The calibration_start_time attribute provides the UTC time 
            at the beginning of the first calibration image line.  
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Date_Time_YMD_UTC</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
     <DD_Attribute> <name>observation_start_time</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.observation_start_time</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The observation_start_time attribute provides the UTC start time
        of a HiRISE image acquisition sequence.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Date_Time_YMD_UTC</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>readout_start_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.readout_start_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The readout_start_count attribute provides the spacecraft clock count
     when the HiRISE CCD Process/Memory Module begins transferring image data
     out of its buffer memory.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute> <name>readout_start_time</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.readout_start_time</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The readout_start_time attribute provides the UTC time when the HiRISE
     CCD Process/Memory Module begins transferring image data out of buffer
     memory.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Date_Time_YMD_UTC</value_data_type>
        </DD_Value_Domain>
    </DD_Attribute>
    <!-- End attribute definitions for the HiRISE_Time_Parameters class. -->
    
     <!-- Attribute definitions for the HiRISE_Instrument_Setting_Parameters class, in alphabetical order:

        adc_timing_settings_image           
        adc_timing_settings_reset           
        binning                       
        channel_number                
        cpmm_number                   
        delta_line_timer_count        
        dll_frequency_correct_count  
        dll_locked_flag_01               
        dll_locked_flag_02               
        dll_locked_once_flag_01          
        dll_locked_once_flag_02          
        dll_reset_count               
        felics_compression_flag       
        focus_position_count          
        heater_control_flag_00           
        heater_control_flag_01           
        heater_control_flag_02           
        heater_control_flag_03           
        heater_control_flag_04           
        heater_control_flag_05           
        heater_control_flag_06           
        heater_control_flag_07           
        heater_control_flag_08           
        heater_control_flag_09           
        heater_control_flag_10           
        heater_control_flag_11           
        heater_control_flag_12           
        heater_control_flag_13           
        heater_control_mode           
        image_exposure_duration       
        line_exposure_duration        
        lookup_table_k_value          
        lookup_table_maximum          
        lookup_table_median           
        lookup_table_minimum          
        lookup_table_number           
        lookup_table_type             
        powered_cpmm_flag_00             
        powered_cpmm_flag_01             
        powered_cpmm_flag_02             
        powered_cpmm_flag_03             
        powered_cpmm_flag_04             
        powered_cpmm_flag_05             
        powered_cpmm_flag_06             
        powered_cpmm_flag_07             
        powered_cpmm_flag_08             
        powered_cpmm_flag_09             
        powered_cpmm_flag_10             
        powered_cpmm_flag_11             
        powered_cpmm_flag_12             
        powered_cpmm_flag_13             
        scan_exposure_duration                                       
        stimulation_lamp_flag_blg
        stimulation_lamp_flag_nir
        stimulation_lamp_flag_red         
        tdi                           
        trim_lines                    
            
	    
    -->
    
    <DD_Attribute><name>adc_timing_settings_image</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.adc_timing_settings_image</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The adc_timing_settings_image attribute provides the HiRISE Channel 0
     analog-to-digital conversion timing settings for the readout of the video waveform.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>9</maximum_value>	     	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>adc_timing_settings_reset</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.adc_timing_settings_reset</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The adc_timing_settings_reset attribute provides the HiRISE Channel 0
     analog-to-digital conversion timing settings for the reset of the video waveform.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
            <minimum_value>0</minimum_value>
            <maximum_value>9</maximum_value>	     	    
        </DD_Value_Domain>
    </DD_Attribute> 
    <DD_Attribute><name>binning</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>channel_number</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.channel_number</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The channel_number attribute provides the HiRISE CCD channel number.        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>0</value>
		<value_meaning>channel 0</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>channel 1</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_number</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_number</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_number attribute provides the HiRISE
          CCD Processing/Memory Module number.
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>0</value>
		<value_meaning>Module 0</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>Module 1</value_meaning>
             </DD_Permissible_Value>	    
	      <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>Module 2</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>Module 3</value_meaning>
             </DD_Permissible_Value>	  
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>Module 4</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>5</value>
		<value_meaning>Module 5</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>6</value>
		<value_meaning>Module 6</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>7</value>
		<value_meaning>Module 7</value_meaning>
             </DD_Permissible_Value>	    
             <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>Module 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>9</value>
		<value_meaning>Module 9</value_meaning>
             </DD_Permissible_Value>	  
             <DD_Permissible_Value>
                <value>10</value>
		<value_meaning>Module 10</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>11</value>
		<value_meaning>Module 11</value_meaning>
             </DD_Permissible_Value>	
	     <DD_Permissible_Value>
                <value>12</value>
		<value_meaning>Module 12</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>13</value>
		<value_meaning>Module 13</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute> 
    <DD_Attribute><name>delta_line_timer_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.delta_line_timer_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The delta_line_timer_count element provides the commanded
        count given to the HiRISE instrument to set the scan line duration.
        mro:scan_line_duration = 74 + mro:delta_line_timer_count/16
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
	    <minimum_value>0</minimum_value>
            <maximum_value>16777216</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute> 
    <DD_Attribute><name>dll_frequency_correct_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.dll_frequency_correct_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The dll_frequency_correct_count attribute provides a count of
        the number of times the HiRISE 96 MHz clock frequency was observed to
        be correct.  This is used with the recursive Digital Lock Loop
        reset circuit.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>0</minimum_value>
            <maximum_value>255</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>  
    <DD_Attribute><name>dll_locked_flag_01</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.dll_locked_flag_01</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The dll_locked_flag_01 attribute provides the state of the 1st
        96 Mhz Digital Lock Loop flag for a HiRISE observation. 
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>NO</value>
		<value_meaning>Lock off</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>YES</value>
		<value_meaning>Lock on</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>         
    <DD_Attribute><name>dll_locked_flag_02</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.dll_locked_flag_02</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The dll_locked_flag_02 attribute provides the state of the 2nd
        96 Mhz Digital Lock Loop flag for a HiRISE observation.        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>NO</value>
		<value_meaning>Lock off</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>YES</value>
		<value_meaning>Lock on</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>  
    <DD_Attribute><name>dll_locked_once_flag_01</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.dll_locked_once_flag_01</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The dll_locked_once_flag_01 attribute indicates if the 1st Digital
         Lock Loop ever locked during a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>NO</value>
		<value_meaning>did not lock</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>YES</value>
		<value_meaning>locked at least once</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>                     
    <DD_Attribute><name>dll_locked_once_flag_02</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.dll_locked_once_flag_02</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The dll_locked_once_flag_02 attribute indicates if the 2nd Digital
         Lock Loop ever locked during a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>NO</value>
		<value_meaning>did not lock</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>YES</value>
		<value_meaning>locked at least once</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>  
    <DD_Attribute><name>dll_reset_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.dll_reset_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The dll_reset_count attribute provides the count of the number of
     times during a HiRISE observation the 96 MHz Digital Lock Loop had
     to be reset in order to lock to the incoming 48 Mhz clock and produce
     an 96 MHz clock.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>0</minimum_value>
            <maximum_value>255</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute><name>felics_compression_flag</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.felics_compression_flag</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The felics_compression_flag element identifies whether FELICS
        data compression was applied to a HiRISE image.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>NO</value>
		<value_meaning>No felics compression</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>YES</value>
		<value_meaning>felics compression applied</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>                                                       
    <DD_Attribute><name>focus_position_count</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.focus_position_count</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The focus_position_count attribute provides the raw count of the
        focus mechanism position in a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>				         	     
        </DD_Value_Domain>
    </DD_Attribute> 
    <DD_Attribute><name>heater_control_flag_00</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_00</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The heater_control_flag element is a set of 14 on/off flags
            that indicate which of the 14 heater control areas were on at the
            time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>heater on</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>heater off</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>  
    <DD_Attribute><name>heater_control_flag_01</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_01</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>heater_control_flag_02</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_02</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>heater_control_flag_03</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_03</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_04</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_04</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>heater_control_flag_05</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_05</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_06</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_06</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>heater_control_flag_07</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_07</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>heater_control_flag_08</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_08</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_09</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_09</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_10</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_10</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_11</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_11</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_12</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_12</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>
    <DD_Attribute><name>heater_control_flag_13</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_flag_13</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_flag element is a set of 14 on/off flags
        that indicate which of the 14 heater control areas were on at the
        time of a HiRISE observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>heater on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>heater off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>   
     <DD_Attribute><name>heater_control_mode</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_control_mode</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_control_mode attribute provides the state of the HiRISE
        heater control, either closed-loop or duty-cycle.  Normally the
        closed-loop mode is used to keep nominal operating temperatures of the
        instrument. A duty-cycle mode is enabled during periods of high EM
        emissions from other MRO instruments.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>CLOSED LOOP</value>
                <value_meaning>closed-loop mode</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>DUTY CYCLE</value>
                <value_meaning>duty cycle mode</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>     
    <DD_Attribute><name>image_exposure_duration</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.image_exposure_duration</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The image_exposure_duration attribute provides the total time
        of a HiRISE observation from the start of the first line to the end
        of the last line computed by multiplying the total number of
        lines in the array times the line exposure duration. 
	Units of microseconds.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Time</unit_of_measure_type>	    				         	     
        </DD_Value_Domain>
    </DD_Attribute>   
    <DD_Attribute><name>line_exposure_duration</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.line_exposure_duration</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The line_exposure_duration attribute provides the time from the
        start of exposure of one binned line to the start of exposure of
        the next binned line in a HiRISE image. 
	Units of microseconds.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Time</unit_of_measure_type>	    				         	     
        </DD_Value_Domain>
    </DD_Attribute> 
    <DD_Attribute><name>lookup_table_k_value</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.lookup_table_k_value</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The lookup_table_k_value attribute provides the 'pixel spread'
        value in a HiRISE image. This parameter is used only for the
        HiRISE SQUARE-ROOT LUT table mode.  A -9998 value indicates a K
        value was not used.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>-9998</minimum_value>
            <maximum_value>32</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>    
    <DD_Attribute><name>lookup_table_maximum</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.lookup_table_maximum</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The lookup_table_maximum attribute provides the maximum 14-bit
        pixel value mapped to the 254 DN 8-bit pixel in a HiRISE image.
        This parameter is used only for the HiRISE LINEAR LUT table mode.
        A -9998 value indicates that the maximum value was not used.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>-9998</minimum_value>
            <maximum_value>16384</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>   
    <DD_Attribute><name>lookup_table_median</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.lookup_table_median</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The lookup_table_median attribute provides the median 14-bit
        pixel value mapped to the 254 DN 8-bit pixel in a HiRISE image.
        This parameter is used only for the HiRISE SQUARE-ROOT LUT table
        mode. A -9998 value indicates that the table median value was not used.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>-9998</minimum_value>
            <maximum_value>16384</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>   
    <DD_Attribute><name>lookup_table_minimum</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.lookup_table_minimum</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The lookup_table_minimum attribute provides the minimum 14-bit
        pixel value mapped to the 0 DN output pixel in a HiRISE image.
        This parameter is used only for the HiRISE LINEAR LUT table mode.
        A -9998 value indicates that the maximum value was not used.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>-9998</minimum_value>
            <maximum_value>16384</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>     
    <DD_Attribute><name>lookup_table_number</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.lookup_table_number</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The lookup_table_number attribute provides the number of the
        stored LUT used in a HiRISE image. This parameter is used only for
        the HiRISE STORED LUT table mode. A value of -9998 indicates that a
        table number was not used.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>-9998</minimum_value>
            <maximum_value>28</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>     
     <DD_Attribute><name>lookup_table_type</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.lookup_table_type</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The lookup_table_type attribute provides the type of lookup table
        that was applied to convert 14-bit pixels to 8-bit pixels in a HiRISE
        image.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>LINEAR</value>
                <value_meaning>linear LUT</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>N/A</value>
                <value_meaning>no LUT</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>SQUARE ROOT</value>
                <value_meaning>square root LUT</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>STORED</value>
                <value_meaning>stored LUT</value_meaning>
             </DD_Permissible_Value>	     	         	     
        </DD_Value_Domain>													
    </DD_Attribute> 
    <DD_Attribute><name>powered_cpmm_flag_00</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_00</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
            The powered_cpmm_flag attribute provides a set of 14 values that
            identify which HiRISE CCD Processing/Memory Modules were commanded to
            acquire imaging during the observation. The first element is for CPMM 0
            and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>     
    <DD_Attribute><name>powered_cpmm_flag_01</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_01</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_02</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_02</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_03</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_03</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_04</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_04</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_05</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_05</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_06</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_06</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_07</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_07</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_08</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_08</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_09</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_09</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_10</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_10</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_11</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_11</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_12</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_12</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>        
    <DD_Attribute><name>powered_cpmm_flag_13</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.powered_cpmm_flag_13</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The powered_cpmm_flag attribute provides a set of 14 values that
        identify which HiRISE CCD Processing/Memory Modules were commanded to
        acquire imaging during the observation. The first element is for CPMM 0
       and the last element is for CPMM 13.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>CPMM powered on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>CPMM powered off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>               
    <DD_Attribute><name>scan_exposure_duration</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.scan_exposure_duration</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The scan_exposure_duration attribute provides the
        unbinned line readout rate of the HiRISE instrument in microseconds.
        This corresponds to the time between successive steps in the
        Time Delay Integration (TDI) process. The adjustment of this
        parameter is used to match image line acquisition to the
        boresight ground velocity.  The value is the same for all
        CCDs for a given observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
	    <minimum_value>74</minimum_value>
            <maximum_value>1048650</maximum_value>
	    <unit_of_measure_type>Units_of_Time</unit_of_measure_type>				         	     
        </DD_Value_Domain>
    </DD_Attribute>     
    <DD_Attribute><name>stimulation_lamp_flag_red</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.stimulation_lamp_flag_red</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The stimulation_lamp_flag attribute is a set of three flags that
        identify which of the three HiRISE stimulation lamps have been turned
        on or off. Stimulation lamps are used to evaluate relative changes in
        instrument calibration throughout the mission.  Stimulation lamps are
        always turned off for science observation data.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>stim lamp on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>stim lamp off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>      
    <DD_Attribute><name>stimulation_lamp_flag_nir</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.stimulation_lamp_flag_nir</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The stimulation_lamp_flag attribute is a set of three flags that
        identify which of the three HiRISE stimulation lamps have been turned
        on or off. Stimulation lamps are used to evaluate relative changes in
        instrument calibration throughout the mission.  Stimulation lamps are
        always turned off for science observation data.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>stim lamp on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>stim lamp off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>      
    <DD_Attribute><name>stimulation_lamp_flag_blg</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.stimulation_lamp_flag_blg</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The stimulation_lamp_flag attribute is a set of three flags that
        identify which of the three HiRISE stimulation lamps have been turned
        on or off. Stimulation lamps are used to evaluate relative changes in
        instrument calibration throughout the mission.  Stimulation lamps are
        always turned off for science observation data.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
                <value_meaning>stim lamp on</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
                <value_meaning>stim lamp off</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>													
    </DD_Attribute>      
    <DD_Attribute><name>tdi</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>trim_lines</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.trim_lines</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The trim_lines attribute provides the number of lines that have
        been trimmed at the beginning of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>0</minimum_value>
        </DD_Value_Domain>
    </DD_Attribute>      
    
     <!-- End attribute definitions for the HiRISE_Instrument_Setting_Parameters class -->
    
    
     <!-- Attribute definitions for the HiRISE_Temperature_Parameters class, in alphabetical order:

        barrel_baffle_temperature     
        cpmm_pws_board_temperature    
        field_stop_temperature        
        focus_motor_temperature       
        fpa_negative_y_temperature    
        fpa_positive_y_temperature    
        (fpe_temperature ALREADY DEFINED ABOVE)             
        iea_temperature               
        ie_pws_board_temperature      
        inst_cont_board_temperature     
        mech_tlm_board_temperature    
        ms_truss_leg_0_a_temperature  
        ms_truss_leg_0_b_temperature  
        ms_truss_leg_120_a_temperature
        ms_truss_leg_120_b_temperature
        ms_truss_leg_240_a_temperature
        ms_truss_leg_240_b_temperature
        opt_bnch_box_beam_temperature 
        opt_bnch_cover_temperature    
        opt_bnch_flexure_temperature  
        opt_bnch_fold_flat_temperature
        opt_bnch_fpa_temperature      
        opt_bnch_fpe_temperature      
        opt_bnch_living_rm_temperature
        opt_bnch_mirror_temperature   
        primary_mirror_baf_temperature
        primary_mirror_mnt_temperature
        primary_mirror_temperature    
        sec_mirror_baffle_temperature 
        sec_mirror_mtr_rng_temperature
        sec_mirror_temperature        
        spider_leg_150_temperature    
        spider_leg_270_temperature    
        spider_leg_30_temperature     
        sun_shade_temperature         



      --> 
    <DD_Attribute><name>barrel_baffle_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.barrel_baffle_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The barrel_baffle_temperature attribute provides the temperature
        of the HiRISE instrument's barrel baffle in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>cpmm_pws_board_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_pws_board_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_pws_board_temperature attribute provides the temperature
        of the HiRISE instrument's CCD Processing/Memory Module Power Supply
        Board in degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS,
        REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>field_stop_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.field_stop_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The field_stop_temperature attribute provides the temperature
        of the HiRISE instrument's focus mechanism field stop in degrees
        Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>focus_motor_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.focus_motor_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The focus_motor_temperature attribute provides the temperature
        of the HiRISE instrument's focus mirror in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>fpa_negative_y_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fpa_negative_y_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The fpa_negative_y_temperature attribute provides the temperature
        of the HiRISE instrument's Focal Plane Array -Y location in
        degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID
        JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>fpa_positive_y_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.fpa_positive_y_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The fpa_positive_y_temperature attribute provides the temperature
        of the HiRISE instrument's Focal Plane Array  +Y side location in
        degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID
        JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>iea_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.iea_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The iea_temperature attribute provides the temperature of the
        HiRISE instrument's Instrument Electronics Assembly in degrees
        Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ie_pws_board_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ie_pws_board_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ie_pws_board_temperature attribute provides the temperature
        of the HiRISE instrument's Instrument Electronics Power Supply
        Board in degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS,
        REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>inst_cont_board_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.inst_cont_board_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The inst_cont_board_temperature attribute provides the temperature
        of the HiRISE instrument control board in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>mech_tlm_board_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.mech_tlm_board_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The mech_tlm_board_temperature attribute provides the temperature
        of the HiRISE instrument's Mech/TLM Board in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ms_truss_leg_0_a_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ms_truss_leg_0_a_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ms_truss_leg_0_a_temperature attribute provides the
        temperature of the HiRISE instrument's metering structure
        truss 0-A leg in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ms_truss_leg_0_b_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ms_truss_leg_0_b_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ms_truss_leg_0_b_temperature attribute provides the
        temperature of the HiRISE instrument's metering structure
        truss 0-B leg in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ms_truss_leg_120_a_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ms_truss_leg_120_a_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ms_truss_leg_120_a_temperature attribute provides the
        temperature of the HiRISE instrument's metering structure
        truss 120-A leg in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ms_truss_leg_120_b_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ms_truss_leg_120_b_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ms_truss_leg_120_b_temperature attribute provides the
        temperature of the HiRISE instrument's metering structure
        truss 120-B leg in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ms_truss_leg_240_a_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ms_truss_leg_240_a_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ms_truss_leg_240_a_temperature attribute provides the
        temperature of the HiRISE instrument's metering structure
        truss 240-A leg in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>ms_truss_leg_240_b_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ms_truss_leg_240_b_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ms_truss_leg_240_b_temperature attribute provides the
        temperature of the HiRISE instrument's metering structure
        truss 240-B leg in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_box_beam_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_box_beam_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_box_beam_temperature attribute provides the temperature
        of the HiRISE instrument's optical bench near the box beam (+Y face)
        in degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID
        JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_cover_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_cover_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_cover_temperature attribute provides the temperature
        of the HiRISE instrument's optical bench cover (external) in degrees
        Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_flexure_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_flexure_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_flexure_temperature attribute provides the temperature
        of the HiRISE instrument's optical bench near the +X MDR flexure in
        degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID
        JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_fold_flat_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_fold_flat_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_fold_flat_temperature attribute provides the
        temperature of the HiRISE instrument's optical fold flat mirror
        location in degrees Centigrade. See Figure 2.3, MRO HiRISE EDR
        SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_fpa_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_fpa_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_fpa_temperature attribute provides the temperature
        of the HiRISE instrument's optical bench near the Focal Plane
        Array in degrees Centigrade. See Figure 2.3, MRO HiRISE EDR
        SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_fpe_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_fpe_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_fpe_temperature attribute provides the temperature
        of the HiRISE instrument's optical bench near the Focal Plane
        Electronics in degrees Centigrade. See Figure 2.3, MRO HiRISE
        EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_living_rm_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_living_rm_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_living_rm_temperature attribute provides the
        temperature of the HiRISE instrument's optical bench in the
        sunken living room location in degrees Centigrade. See Figure
        2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>opt_bnch_mirror_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.opt_bnch_mirror_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The opt_bnch_mirror_temperature attribute provides the temperature
        of the HiRISE instrument's optical bench near the tertiary mirror
        in degrees Centigrade. See Figure 2.3, MRO HiRISE EDR SIS,
        REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>primary_mirror_baf_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.primary_mirror_baf_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The primary_mirror_baf_temperature attribute provides the
        temperature of the HiRISE instrument's primary mirror baffle
        near the base (external) in degrees Centigrade. See Figure 2.3,
        MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>primary_mirror_mnt_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.primary_mirror_mnt_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The primary_mirror_mnt_temperature attribute provides the temperature
        of the HiRISE instrument's primary mirror mount in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>             
    <DD_Attribute><name>primary_mirror_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.primary_mirror_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The primary_mirror_temperature attribute provides the
        temperature of the HiRISE instrument's primary mirror
        at its maximum thickness in degrees Centigrade. See
        Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>sec_mirror_baffle_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sec_mirror_baffle_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The sec_mirror_baffle_temperature attribute provides the
        temperature of the HiRISE instrument's secondary mirror
        baffle near the base (external) in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>sec_mirror_mtr_rng_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sec_mirror_mtr_rng_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The sec_mirror_mtr_rng_temperature attribute provides the
        temperature of the HiRISE instrument's secondary mirror
        metering ring in degrees Centigrade. See Figure 2.3, MRO
        HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>sec_mirror_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sec_mirror_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The sec_mirror_temperature attribute provides the temperature
        of the HiRISE instrument's secondary mirror in degrees Centigrade.
        See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>spider_leg_150_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spider_leg_150_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The spider_leg_150_temperature attribute provides the
        temperature of the HiRISE instrument's spider leg at the
        150 degree location in degrees Centigrade. See Figure 2.3,
        MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>spider_leg_270_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spider_leg_270_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The spider_leg_270_temperature attribute provides the
        temperature of the HiRISE instrument's spider leg at the
        270 degree location in degrees Centigrade. See Figure 2.3,
        MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>spider_leg_30_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.spider_leg_30_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The spider_leg_30_temperature attribute provides the
        temperature of the HiRISE instrument's spider leg at the
        30 degree location in degrees Centigrade. See Figure 2.3,
        MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>sun_shade_temperature</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.sun_shade_temperature</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The sun_shade_temperature attribute provides the temperature of
       the HiRISE instrument's sun shade under the MLI in degrees Centigrade.
       See Figure 2.3, MRO HiRISE EDR SIS, REFKEYID JPLD-32004.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Temperature</unit_of_measure_type>
            <specified_unit_id>C</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       

    
     <!-- End of attribute definitions for the HiRISE_Temperature_Parameters class  -->



    
     <!-- Attribute definitions for the HiRISE_Power_Parameters class, in alphabetical order:


        cpmm_negative_5_current       
        cpmm_negative_5_voltage       
        cpmm_positive_10_current      
        cpmm_positive_10_voltage      
        cpmm_positive_1_8_current     
        cpmm_positive_1_8_voltage     
        cpmm_positive_2_5_current     
        cpmm_positive_2_5_voltage     
        cpmm_positive_29_current      
        cpmm_positive_29_voltage      
        cpmm_positive_3_3_current     
        cpmm_positive_3_3_voltage     
        cpmm_positive_5_current       
        cpmm_positive_5_voltage       
        heater_current                
        iea_negative_15_voltage       
        iea_positive_15_voltage       
        iea_positive_28_voltage       
        iea_positive_5_voltage        
        inst_cont_fpga_pos_2_5_voltage
        mech_tlm_fpga_pos_2_5_voltage 


     -->


    <DD_Attribute><name>cpmm_negative_5_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_negative_5_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_negative_5_current attribute provides the negative 5
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_negative_5_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_negative_5_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_negative_5_voltage attribute provides the negative
        5 voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_10_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_10_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_10_current attribute provides the positive 10
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_10_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_10_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_10_voltage attribute provides the positive 10
        voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_1_8_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_1_8_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_1_8_current attribute provides the positive 1_8
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_1_8_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_1_8_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_1_8_voltage attribute provides the positive 1_8
        voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_2_5_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_2_5_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_2_5_current attribute provides the positive 2_5
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_2_5_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_2_5_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_2_5_voltage attribute provides the positive 2_5
        voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_29_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_29_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_29_current attribute provides the positive 29
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_29_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_29_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_29_voltage attribute provides the positive 29
        voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_3_3_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_3_3_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_3_3_current attribute provides the positive 3_3
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_3_3_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_3_3_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_3_3_voltage attribute provides the positive 3_3
        voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_5_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_5_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_5_current attribute provides the positive 5
        current of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>cpmm_positive_5_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.cpmm_positive_5_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The cpmm_positive_5_voltage attribute provides the positive 5
        voltage state of the HiRISE CCD Processing/Memory Module.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>heater_current</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.heater_current</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The heater_current attribute provides the HiRISE heater current
        in amps.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Current</unit_of_measure_type>
            <specified_unit_id>A</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>iea_negative_15_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.iea_negative_15_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The iea_negative_15_voltage attribute provides the negative
        15 voltage state of the HiRISE Interface Electronics Assembly.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>iea_positive_15_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.iea_positive_15_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The iea_positive_15_voltage attribute provides the positive
        15 voltage state of the HiRISE Interface Electronics Assembly.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>iea_positive_28_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.iea_positive_28_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The iea_positive_28_voltage attribute provides the positive
        28 voltage state of the HiRISE Interface Electronics Assembly.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>iea_positive_5_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.iea_positive_5_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The iea_positive_5_voltage attribute provides the positive
        5 voltage state of the HiRISE Interface Electronics Assembly.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>inst_cont_fpga_pos_2_5_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.inst_cont_fpga_pos_2_5_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The inst_cont_fpga_pos_2_5_voltage attribute provides the
        positive 2_5 voltage state of the HiRISE instrument control
        Field-Programmable Gate Array.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       
    <DD_Attribute><name>mech_tlm_fpga_pos_2_5_voltage</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.mech_tlm_fpga_pos_2_5_voltage</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The mech_tlm_fpga_pos_2_5_voltage attribute provides the
        positive 2_5 voltage state of the HiRISE Mech/TLM Field-Programmable
        Gate Array.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Real</value_data_type>
            <unit_of_measure_type>Units_of_Voltage</unit_of_measure_type>
            <specified_unit_id>V</specified_unit_id>
        </DD_Value_Domain>
    </DD_Attribute>       


<!-- End attribute definitions for the HiRISE_Power_Parameters class -->

<!-- Attribute definitions for the HiRISE_RDR_Parameters class, in alphabetical order with subgroups in label order:

	binning_red0
	binning_red1
	binning_red2
	binning_red3
	binning_red4
	binning_red5
	binning_red6
	binning_red7
	binning_red8
	binning_red9
	binning_ir10
	binning_ir11
	binning_bg12
	binning_bg13
	ccd_flag_red0
	ccd_flag_red1
	ccd_flag_red2
	ccd_flag_red3
	ccd_flag_red4
	ccd_flag_red5
	ccd_flag_red6
	ccd_flag_red7
	ccd_flag_red8
	ccd_flag_red9
	ccd_flag_ir10
	ccd_flag_ir11
	ccd_flag_bg12
	ccd_flag_bg13
	maximum_stretch
	minimum_stretch
	special_processing_flag_red0
	special_processing_flag_red1
	special_processing_flag_red2
	special_processing_flag_red3
	special_processing_flag_red4
	special_processing_flag_red5
	special_processing_flag_red6
	special_processing_flag_red7
	special_processing_flag_red8
	special_processing_flag_red9
	special_processing_flag_ir10
	special_processing_flag_ir11
	special_processing_flag_bg12
	special_processing_flag_bg13	
	tdi_red0
	tdi_red1
	tdi_red2
	tdi_red3
	tdi_red4
	tdi_red5
	tdi_red6
	tdi_red7
	tdi_red8
	tdi_red9
	tdi_ir10
	tdi_ir11
	tdi_bg12
	tdi_bg13
	-->	     
    <DD_Attribute><name>binning_red0</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red0</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red3</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red3</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red4</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red4</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red5</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red5</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red6</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red6</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red7</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red7</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red8</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red8</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_red9</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_red9</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_ir10</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_ir10</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_ir11</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_ir11</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_bg12</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_bg12</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>binning_bg13</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.binning_bg13</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The binning element provides the HiRISE observation binning mode;
         i.e., the number of lines binned in an observation.
         mro:line_exposure_duration = mro:binning * mro:scan_line_duration
             </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>1</value>
		<value_meaning>bin 1</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>2</value>
		<value_meaning>bin 2</value_meaning>
             </DD_Permissible_Value>	    
	          <DD_Permissible_Value>
                <value>3</value>
		<value_meaning>bin 3</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>4</value>
		<value_meaning>bin 4</value_meaning>
             </DD_Permissible_Value>	  
	          <DD_Permissible_Value>
                <value>8</value>
		<value_meaning>bin 8</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>16</value>
		<value_meaning>bin 16</value_meaning>
             </DD_Permissible_Value>	       	     
        </DD_Value_Domain>
    </DD_Attribute>           
    <DD_Attribute><name>ccd_flag_red0</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red0</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red1</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red2</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red3</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red3</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red4</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red4</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red5</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red5</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red6</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red6</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red7</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red7</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red8</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red8</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_red9</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_red9</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_ir10</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_ir10</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_ir11</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_ir11</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_bg12</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_bg12</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>ccd_flag_bg13</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.ccd_flag_bg13</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The ccd_flag elements identify which CCDs were operating at the
        time of an observation. There is a special processing flag for each
        CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
	     <DD_Permissible_Value>
                <value>ON</value>
		<value_meaning>the CCD was actively acquiring data during the observation.</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>OFF</value>
		<value_meaning>the CCD was turned off during the observation.</value_meaning>
             </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>maximum_stretch</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.maximum_stretch</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The maximum_stretch attribute provides a contrast stretch value to
        be used in the display of a HiRISE Image. The mro.maximum_stretch
        parameter specifies the DN value to map to the 255 DN value of the
        display. For color images, there will be three values, one for each
     color.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>0</minimum_value>
            <maximum_value>1024</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>  
    <DD_Attribute><name>minimum_stretch</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.minimum_stretch</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The minimum_stretch attribute provides a contrast stretch value to
        be used in the display of a HiRISE Image. The mro.minimum_stretch
        parameter specifies the DN value to map to the 0 DN value of the
        display. For color images, there will be three values, one for each
     color.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>false</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	    <minimum_value>0</minimum_value>
            <maximum_value>1024</maximum_value>				         	     
        </DD_Value_Domain>
    </DD_Attribute>

    <DD_Attribute><name>special_processing_flag_red0</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red0</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red1</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red2</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red3</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red3</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red4</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red4</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red5</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red5</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red6</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red6</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red7</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red7</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red8</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red8</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_red9</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_red9</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_ir10</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_ir10</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_ir11</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_ir11</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_bg12</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_bg12</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>special_processing_flag_bg13</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.special_processing_flag_bg13</local_identifier>
        <nillable_flag>false</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The special_processing_flag elements indicate if special
        calibration processing was applied to a HiRISE CCD image. The
        HiRISE instrument may experience instability problems or a
        low-signal image may have been poorly calibrated requiring an
        alternate calibration strategy. There is a special processing
        flag for each CCD used in the observation.        
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Short_String_Collapsed</value_data_type>
            <DD_Permissible_Value>
                <value>NOMINAL</value>
                <value_meaning>the standard calibration processing was used for the CCD image.</value_meaning>
            </DD_Permissible_Value>
            <DD_Permissible_Value>
                <value>CUBENORM</value>
                <value_meaning>the calibration processing used a columnar gain correction based on columnar statistics of the image.</value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>BADCAL</value>
                <value_meaning>The channel could not be properly calibrated. This may be due to data gaps or 
                    instabilities in the instrument electronics (eg. Bitflips).
                </value_meaning>
            </DD_Permissible_Value>	         	     
            <DD_Permissible_Value>
                <value>NULL</value>
                <value_meaning>the CCD was not operating or was missing for this observation.</value_meaning>
            </DD_Permissible_Value>	         	     
        </DD_Value_Domain>
    </DD_Attribute>	
    <DD_Attribute><name>tdi_red0</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red0</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red1</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red1</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red2</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red2</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red3</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red3</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red4</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red4</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red5</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red5</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red6</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red6</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red7</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red7</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red8</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red8</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_red9</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_red9</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_ir10</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_ir10</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_ir11</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_ir11</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_bg12</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_bg12</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
    <DD_Attribute><name>tdi_bg13</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.tdi_bg13</local_identifier>
        <nillable_flag>true</nillable_flag>
        <submitter_name>IMG</submitter_name>
        <definition>
	The tdi attribute provides the number of time delay and
        integration (TDI) stages used to increase the exposure time
        of a HiRISE observation.
        </definition>
        <DD_Value_Domain>
            <enumeration_flag>true</enumeration_flag>
            <value_data_type>ASCII_Integer</value_data_type>
	     <DD_Permissible_Value>
                <value>8</value>
                <value_meaning>8 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>32</value>
                <value_meaning>32 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>64</value>
                <value_meaning>64 stages</value_meaning>
             </DD_Permissible_Value>
	     <DD_Permissible_Value>
                <value>128</value>
                <value_meaning>128 stages</value_meaning>
             </DD_Permissible_Value> 	     
        </DD_Value_Domain>
    </DD_Attribute>      
     

<!-- End attribute definitions for the HiRISE_RDR_Parameters class --> 
   
<!-- END OF ATTRIBUTE DEFINITIONS -->
    
<!-- BEGINNING OF CLASS DEFINITIONS -->
<!-- Class definitions are in order from innermost to outermost -->

    
    <!-- Beginning of HiRISE_Time_Parameters definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>HiRISE_Time_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.HiRISE_Time_Parameters</local_identifier>
        <submitter_name>IMG</submitter_name>
        <definition>The HiRISE_Time_Parameters class contains attributes specific to HiRISE EDRs.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
	<DD_Association>
            <identifier_reference>mro.observation_start_time</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.readout_start_time</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.readout_start_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.analog_power_start_time</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.analog_power_start_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.calibration_start_time</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.calibration_start_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
    </DD_Class>    
    <!-- End of HiRISE_Time_Parameters Class definition -->
    
    
    <!-- Beginning of HiRISE_Instrument_Setting_Parameters definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>HiRISE_Instrument_Setting_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.HiRISE_Instrument_Setting_Parameters</local_identifier>
        <submitter_name>IMG</submitter_name>
        <definition>The HiRISE_Instrument_Setting_Parameters class contains attributes specific to HiRISE EDRs.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.cpmm_number</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.channel_number</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.scan_exposure_duration</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.line_exposure_duration</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.image_exposure_duration</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.delta_line_timer_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_00</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_01</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_02</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_03</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_04</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_05</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_06</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_07</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_08</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_09</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_10</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_11</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_12</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.powered_cpmm_flag_13</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.binning</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.tdi</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.trim_lines</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.focus_position_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.felics_compression_flag</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.stimulation_lamp_flag_red</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.stimulation_lamp_flag_blg</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.stimulation_lamp_flag_nir</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_mode</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_00</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_01</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_02</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_03</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_04</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_05</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_06</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_07</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_08</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_09</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_10</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_11</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_12</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_control_flag_13</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.lookup_table_type</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.lookup_table_minimum</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.lookup_table_maximum</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.lookup_table_median</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.lookup_table_k_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.lookup_table_number</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.adc_timing_settings_image</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.adc_timing_settings_reset</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.dll_locked_flag_01</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.dll_locked_flag_02</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.dll_locked_once_flag_01</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.dll_locked_once_flag_02</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.dll_reset_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.dll_frequency_correct_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
		
    </DD_Class>    
    <!-- End of HiRISE_Instrument_Setting_Parameters Class definition -->
    
    
    <!-- Beginning of HiRISE_Temperature_Parameters definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>HiRISE_Temperature_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.HiRISE_Temperature_Parameters</local_identifier>
        <submitter_name>IMG</submitter_name>
        <definition>The HiRISE_Temperature_Parameters class contains attributes specific to HiRISE EDRs.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_flexure_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_mirror_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_fold_flat_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_fpa_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_fpe_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_living_rm_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_box_beam_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.opt_bnch_cover_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.field_stop_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fpa_positive_y_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fpa_negative_y_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fpe_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.primary_mirror_mnt_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.primary_mirror_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.primary_mirror_baf_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ms_truss_leg_0_a_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ms_truss_leg_0_b_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ms_truss_leg_120_a_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ms_truss_leg_120_b_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ms_truss_leg_240_a_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ms_truss_leg_240_b_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.barrel_baffle_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sun_shade_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spider_leg_30_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spider_leg_150_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spider_leg_270_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sec_mirror_mtr_rng_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sec_mirror_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sec_mirror_baffle_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.iea_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.focus_motor_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ie_pws_board_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_pws_board_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.mech_tlm_board_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.inst_cont_board_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>

    </DD_Class>    
    <!-- End of HiRISE_Temperature_Parameters Class definition -->
             
    <!-- Beginning of HiRISE_Power_Parameters definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>HiRISE_Power_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.HiRISE_Power_Parameters</local_identifier>
        <submitter_name>IMG</submitter_name>
        <definition>The HiRISE_Power_Parameters class contains attributes specific to HiRISE EDRs.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_29_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_29_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_10_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_10_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_5_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_5_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_3_3_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_3_3_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_2_5_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_2_5_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_1_8_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_positive_1_8_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_negative_5_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.cpmm_negative_5_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.heater_current</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.inst_cont_fpga_pos_2_5_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.mech_tlm_fpga_pos_2_5_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.iea_positive_28_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.iea_negative_15_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.iea_positive_15_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.iea_positive_5_voltage</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
		
    </DD_Class>    
    <!-- End of HiRISE_Power_Parameters Class definition -->
    
    <!-- Beginning of HiRISE_RDR_Parameters definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>HiRISE_RDR_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.HiRISE_RDR_Parameters</local_identifier>
        <submitter_name>IMG</submitter_name>
        <definition>The HiRISE_RDR_Parameters class contains attributes specific to HiRISE RDRs.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red0</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red3</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red4</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red5</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red6</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red7</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red8</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_red9</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_ir10</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_ir11</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_bg12</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ccd_flag_bg13</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red0</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red3</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red4</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red5</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red6</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red7</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red8</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_red9</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_ir10</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_ir11</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_bg12</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
	<DD_Association>
            <identifier_reference>mro.binning_bg13</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.tdi_red0</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red3</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red4</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red5</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red6</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red7</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red8</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_red9</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_ir10</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_ir11</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_bg12</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.tdi_bg13</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red0</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red3</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red4</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red5</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red6</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red7</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red8</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_red9</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_ir10</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_ir11</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_bg12</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.special_processing_flag_bg13</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.minimum_stretch</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>3</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.maximum_stretch</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>3</maximum_occurrences>
        </DD_Association>	
	
    </DD_Class>    
    <!-- End of HiRISE_RDR_Parameters Class definition -->    

    <!-- Beginning of CRISM_Hyperspectral_Data_Filter_Control_Parameters class definition with attributes in order as they appear in the label -->
    <DD_Class> <name>CRISM_Hyperspectral_Data_Filter_Control_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.CRISM_Hyperspectral_Data_Filter_Control_Parameters</local_identifier>
        <submitter_name>GEO</submitter_name>
        <definition>The CRISM_Hyperspectral_Data_Filter_Control_Parameters class contains attributes related to the 
            CRISM hyperspectral data filtering application used to convert TRR3 radiance data to I/F.</definition>
        <DD_Association>
            <identifier_reference>mro.hdf_software_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.hdf_software_version_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.if_min_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.if_max_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.trace_min_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.trace_max_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.refz_median_box_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.refz_smooth_box_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fram_stat_median_box_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fram_stat_min_deviation</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fram_stat_median_conf_lvl</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fram_stat_iqr_conf_lvl</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_ref_xy_median_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_ref_xy_smooth_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_ref_yz_median_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_ref_yz_smooth_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_ratio_xy_median_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_ratio_xy_smooth_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_res_xy_ply_order</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.rsc_res_xy_ply_extnd_width</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.log_xform_neg_clip_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_num_regions</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_start_channel_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_start_channel_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_stop_channel_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_stop_channel_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_confidence_level_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_confidence_level_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_weighting_stddev_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_weighting_stddev_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_kernel_size_x_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_kernel_size_x_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_kernel_size_y_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_kernel_size_y_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_kernel_size_z_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_kernel_size_z_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_model_order_x_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_model_order_x_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_model_order_y_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_model_order_y_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_model_order_z_r1</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ikf_model_order_z_r2</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>        
    </DD_Class>
    <!-- End of CRISM_Hyperspectral_Data_Filter_Control_Parameters Class definition -->
    
    <!-- Beginning of CRISM_Temperatures class definition with attributes in order as they appear in the label -->
    <DD_Class> <name>CRISM_Temperatures</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.CRISM_Temperatures</local_identifier>
        <submitter_name>GEO</submitter_name>
        <definition>The CRISM_Temperatures class is the container for CRISM-specific temperature-related parameters.</definition>
        <DD_Association>
            <identifier_reference>mro.detector_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.optical_bench_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spectrometer_housing_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sphere_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.fpe_temperature</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
    </DD_Class>
    <!-- End of CRISM_Temperatures Class definition -->
    
    <!-- Beginning of CRISM_Band Class definition with attributes in the order as they appear in the label -->    
    <DD_Class> <name>CRISM_Band</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.CRISM_Band</local_identifier>
        <submitter_name>Susan Slavney</submitter_name>
        <!-- definition pending approval by Frank S. -->
        <definition>The CRISM_Band class contains parameters describing a single band in 
            CRISM Browse Product 3D image array or in the CRISM data cube containing 
            refined spectral summary parameters. 
        </definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.band_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.band_sequence_number</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.scaling_factor</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.value_offset</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
    </DD_Class>
    <!-- End of CRISM_Band Class definition -->
    
    <!-- Beginning of CRISM_Parameters Class definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>CRISM_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.CRISM_Parameters</local_identifier>
        <submitter_name>GEO</submitter_name>
        <definition>The CRISM_Parameters class is the container for CRISM-specific observation parameters.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.observation_type</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.observation_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.observation_number</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.activity_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sensor_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.instrument_pointing_mode</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.scan_mode_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.frame_rate</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.exposure_parameter</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.sampling_mode_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.wavelength_filter</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.wavelength_file_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.pixel_proc_file_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.inv_lookup_table_file_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.CRISM_Hyperspectral_Data_Filter_Control_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.CRISM_Temperatures</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.CRISM_Band</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>*</maximum_occurrences>
        </DD_Association>
    </DD_Class>    
    <!-- End of CRISM_Parameters Class definition -->

    <!-- Beginning of CRISM_ATO_Parameters Class definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>CRISM_ATO_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.CRISM_ATO_Parameters</local_identifier>
        <submitter_name>GEO</submitter_name>
        <definition>The CRISM_ATO_Parameters class is the container for observation parameters specific to the CRISM ATO (Along-Track Oversampled) reprocessing project.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.ato.min_line</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ato.max_line</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ato.min_sample</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.ato.max_sample</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
    </DD_Class>
    <!-- End of CRISM_ATO_Parameters Class definition -->
    
    <!-- Beginning of SHARAD_Observation_Parameters Class definition with attributes in the order as they appear in the label -->    
    <DD_Class> <name>SHARAD_Observation_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.SHARAD_Observation_Parameters</local_identifier>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>
            The SHARAD_Observation_Parameters class provides parameters for SHARAD radar observations.
        </definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.synthetic_aperture_duration</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.multilook_doppler_bandwidth</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.number_of_looks</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.chirp_frequency_envelope</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.range_compression_window</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.azimuth_processing_window</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
    </DD_Class>
    <!-- End of SHARAD_Observation_Parameters Class definition -->
    
    <!-- Beginning of Array_Sampled Class definition with attributes in the order as they appear in the label -->    
    <DD_Class> <name>Array_Sampled</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.Array_Sampled</local_identifier>
        <submitter_name>Jennifer Ward</submitter_name>
        <definition>
            The Array_Sampled class class provides parameters for a uniformly sampled array.
        </definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.array_interval</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.array_unit</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.array_first_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.array_last_value</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.array_scale</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>1</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
    </DD_Class>
    <!-- End of Array_Sampled Class definition -->

    <!-- Beginning of SHARAD_Parameters Class definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>SHARAD_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.SHARAD_Parameters</local_identifier>
        <submitter_name>GEO</submitter_name>
        <definition>The SHARAD_Parameters class contains attributes specific to SHARAD data.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>false</element_flag>
        <DD_Association>
            <identifier_reference>mro.SHARAD_Observation_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>*</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.Array_Sampled</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>*</maximum_occurrences>
        </DD_Association>
    </DD_Class>    
    <!-- End of SHARAD_Parameters Class definition -->
    
    <!-- Beginning of MRO_Parameters Class definition with attributes in the order as they appear in the label -->
    <DD_Class> <name>MRO_Parameters</name>
        <version_id>1.0</version_id>
        <local_identifier>mro.MRO_Parameters</local_identifier>
        <submitter_name>GEO</submitter_name>
        <definition>The MRO_Parameters class is the container for mission-specific metadata elements.</definition>
        <abstract_flag>false</abstract_flag>
        <element_flag>true</element_flag>
        <DD_Association>
            <identifier_reference>mro.product_type</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.product_version_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.release_id</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.observation_rationale</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.orbit_number</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.mission_phase_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spacecraft_clock_count_partition</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spacecraft_clock_start_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.spacecraft_clock_stop_count</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.producer_institution_name</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.line_prefix_bytes</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.line_suffix_bytes</identifier_reference>
            <reference_type>attribute_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.HiRISE_Time_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.HiRISE_Instrument_Setting_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.HiRISE_Temperature_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.HiRISE_Power_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.HiRISE_RDR_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>	
        <DD_Association>
            <identifier_reference>mro.CRISM_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.SHARAD_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
        <DD_Association>
            <identifier_reference>mro.CRISM_ATO_Parameters</identifier_reference>
            <reference_type>component_of</reference_type>
            <minimum_occurrences>0</minimum_occurrences>
            <maximum_occurrences>1</maximum_occurrences>
        </DD_Association>
    </DD_Class>
    <!-- End of MRO_Parameters Class definition -->
    
<!-- End of class definitions -->
    
<!-- Beginning of MRO Mission Dictionary Rules -->
    <DD_Rule>
        <local_identifier>mro.sclk_rule</local_identifier>
        <rule_context>/pds:Product_Observational/pds:Observation_Area/pds:Mission_Area/mro:MRO_Parameters</rule_context>
        
        <DD_Rule_Statement>
            <rule_type>Assert</rule_type>
            <rule_test>if ( 
                            (mro:spacecraft_clock_count_partition) 
                            or 
                            ( (contains(mro:spacecraft_clock_start_count, '/') ) 
                               and
                              (contains(mro:spacecraft_clock_stop_count,'/') ) 
                            ) 
                            or 
                            ( (not (mro:spacecraft_clock_count_partition)) 
                               and (not (mro:spacecraft_clock_start_count)) 
                               and (not (mro:spacecraft_clock_stop_count)) 
                            ) 
                           ) then true() else false() 
            </rule_test>
            <rule_message>
                mro:error:sclk_rule_0: If mro:spacecraft_clock_start_count and mro:spacecraft_clock_stop_count are
                present, they must begin with a partition number followed by a forward slash, OR the partition number must be given by
                mro:spacecraft_clock_count_partition. 
            </rule_message>
            <rule_description>
                If spacecraft_clock_start_count and spacecraft_clock_stop_count are present, they must begin with a
                partition number followed by a forward slash, OR the partition number must be given by spacecraft_clock_count_partition.
            </rule_description>
        </DD_Rule_Statement>
    </DD_Rule>

<!-- End of MRO Mission Dictionary Rules -->
    
</Ingest_LDD>
