<?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_ns_raw:data_edr:ns_spe2005139zzz_dat</logical_identifier>
    <version_id>1.0</version_id>
    <title>MESSENGER NS Spectra product: ns_spe2005139zzz_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>2005-05-19T00:01:39.000Z</start_date_time>
      <stop_date_time>2005-05-19T23:59:39.000Z</stop_date_time>
    </Time_Coordinates>
    <Primary_Result_Summary>
      <purpose>Calibration</purpose>
      <processing_level>Raw</processing_level>
    </Primary_Result_Summary>
    <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>Neutron Spectrometer</name>
        <type>Instrument</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument:ns.mess</lid_reference>
          <reference_type>is_instrument</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
    </Observing_System>
    <Target_Identification>
      <name>Earth</name>
      <type>Planet</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:target:planet.earth</lid_reference>
        <reference_type>data_to_target</reference_type>
      </Internal_Reference>
    </Target_Identification>
    <Mission_Area>
      <mess:MESSENGER>
        <mess:mission_phase_name>Earth Cruise</mess:mission_phase_name>
        <mess:spacecraft_clock_start_count>1/024948043</mess:spacecraft_clock_start_count>
        <mess:spacecraft_clock_stop_count>1/025034323</mess:spacecraft_clock_stop_count>
        <mess:standard_data_product_id>ns_spectra</mess:standard_data_product_id>
        <mess:software_name>pipe-ns2edr</mess:software_name>
        <mess:software_version_id>1.0</mess:software_version_id>
      </mess:MESSENGER>
    </Mission_Area>
  </Observation_Area>
  <File_Area_Observational>
    <File>
      <file_name>ns_spe2005139zzz.dat</file_name>
      <creation_date_time>2007-02-17T06:09:58Z</creation_date_time>
    </File>
    <Table_Binary>
      <offset unit="byte">0</offset>
      <records>720</records>
      <description>
        This table contains one set of spectra data, status, and software event
        counters collected from the MESSENGER Neutron Spectrometer (NS). A set is
        defined as all data with time stamps corresponding to a given Earth day.
        Additional details are contained in the EDR SIS document.
      </description>
      <Record_Binary>
        <fields>25</fields>
        <groups>5</groups>
        <record_length unit="byte">378</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>
            Time tag in seconds of the start of the associated
            Reporting/Accumulation period.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>orbit_number</name>
          <field_number>2</field_number>
          <field_location unit="byte">5</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>actual_accum</name>
          <field_number>3</field_number>
          <field_location unit="byte">7</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            Actual accumulation period for software counters and energy histograms.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>sensor_cfg_changed</name>
          <field_number>4</field_number>
          <field_location unit="byte">11</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Sensor Configuration Changed Flag. 
            =0 config unchanged, =1 config changed.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>lg_safing</name>
          <field_number>5</field_number>
          <field_location unit="byte">13</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Maximum Lithium Glass (LG) safing level reached during
            current reporting period. =0 nominal, =1 seeking, =2 level1_rampdown, 
            =3 level1_waiting, =4 level1_seeking, =5 level2_safing.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>bp_safing</name>
          <field_number>6</field_number>
          <field_location unit="byte">15</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            Maximum safing level reached during current reporting
            period for the Borrated Plastic (BP) sensor.
            =0 nominal, =1 seeking, =2 level1_rampdown, 
            =3 level1_waiting, =4 level1_seeking, =5 level2_safing.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>log_compression</name>
          <field_number>7</field_number>
          <field_location unit="byte">17</field_location>
          <data_type>UnsignedMSB2</data_type>
          <field_length unit="byte">2</field_length>
          <description>
            The Log Compression flag identifies when the log compression data mode has
            been enabled. The NS flight software uses 32-bit to 16-bit log compression on software
            counters when the log compression data mode is enabled. See the NS Flight Software
            document for details on the log compression algorithm. 
            =0 no log compression. =1 log compression enabled.
          </description>
        </Field_Binary>
        <Group_Field_Binary>
          <group_number>1</group_number>
          <repetitions>32</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">19</group_location>
          <group_length unit="byte">64</group_length>
          <Field_Binary>
            <name>singles_lg1</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>
              Spectrum is a 32 channel histogram of event energies
              that arrived as a single event with no time correlation to the other
              sensors. LG1 is the Lithium Glass 1 sensor.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>2</group_number>
          <repetitions>32</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">83</group_location>
          <group_length unit="byte">64</group_length>
          <Field_Binary>
            <name>singles_lg2</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>
              Spectrum is a 32 channel histogram of event energies
              that arrived as a single event with no time correlation to the other
              sensors. LG2 is the Lithium Glass 2 sensor.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>3</group_number>
          <repetitions>64</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">147</group_location>
          <group_length unit="byte">128</group_length>
          <Field_Binary>
            <name>singles_bp_spectra</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>
              BP is the Borated Plastic sensor. Spectrum is a 64
              channel histogram of event energies that arrived as a solo event with
              respect to the other sensors.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>4</group_number>
          <repetitions>8</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">275</group_location>
          <group_length unit="byte">16</group_length>
          <Field_Binary>
            <name>tc_early</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>
              The time-correlated early spectrum is a histogram of
              prompt BP events that had a delayed BP event occurring during the early
              capture window, as defined by commandable software parameters provided
              in columns EARLY_CAPTURE_START and EARLY_CAPTURE_END of the NS Status EDR,
              and no additional events in the event set.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
        <Group_Field_Binary>
          <group_number>5</group_number>
          <repetitions>8</repetitions>
          <fields>1</fields>
          <groups>0</groups>
          <group_location unit="byte">291</group_location>
          <group_length unit="byte">16</group_length>
          <Field_Binary>
            <name>tc_late</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>
              The time-correlated late spectrum is a histogram of 
              prompt BP events that had a delayed BP event occurring during the late
              capture window, as defined by commandable software parameters provided
              in columns LATE_CAPTURE_START and LATE_CAPTURE_END of the NS Status EDR,
              and no additional events in the event set.
            </description>
          </Field_Binary>
        </Group_Field_Binary>
        <Field_Binary>
          <name>lg1_raw_events</name>
          <field_number>8</field_number>
          <field_location unit="byte">307</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG1 Raw event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>lg2_raw_events</name>
          <field_number>9</field_number>
          <field_location unit="byte">311</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG2 Raw event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>bp_raw_events</name>
          <field_number>10</field_number>
          <field_location unit="byte">315</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>BP Raw event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>sw_total_events</name>
          <field_number>11</field_number>
          <field_location unit="byte">319</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            Total events processed by software in the current accumulation period.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>dead_time</name>
          <field_number>12</field_number>
          <field_location unit="byte">323</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            Dead time software counter. Units are in
            microseconds/16. Multiply by 16 to get back to microseconds.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>lg1_reset</name>
          <field_number>13</field_number>
          <field_location unit="byte">327</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG1 charge reset software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>lg2_reset</name>
          <field_number>14</field_number>
          <field_location unit="byte">331</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG2 charge reset software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>bp_reset</name>
          <field_number>15</field_number>
          <field_location unit="byte">335</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>BP charge reset software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>bpp_lgxs</name>
          <field_number>16</field_number>
          <field_location unit="byte">339</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            Software counter for prompt pulse in BP detector with
            delayed secondary pulse in LGx detector (x=1 or 2).
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>lg1_over_range</name>
          <field_number>17</field_number>
          <field_location unit="byte">343</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            LG1 prompt over range software counter (pulse height
            larger than maximum specified).
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>lg2_over_range</name>
          <field_number>18</field_number>
          <field_location unit="byte">347</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            LG2 prompt over range software counter (pulse height
            larger than maximum specified).
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>bp_over_range</name>
          <field_number>19</field_number>
          <field_location unit="byte">351</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            BP prompt over range software counter (pulse height
            larger than maximum specified).
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>valid_tc_event</name>
          <field_number>20</field_number>
          <field_location unit="byte">355</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            Time-correlated software counter: non-coincidence and not
            over range events.
          </description>
        </Field_Binary>
        <Field_Binary>
          <name>lg1_bpp_coin</name>
          <field_number>21</field_number>
          <field_location unit="byte">359</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG1/BPP coincidence event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>lg2_bpp_coin</name>
          <field_number>22</field_number>
          <field_location unit="byte">363</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG2/BPP coincidence event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>lg1_bpp_lg2_coin</name>
          <field_number>23</field_number>
          <field_location unit="byte">367</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG1/BPP/LG2 coincidence event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>lg1_bps_coin</name>
          <field_number>24</field_number>
          <field_location unit="byte">371</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG1/BPS coincidence event software counter.</description>
        </Field_Binary>
        <Field_Binary>
          <name>lg2_bps_coin</name>
          <field_number>25</field_number>
          <field_location unit="byte">375</field_location>
          <data_type>UnsignedMSB4</data_type>
          <field_length unit="byte">4</field_length>
          <description>LG2/BPS coincidene event software counter.</description>
        </Field_Binary>
      </Record_Binary>
    </Table_Binary>
  </File_Area_Observational>
  <File_Area_Observational_Supplemental>
    <File>
      <file_name>ns_spe2005139zzz.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>
