<?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_cac2011237zzz_dat</logical_identifier>
    <version_id>1.0</version_id>
    <title>MESSENGER GRS Anti-Coincidence Spectra Product: grs_cac2011237zzz_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>2011-08-25T00:07:12.555Z</start_date_time>
      <stop_date_time>2011-08-25T23:47:18.557Z</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</mess:mission_phase_name>
        <mess:spacecraft_clock_start_count>1/222718300</mess:spacecraft_clock_start_count>
        <mess:spacecraft_clock_stop_count>1/222803506</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>hpge</mess:detector_id>
      </mess:MESSENGER>
    </Mission_Area>
  </Observation_Area>
  <File_Area_Observational>
    <File>
      <file_name>grs_cac2011237zzz.dat</file_name>
      <creation_date_time>2015-09-21T14:47:22Z</creation_date_time>
    </File>
    <Table_Binary>
      <offset unit="byte">0</offset>
      <records>296</records>
      <description>
        This table contains one set of Anti-Coincident (AC) 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 timestamps corresponding to
        a given day of year.
      </description>
      <Record_Binary>
        <fields>58</fields>
        <groups>1</groups>
        <record_length unit="byte">65831</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 HPGE 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>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 HPGe 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>missing_data_packets</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>
            The value represents a 16-bit binary number where each bit indicates whether an HPGe Raw telemetry packet is missing from the EDR. 
            Each HPGe Raw EDR consists of information extracted from 16 telemetry packets in a complete observation. The least significant bit 
            is a flag corresponding to the first of 16 packets and the most significant bit is a flag corresponding to the 16th packet. A bit 
            value of 1 indicates that a given packet is missing from the EDR. For example, a value of 0 in this column indicates that the 
            spectra from all 16 packets have been downloaded and included in the HPGE_RAW spectra for this EDR. A value of 3 indicates that 
            the spectra information from the first and second packets are missing and therefore spectral bins 0-2047 should be discounted 
            from analysis of the HPGE_RAW spectra.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>bad_data_flag</name>
          <field_number>9</field_number>
          <field_location unit="byte">23</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>
        <Group_Field_Binary>
          <group_number>1</group_number>
          <repetitions>16384</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">25</group_location>
          <group_length unit="byte">65536</group_length>
          <Field_Binary>
            <name>cal_ac</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>
              Anti-coincident (AC) spectra accumulated by the HPGe detector. 
              Contains the corrected counts in each of the 16384 bins after 1 accumulation period.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
        <Field_Binary>
          <name>utc_midpoint_met</name>
          <field_number>10</field_number>
          <field_location unit="byte">65561</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>11</field_number>
          <field_location unit="byte">65584</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>12</field_number>
          <field_location unit="byte">65592</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>13</field_number>
          <field_location unit="byte">65600</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>14</field_number>
          <field_location unit="byte">65608</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>15</field_number>
          <field_location unit="byte">65616</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>16</field_number>
          <field_location unit="byte">65624</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>17</field_number>
          <field_location unit="byte">65632</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>18</field_number>
          <field_location unit="byte">65640</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>19</field_number>
          <field_location unit="byte">65648</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>20</field_number>
          <field_location unit="byte">65649</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>21</field_number>
          <field_location unit="byte">65650</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>22</field_number>
          <field_location unit="byte">65651</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>23</field_number>
          <field_location unit="byte">65652</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>24</field_number>
          <field_location unit="byte">65660</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>25</field_number>
          <field_location unit="byte">65668</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>hpge_temp_1</name>
          <field_number>26</field_number>
          <field_location unit="byte">65676</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Channel 00, HPGE Detector Temperature 1, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hpge_temp_2</name>
          <field_number>27</field_number>
          <field_location unit="byte">65684</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Channel 01, HPGE Detector Temperature 2, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>calib_avg_det_temp</name>
          <field_number>28</field_number>
          <field_location unit="byte">65692</field_location>
          <data_type>IEEE754MSBDouble</data_type>
          <field_length unit="byte">8</field_length>
          <description>Calibrated, averaged detector temperature, smoothed and interpolated to the center of the collection interval.</description>
        </Field_Binary>
        <Field_Binary>
          <name>preamp_temp</name>
          <field_number>29</field_number>
          <field_location unit="byte">65700</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>30</field_number>
          <field_location unit="byte">65708</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>31</field_number>
          <field_location unit="byte">65716</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>32</field_number>
          <field_location unit="byte">65724</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>33</field_number>
          <field_location unit="byte">65728</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>34</field_number>
          <field_location unit="byte">65732</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Counter for accumulated dead time.</description>
        </Field_Binary>
        <Field_Binary>
          <name>hpge_charge_resets</name>
          <field_number>35</field_number>
          <field_location unit="byte">65736</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Number of HPGe charge resets.</description>
        </Field_Binary>
        <Field_Binary>
          <name>shield_charge_resets</name>
          <field_number>36</field_number>
          <field_location unit="byte">65740</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Number of SHIELD charge resets.</description>
        </Field_Binary>
        <Field_Binary>
          <name>all_events</name>
          <field_number>37</field_number>
          <field_location unit="byte">65744</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>total count of gamma events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>all_ch0_ch1_events</name>
          <field_number>38</field_number>
          <field_location unit="byte">65748</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>All channel 0 and channel 1 events. Excludes inverted Channel 0, Pileups, and Pulser events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>all_ch0_events</name>
          <field_number>39</field_number>
          <field_location unit="byte">65752</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>All single Channel 0 events - either singlet or fails crossing time criterion.</description>
        </Field_Binary>
        <Field_Binary>
          <name>all_ch1_events</name>
          <field_number>40</field_number>
          <field_location unit="byte">65756</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>All single Channel 1 events - either singlet or fails crossing time criterion.</description>
        </Field_Binary>
        <Field_Binary>
          <name>invalid_single_ch0</name>
          <field_number>41</field_number>
          <field_location unit="byte">65760</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Single channel 0 out-of-range events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>invalid_single_ch1</name>
          <field_number>42</field_number>
          <field_location unit="byte">65764</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Single channel 1 out-of-range events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>invalid_coincident_ch0</name>
          <field_number>43</field_number>
          <field_location unit="byte">65768</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Channel 0 out-of-range coincidence events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>invalid_coincident_ch1</name>
          <field_number>44</field_number>
          <field_location unit="byte">65772</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Channel 1 out-of-range coincidence events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>valid_single_ch0</name>
          <field_number>45</field_number>
          <field_location unit="byte">65776</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Single channel 0 valid events only.</description>
        </Field_Binary>
        <Field_Binary>
          <name>valid_coincident_ch0</name>
          <field_number>46</field_number>
          <field_location unit="byte">65780</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Coincidence channel 0 valid events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>valid_single_ch1</name>
          <field_number>47</field_number>
          <field_location unit="byte">65784</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Single channel 1 valid events only.</description>
        </Field_Binary>
        <Field_Binary>
          <name>valid_coincident_ch1</name>
          <field_number>48</field_number>
          <field_location unit="byte">65788</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Coincidence channel 1 valid events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>all_valid_coincident</name>
          <field_number>49</field_number>
          <field_location unit="byte">65792</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>All valid coincidence events - both Channel 0 and Channel 1 valid.</description>
        </Field_Binary>
        <Field_Binary>
          <name>inverted_ch0</name>
          <field_number>50</field_number>
          <field_location unit="byte">65796</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Channel 0 events flagged 'inverted' by the hardware.</description>
        </Field_Binary>
        <Field_Binary>
          <name>ch0_pileup_reject</name>
          <field_number>51</field_number>
          <field_location unit="byte">65800</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Channel 0 pileup rejected events. Only if pileup rejection is enabled.</description>
        </Field_Binary>
        <Field_Binary>
          <name>fifo_full_count</name>
          <field_number>52</field_number>
          <field_location unit="byte">65804</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Hardware FIFO full flag tested for all events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>pulser_energy_sum</name>
          <field_number>53</field_number>
          <field_location unit="byte">65808</field_location>
          <data_type>SignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Pulser energy sum. Summation of (Pulser Energy - Offset).</description>
        </Field_Binary>
        <Field_Binary>
          <name>pulser_energy_sum2</name>
          <field_number>54</field_number>
          <field_location unit="byte">65812</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Pulser energy sum squared. Summation of square of (Pulser Energy - Offset).</description>
        </Field_Binary>
        <Field_Binary>
          <name>pulser_events</name>
          <field_number>55</field_number>
          <field_location unit="byte">65816</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Number of valid pulser events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>invalid_pulser_events</name>
          <field_number>56</field_number>
          <field_location unit="byte">65820</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Out-of-range pulser events.</description>
        </Field_Binary>
        <Field_Binary>
          <name>neutron_events</name>
          <field_number>57</field_number>
          <field_location unit="byte">65824</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Coincidence events that meet neutron criterion.</description>
        </Field_Binary>
        <Field_Binary>
          <name>pulser_offset</name>
          <field_number>58</field_number>
          <field_location unit="byte">65828</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>Pulser energy offset used to form PULSER_ENERGY_SUM and PULSER_ENERGY_SUM2.</description>
        </Field_Binary>
      </Record_Binary>
    </Table_Binary>
  </File_Area_Observational>
  <File_Area_Observational_Supplemental>
    <File>
      <file_name>grs_cac2011237zzz.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>
