<?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_cad2012144zzz_tab</logical_identifier>
    <version_id>1.0</version_id>
    <title>MESSENGER NS Calibration and Diagnostic product: ns_cad2012144zzz_tab</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>2012-05-23T00:00:07.000Z</start_date_time>
      <stop_date_time>2012-05-23T23:59:40.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>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>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/246218673</mess:spacecraft_clock_start_count>
        <mess:spacecraft_clock_stop_count>1/246305046</mess:spacecraft_clock_stop_count>
        <mess:standard_data_product_id>ns_calibration_diagnostic</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_cad2012144zzz.tab</file_name>
      <creation_date_time>2012-05-24T02:43:28Z</creation_date_time>
    </File>
    <Table_Character>
      <offset unit="byte">0</offset>
      <records>191520</records>
      <description>
        This table contains one set of calibration and diagnostic data collected
        from the MESSENGER Neutron Spectrometer (NS). A set is defined as all
        data with timestamps corresponding to a given Earth day. Additional details are
        contained in the EDR SIS document.
      </description>
      <record_delimiter>Carriage-Return Line-Feed</record_delimiter>
      <Record_Character>
        <fields>11</fields>
        <groups>0</groups>
        <record_length unit="byte">80</record_length>
        <Field_Character>
          <name>met</name>
          <field_number>1</field_number>
          <field_location unit="byte">1</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">12</field_length>
          <description>
            Time tag of each event recorded in the 
            Calibration/Diagnostic data packet. All events recorded in a given
            packet will have the same MET time tag value.
          </description>
        </Field_Character>
        <Field_Character>
          <name>orbit_number</name>
          <field_number>2</field_number>
          <field_location unit="byte">15</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</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_Character>
        <Field_Character>
          <name>sequence_ct</name>
          <field_number>3</field_number>
          <field_location unit="byte">22</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>Continuous sequence count for each ApID.</description>
        </Field_Character>
        <Field_Character>
          <name>length</name>
          <field_number>4</field_number>
          <field_location unit="byte">29</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>
            Number of bytes 
            [packet secondary header  + packet data field] - 1.  
            The number of events (N) collected at a given MET is determined by 
            N = (Length-3)/12.
          </description>
        </Field_Character>
        <Field_Character>
          <name>bpp_energy</name>
          <field_number>5</field_number>
          <field_location unit="byte">36</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>Borated Plastic (BP) detector prompt pulse energy.</description>
        </Field_Character>
        <Field_Character>
          <name>bps_energy</name>
          <field_number>6</field_number>
          <field_location unit="byte">43</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>BP detector delayed secondary pulse energy.</description>
        </Field_Character>
        <Field_Character>
          <name>ttsp</name>
          <field_number>7</field_number>
          <field_location unit="byte">50</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">3</field_length>
          <description>Time from first to second pulse for valid BP events.</description>
        </Field_Character>
        <Field_Character>
          <name>data_quality</name>
          <field_number>8</field_number>
          <field_location unit="byte">55</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">3</field_length>
          <description>
            Data quality indicator flags (16 bits, one flag/bit).
            Indicate whether event is in energy range, if pileup is detected, etc.
          </description>
        </Field_Character>
        <Field_Character>
          <name>lg1_energy</name>
          <field_number>9</field_number>
          <field_location unit="byte">60</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>LG1 energy.</description>
        </Field_Character>
        <Field_Character>
          <name>lg2_energy</name>
          <field_number>10</field_number>
          <field_location unit="byte">67</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>LG2 energy.</description>
        </Field_Character>
        <Field_Character>
          <name>status_register</name>
          <field_number>11</field_number>
          <field_location unit="byte">74</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">5</field_length>
          <description>
            Status register. Contains flags allowing determination
            of event type (16 bits, one flag/bit).
          </description>
        </Field_Character>
      </Record_Character>
    </Table_Character>
  </File_Area_Observational>
  <File_Area_Observational_Supplemental>
    <File>
      <file_name>ns_cad2012144zzz.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>
