<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<?xml-model href="https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1A10.sch"
  schematypens="http://purl.oclc.org/dsdl/schematron"?>
<?xml-model href="https://pds.nasa.gov/pds4/mission/mess/v1/PDS4_MESS_1B00_1020.sch"
  schematypens="http://purl.oclc.org/dsdl/schematron"?>

<Product_Observational xmlns="http://pds.nasa.gov/pds4/pds/v1" 
    xmlns:mess="http://pds.nasa.gov/pds4/mission/mess/v1" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="http://pds.nasa.gov/pds4/pds/v1 https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1A10.xsd   http://pds.nasa.gov/pds4/mission/mess/v1 https://pds.nasa.gov/pds4/mission/mess/v1/PDS4_MESS_1B00_1020.xsd">
  <Identification_Area>
    <logical_identifier>urn:nasa:pds:mess_grs_raw:data_edr:grs_shi2014246zzz_dat</logical_identifier>
    <version_id>1.0</version_id>
    <title>MESSENGER GRS Shield Spectra product: grs_shi2014246zzz_dat</title>
    <information_model_version>1.10.1.0</information_model_version>
    <product_class>Product_Observational</product_class>
    <Modification_History>
      <Modification_Detail>
        <modification_date>2018-06-08</modification_date>
        <version_id>1.0</version_id>
        <description>PDS4 migrated product</description>
      </Modification_Detail>
    </Modification_History>
  </Identification_Area>
  <Observation_Area>
    <Time_Coordinates>
      <start_date_time>2014-09-03T00:15:43.000Z</start_date_time>
      <stop_date_time>2014-09-03T23:52:13.000Z</stop_date_time>
    </Time_Coordinates>
    <Investigation_Area>
      <name>MESSENGER</name>
      <type>Mission</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:investigation:mission.messenger</lid_reference>
        <reference_type>data_to_investigation</reference_type>
      </Internal_Reference>
    </Investigation_Area>
    <Observing_System>
      <Observing_System_Component>
        <name>MESSENGER</name>
        <type>Spacecraft</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument_host:spacecraft.mess</lid_reference>
          <reference_type>is_instrument_host</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
      <Observing_System_Component>
        <name>Gamma Ray Spectrometer</name>
        <type>Instrument</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument:grs.mess</lid_reference>
          <reference_type>is_instrument</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
    </Observing_System>
    <Target_Identification>
      <name>Mercury</name>
      <type>Planet</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:target:planet.mercury</lid_reference>
        <reference_type>data_to_target</reference_type>
      </Internal_Reference>
    </Target_Identification>
    <Mission_Area>
      <mess:MESSENGER>
        <mess:mission_phase_name>Mercury Orbit Year 4</mess:mission_phase_name>
        <mess:spacecraft_clock_start_count>2/052027342</mess:spacecraft_clock_start_count>
        <mess:spacecraft_clock_stop_count>2/052112332</mess:spacecraft_clock_stop_count>
        <mess:standard_data_product_id>grs_shield_spectra_2</mess:standard_data_product_id>
        <mess:software_name>pipe-grs2edr</mess:software_name>
        <mess:software_version_id>1.1</mess:software_version_id>
        <mess:detector_id>shield</mess:detector_id>
      </mess:MESSENGER>
    </Mission_Area>
  </Observation_Area>
  <File_Area_Observational>
    <File>
      <file_name>grs_shi2014246zzz.dat</file_name>
      <creation_date_time>2014-09-04T16:47:00Z</creation_date_time>
    </File>
    <Table_Binary>
      <offset unit="byte">0</offset>
      <records>948</records>
      <description>
        This table contains one set of raw spectra collected from the SHIELD
        detector, MESSENGER Gamma Ray Spectrometer (GRS). A set is defined as
        all data with MET timestamps corresponding to a given Earth day.
        Additional details are contained in the EDR SIS document.
      </description>
      <Record_Binary>
        <fields>8</fields>
        <groups>1</groups>
        <record_length unit="byte">2070</record_length>
        <Field_Binary>
          <name>met</name>
          <field_number>1</field_number>
          <field_location unit="byte">1</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            Mission elapsed time, in seconds, corresponding to the 
            start of the accumulation period for the spectra.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>accum_time</name>
          <field_number>2</field_number>
          <field_location unit="byte">5</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Accumulation time, in seconds, of the HPGe detector.</description>
        </Field_Binary>
        <Field_Binary>
          <name>midpoint_met</name>
          <field_number>3</field_number>
          <field_location unit="byte">9</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            The mission elapsed time at the midpoint of the 
            observation. Defined as:
            MET at the start of the observation +  (ACCUM_TIME / 2).
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>orbit_number</name>
          <field_number>4</field_number>
          <field_location unit="byte">13</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Orbit number is a unique identifier for a given orbit of
            the MESSENGER spacecraft around Mercury. Orbit number is defined as
            starting at apoherm and is calculated using the MET value and the
            appropriate SPICE kernels. Orbit numbering does not start until MESSENGER
            performs the Mercury orbit insertion. Until that time the value for orbit
            number is 0.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>start_bin</name>
          <field_number>5</field_number>
          <field_location unit="byte">15</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>Start Bin of the Shield detector.</description>
        </Field_Binary>
        <Field_Binary>
          <name>number_of_bins</name>
          <field_number>6</field_number>
          <field_location unit="byte">17</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>Number of bins in the raw spectra.</description>
        </Field_Binary>
        <Field_Binary>
          <name>grs_priority_level</name>
          <field_number>7</field_number>
          <field_location unit="byte">19</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Indicates the type of priority assigned to the science
            packet. The priority level is tied to the ApID of the packet. Priority
            level varies from 0-3, 0 being highest and 3 being lowest priority.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>bad_data_flag</name>
          <field_number>8</field_number>
          <field_location unit="byte">21</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Intended for use as a bit-string bad data flag to indicate
            specific problems associated with the data. Values are expected to be 
            assigned to specific bits as problems are identified during the course of
            the mission. Currently no values have been assigned and will default to a
            value of zero.
          </description>
        </Field_Binary>
        <Group_Field_Binary>
          <group_number>1</group_number>
          <repetitions>1024</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">23</group_location>
          <group_length unit="byte">2048</group_length>
          <Field_Binary>
            <name>shield</name>
            <field_number>1</field_number>
            <field_location unit="byte">1</field_location>
            <data_type>UnsignedMSB2</data_type>
            <field_length unit="byte">2</field_length>
            <description>
              Contains a set of data values as defined by the Appendix
              SHIELD 2 Content Description in the EDR SIS.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
      </Record_Binary>
    </Table_Binary>
  </File_Area_Observational>
  <File_Area_Observational_Supplemental>
    <File>
      <file_name>grs_shi2014246zzz.lbl</file_name>
    </File>
    <Stream_Text>
      <offset unit="byte">0</offset>
      <parsing_standard_id>PDS3</parsing_standard_id>
      <description>Original PDS3 label</description>
      <record_delimiter>Carriage-Return Line-Feed</record_delimiter>
    </Stream_Text>
  </File_Area_Observational_Supplemental>
</Product_Observational>
