<?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_derived:data_cdr:grs_cs22012173zzz_dat</logical_identifier>
    <version_id>1.0</version_id>
    <title>MESSENGER GRS Shield Spectra Product: grs_cs22012173zzz_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-07-03</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>2012-06-21T00:00:02.912Z</start_date_time>
      <stop_date_time>2012-06-21T23:59:10.913Z</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 2</mess:mission_phase_name>
        <mess:spacecraft_clock_start_count>1/248724268</mess:spacecraft_clock_start_count>
        <mess:spacecraft_clock_stop_count>1/248810616</mess:spacecraft_clock_stop_count>
        <mess:software_name>grs_cdr_gen</mess:software_name>
        <mess:software_version_id>1.0</mess:software_version_id>
        <mess:detector_id>shield</mess:detector_id>
      </mess:MESSENGER>
    </Mission_Area>
  </Observation_Area>
  <File_Area_Observational>
    <File>
      <file_name>grs_cs22012173zzz.dat</file_name>
      <creation_date_time>2015-09-21T15:54:58Z</creation_date_time>
    </File>
    <Table_Binary>
      <offset unit="byte">0</offset>
      <records>318</records>
      <description>
        This table contains one set of Shield (SHI) spectra
        collected from the high purity Germanium (HPGe) detector plus
        spatial and temporal information and relevant engineering and
        counter and pulser data from the time the spectra was taken.
        A set is defined as all data with time stamps corresponding to
        a given day of year.
      </description>
      <Record_Binary>
        <fields>41</fields>
        <groups>4</groups>
        <record_length unit="byte">1245</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 Shield 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 shield Raw 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>initial_energy</name>
          <field_number>5</field_number>
          <field_location unit="byte">15</field_location>
          <data_type>IEEE754MSBSingle</data_type>
          <field_length unit="byte">4</field_length>
          <description>The energy of the middle of the first bin of the FAST and THERMAL NEURTON HPGE spectra.</description>
        </Field_Binary>
        <Field_Binary>
          <name>grs_priority_level</name>
          <field_number>6</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>7</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. 
            Bit 1  - The high voltage is not on, is being ramped or has not been stable long enough. 
            Bit 2  - Indicates a change in the analog pulse processing system gain setting. 
            Bit 3  - Indicates a spectrum where the temperatures used for correction have fluctuated by greater 
                     than 5 percent from previous readings. 
            Bit 4  - Indicates gamma spectra collected during a solar particle event. These spectra should not 
                     be combined with spectra collected under normal solar conditions. 
            Bit 5  - Pulser data is not combined with the spectrum. 
            Bit 6  - Indicates gamma spectra collected during a solar flare event. These spectra should not be 
                     combined with spectra collected under normal solar conditions. 
            Bit 7  - Indicates gamma spectra collected during periods of decreased GS detector spectral resolution. 
                     These spectra should not be combined with spectra collected under 'normal' detector conditions. 
            Bit 8  - Not all data channels were received on the ground. 
            Bit 9  - Indicates a unique problem with single spectrum. 
            Bit 10 - The high voltage has not been stable long enough. 
            Bit 11 - This data was taken during a time when the spectra were particularly noisy. Many channels 
                     have far too many counts, especially the lower channels.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>num_buffered_events</name>
          <field_number>8</field_number>
          <field_location unit="byte">23</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            The number of bytes in the raw event buffer. The number of events in the raw event 
            buffer is (Raw Bytes-16)/8. The number of raw events in the buffer will range from 
            0 to 126. Note there must be at least one event in the buffer before the Event Buffer 
            Header will be generated.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>num_raw_events</name>
          <field_number>9</field_number>
          <field_location unit="byte">25</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            This value contains a count of the total number of raw events detected and is not limited 
            by the length of the buffer. This counter will rollover if the count exceeds 65535.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>zct_thermal_min</name>
          <field_number>10</field_number>
          <field_location unit="byte">27</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Window parameter that sets the minimum acceptable time difference between shield and HpGe 
            triggers for an event to be considered a thermal neutron. Units are 100 ns/tick. 
            Parameter is inclusive, i.e., values equal to this parameter are accepted.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>zct_therm_max</name>
          <field_number>11</field_number>
          <field_location unit="byte">29</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Window parameter that sets the maximum acceptable time difference between shield and HpGe triggers 
            for an event to be considered a thermal neutron. Units are 100 ns/tick. Parameter is exclusive, 
            i.e., values equal to this parameter are rejected
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>zct_fast_min</name>
          <field_number>12</field_number>
          <field_location unit="byte">31</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Window parameter that sets the minimum acceptable time difference between shield and HpGe triggers 
            for an event to be considered a fast neutron. Units are 100 ns/tick. Parameter is inclusive, i.e., 
            values equal to this parameter are accepted.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>zct_fast_max</name>
          <field_number>13</field_number>
          <field_location unit="byte">33</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Window parameter that sets the maximum time difference between shield and HpGe triggers for an event 
            to be considered a fast neutron. Units are 100 ns/tick. Parameter is exclusive, i.e., values equal to 
            this parameter are rejected.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>shield_shifts_raw</name>
          <field_number>14</field_number>
          <field_location unit="byte">35</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            The number of right shifts (divide by 2s) that are applied to raw shield pulse heights prior to binning 
            in the Shield All Events spectrum. Possible values are 2 or 3. A value of two effectively increases the 
            binning resolution but decreases the dynamic range (maximum binned energy).
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>shield_shifts_neutron</name>
          <field_number>15</field_number>
          <field_location unit="byte">37</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            The number of right shifts (divide by 2s) that are applied to raw shield pulse heights prior to binning 
            in either the Shield Thermal Events spectrum or the Shield Fast Events spectrum. Possible values are 2 
            or 3. A value of two effectively increases the binning resolution but decreases the dynamic range (maximum binned energy).
          </description>
        </Field_Binary>
        <Group_Field_Binary>
          <group_number>1</group_number>
          <repetitions>64</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">39</group_location>
          <group_length unit="byte">256</group_length>
          <Field_Binary>
            <name>hpge_thermal</name>
            <field_number>1</field_number>
            <field_location unit="byte">1</field_location>
            <data_type>IEEE754MSBSingle</data_type>
            <field_length unit="byte">4</field_length>
            <description>Thermal Neutron spectrum about the 478-keV line, normalized to 0.60 keV energy bins.</description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>2</group_number>
          <repetitions>64</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">295</group_location>
          <group_length unit="byte">256</group_length>
          <Field_Binary>
            <name>hpge_fast</name>
            <field_number>1</field_number>
            <field_location unit="byte">1</field_location>
            <data_type>IEEE754MSBSingle</data_type>
            <field_length unit="byte">4</field_length>
            <description>Fast Neutron spectrum about the 478-keV line, normalized to 0.60 keV energy bins.</description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>3</group_number>
          <repetitions>128</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">551</group_location>
          <group_length unit="byte">256</group_length>
          <Field_Binary>
            <name>shield_thermal</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>Raw Thermal Neutron spectrum about the 478-keV line.</description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>4</group_number>
          <repetitions>128</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">807</group_location>
          <group_length unit="byte">256</group_length>
          <Field_Binary>
            <name>shield_fast</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>Raw Fast Neutron spectrum about the 478-keV line.</description>
          </Field_Binary>
        </Group_Field_Binary>
        <Field_Binary>
          <name>utc_midpoint_met</name>
          <field_number>16</field_number>
          <field_location unit="byte">1063</field_location>
          <data_type>ASCII_String</data_type>
          <field_length unit="byte">23</field_length>
          <description>midpoint_met converted to UTC, stored as yyyy-mm-ddThh:mm:ss.sss.</description>
        </Field_Binary>
        <Field_Binary>
          <name>mercury_centric_latitude</name>
          <field_number>17</field_number>
          <field_location unit="byte">1086</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Sub spacecraft latitude in Mercury fixed coordinates at the middle of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>mercury_centric_longitude</name>
          <field_number>18</field_number>
          <field_location unit="byte">1094</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>
            Sub spacecraft longitude in Mercury fixed coordinates at the middle of 
            the collection interval. Longitude increases towards the East.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>instr_boresight_mercury_x</name>
          <field_number>19</field_number>
          <field_location unit="byte">1102</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Sub instrument boresight (x component) in Mercury fixed coordinates at the middle of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>instr_boresight_mercury_y</name>
          <field_number>20</field_number>
          <field_location unit="byte">1110</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Sub instrument boresight (y component) in Mercury fixed coordinates at the middle of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>instr_boresight_mercury_z</name>
          <field_number>21</field_number>
          <field_location unit="byte">1118</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Sub instrument boresight (z component) in Mercury fixed coordinates at the middle of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>scalt</name>
          <field_number>22</field_number>
          <field_location unit="byte">1126</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>
            Mercury centric altitude of the sub-spacecraft point in Mercury-fixed 
            rotating frame at the middle of the collection interval.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>delta_angle</name>
          <field_number>23</field_number>
          <field_location unit="byte">1134</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Difference between instrument +y direction and true north at the middle of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>mercury_sol</name>
          <field_number>24</field_number>
          <field_location unit="byte">1142</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>
            Longitude of the Sun at 0 hours UT on the date of the record. 
            Taken from the Association of Lunar and Planetary Observers 
            'Ephemeris for Physical Observation of Mercury'.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>local_hour</name>
          <field_number>25</field_number>
          <field_location unit="byte">1150</field_location>
          <data_type>UnsignedByte</data_type>
          <field_length unit="byte">1</field_length>
          <description>Local Sun hour at the sub-spacecraft point.</description>
        </Field_Binary>
        <Field_Binary>
          <name>local_minute</name>
          <field_number>26</field_number>
          <field_location unit="byte">1151</field_location>
          <data_type>UnsignedByte</data_type>
          <field_length unit="byte">1</field_length>
          <description>Local Sun minute at the sub-spacecraft point.</description>
        </Field_Binary>
        <Field_Binary>
          <name>pointing</name>
          <field_number>27</field_number>
          <field_location unit="byte">1152</field_location>
          <data_type>UnsignedByte</data_type>
          <field_length unit="byte">1</field_length>
          <description>True if pointing data was available.</description>
        </Field_Binary>
        <Field_Binary>
          <name>intersecting</name>
          <field_number>28</field_number>
          <field_location unit="byte">1153</field_location>
          <data_type>UnsignedByte</data_type>
          <field_length unit="byte">1</field_length>
          <description>True if the pointing vector intersects Mercury.</description>
        </Field_Binary>
        <Field_Binary>
          <name>nadir_angle</name>
          <field_number>29</field_number>
          <field_location unit="byte">1154</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>
            Spacecraft attitude during orbits and flybys is defined by two additional coordinate systems, 
            the GRS LVLH (Local Vertical Local Horizontal) frame and the spacecraft fixed frame, and by the 
            rotation of the spacecraft frame with respect to the GRS LVLH frame. In the GRS LVLH frame, the 
            Z axis is aligned with the vector from the spacecraft to the planet center (the nadir direction), 
            the Y axis is the negative of the cross product of the position and velocity vectors, and the 
            X axis points in the instantaneous direction of motion, completing a right-handed coordinate 
            system. The Z axis is along the viewing direction of the instrument deck inside the adapter 
            ring and of the GRS just outside the adapter ring, the Y axis is directed from the spacecraft 
            along the magnetometer boom, and the X-axis is parallel to the solar panel booms, forming a 
            right-handed coordinate system. The spacecraft attitude is specified by the rotation of the 
            spacecraft fixed frame Z axis in the GRS LVLH frame and a twist angle about the Z axis. The 
            Z axis rotation is given by a nadir angle and an azimuth angle, where the nadir angle is 
            0 degrees when the spacecraft Z axis points along the + Z LVLH axis and 180 degrees when it 
            points along -Z in the LVLH frame, and the LVLH azimuth angle is measured counterclockwise 
            about the Z LVLH axis from the X LVLH axis. The twist angle is measured positive about the 
            +Z spacecraft axis. See section 5.4.2 in the GRS_CDR_SIS for further details.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>azimuth</name>
          <field_number>30</field_number>
          <field_location unit="byte">1162</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>
            Spacecraft attitude during orbits and flybys is defined by two additional coordinate systems, 
            the GRS LVLH (Local Vertical Local Horizontal) frame and the spacecraft fixed frame, and by 
            the rotation of the spacecraft frame with respect to the GRS LVLH frame. In the GRS LVLH frame, 
            the Z axis is aligned with the vector from the spacecraft to the planet center (the nadir direction), 
            the Y axis is the negative of the cross product of the position and velocity vectors, and the 
            X axis points in the instantaneous direction of motion, completing a right-handed coordinate 
            system. The Z axis is along the viewing direction of the instrument deck inside the adapter 
            ring and of the GRS just outside the adapter ring, the Y axis is directed from the spacecraft 
            along the magnetometer boom, and the X-axis is parallel to the solar panel booms, forming a 
            right-handed coordinate system. The spacecraft attitude is specified by the rotation of the 
            spacecraft fixed frame Z axis in the GRS LVLH frame and a twist angle about the Z axis. The 
            Z axis rotation is given by a nadir angle and an azimuth angle, where the nadir angle is 
            0 degrees when the spacecraft Z axis points along the + Z LVLH axis and 180 degrees when 
            it points along -Z in the LVLH frame, and the LVLH azimuth angle is measured counterclockwise 
            about the Z LVLH axis from the X LVLH axis. The twist angle is measured positive about the 
            +Z spacecraft axis. See section 5.4.2 in the GRS_CDR_SIS for further details.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>twist_angle</name>
          <field_number>31</field_number>
          <field_location unit="byte">1170</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>
            Spacecraft attitude during orbits and flybys is defined by two additional coordinate systems, 
            the GRS LVLH (Local Vertical Local Horizontal) frame and the spacecraft fixed frame, and by the 
            rotation of the spacecraft frame with respect to the GRS LVLH frame. In the GRS LVLH frame, the 
            Z axis is aligned with the vector from the spacecraft to the planet center (the nadir direction), 
            the Y axis is the negative of the cross product of the position and velocity vectors, and the 
            X axis points in the instantaneous direction of motion, completing a right-handed coordinate 
            system. The Z axis is along the viewing direction of the instrument deck inside the adapter 
            ring and of the GRS just outside the adapter ring, the Y axis is directed from the spacecraft 
            along the magnetometer boom, and the X-axis is parallel to the solar panel booms, forming a 
            right-handed coordinate system. The spacecraft attitude is specified by the rotation of the 
            spacecraft fixed frame Z axis in the GRS LVLH frame and a twist angle about the Z axis. The 
            Z axis rotation is given by a nadir angle and an azimuth angle, where the nadir angle is 0 degrees 
            when the spacecraft Z axis points along the + Z LVLH axis and 180 degrees when it points along 
            -Z in the LVLH frame, and the LVLH azimuth angle is measured counterclockwise about the Z LVLH 
            axis from the X LVLH axis. The twist angle is measured positive about the +Z spacecraft axis. 
            See section 5.4.2 in the GRS_CDR_SIS for further details.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>ad_temp</name>
          <field_number>32</field_number>
          <field_location unit="byte">1178</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Channel 06, AD Temperature, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hvps_temp</name>
          <field_number>33</field_number>
          <field_location unit="byte">1186</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>HVPS Temperature, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hvps_volt</name>
          <field_number>34</field_number>
          <field_location unit="byte">1194</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>HVPS Voltage, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hvps_ref_volt</name>
          <field_number>35</field_number>
          <field_location unit="byte">1202</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>HVPS Reference Voltage, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>preamp_temp</name>
          <field_number>36</field_number>
          <field_location unit="byte">1210</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Channel 04, Pre Amp Temperature, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>shaper_temp</name>
          <field_number>37</field_number>
          <field_location unit="byte">1218</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Channel 05, Shaper Temperature, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hv_monitor</name>
          <field_number>38</field_number>
          <field_location unit="byte">1226</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Channel 07, HV Monitor, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hpge_raw_events</name>
          <field_number>39</field_number>
          <field_location unit="byte">1234</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Counter of HPGe Raw events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>shield_raw_events</name>
          <field_number>40</field_number>
          <field_location unit="byte">1238</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Counter for SHIELD raw events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>accumulated_dead_time</name>
          <field_number>41</field_number>
          <field_location unit="byte">1242</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Counter for accumulated dead time.</description>
        </Field_Binary>
      </Record_Binary>
    </Table_Binary>
  </File_Area_Observational>
  <File_Area_Observational_Supplemental>
    <File>
      <file_name>grs_cs22012173zzz.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>
