Data Product Overview :+Every 2.048 seconds Diviner collects a data 'frame' containing the following:* 16 sets of science data, with each set containing 192 sixteen-bit  science measurements from the focal plane interface electronics  obtained over integration periods of 0.128 seconds* A single set of instrument engineering and housekeeping  measurements (or 'engineering data')The data are downlinked to the LRO Ground Data System (GDS) and are pushed to the Diviner SOC at the end of each downlink pass. Diviner software assembles the telemetry files into EDR data tables, each covering a one-hour time period.Each Diviner EDR data product will consist of two files. The first file is an ASCII formatted detached PDS label. The second file is the ASCII data table file.Each ASCII record contains 2656 bytes, and there will be a record every 0.128 seconds (unless there is a data gap; time periods which contain no data will not produce data records). Each one-hour Diviner EDR ASCII data table will be up to approximately 75 MB. The volume of the EDR data product will be up to approximately 1800 MB per day.While there is only a single set of engineering data for the 16 sets of science data, it is known during which of the 16 science data sets a given engineering measurement was taken. In the EDR, the engineering data are propagated across each science data set for a completely uniform and flat file. Each engineering measurement will contain a valid value during the appropriate science data set, and the UNKNOWN_CONSTANT (-9999) during the other science data sets where engineering data were not obtained.In the ASCII data tables, each complete set of science data plus engineering data is considered a 'record', and is contained on a single line. Where a data measurement is not valid or applicable, the UNKNOWN_CONSTANT will be found.Data Processing Level:This document uses the Committee on Data Management and Computation (CODMAC) data level numbering system to describe the processing level of the EDR data product. Diviner EDR data products are considered CODMAC 'Level 2', equivalent to NASA level 0. The EDR data files are generated from CODMAC Level 1 or 'Raw Data', which are the telemetry packets within the project specific Standard Formatted Data Unit (SFDU) record. Data Product Generation :The Diviner EDR data products will be generated by the Diviner Instrument Team at JPL. The EDR data products will be reconstructed from telemetry data products and formatted according to the EDR SIS. Meta-data acquired from the telemetry data headers will be used to populate the PDS label. The PDS archives will be assembled and delivered to the PDS from UCLA.Data Flow :Diviner science and engineering telemetry are transferred to the Diviner JPL SOC. Once transferred, the Diviner software automatically processes the telemetry into Level 0 EDR data products. The Diviner EDR data products are then archived locally at the Diviner operation center. After an initial data validation period, the Diviner team will assemble the data products and ancillary files into archive volumes and will transfer the assembled volume to the PDS Geosciences Node. The Diviner EDR archive will be made available via data releases scheduled at three month intervals as specified in the Lunar Reconnaissance Orbiter Project Data Management andArchive Plan.For more information please see the document DP_SIS.HTM(HTML format) or DP_SIS.PDF (Adobe Acrobat format) locatedin the DOCUMENT directory of this archive.

Overview: With respect to the EDR data, the data exists in 2 states -- Absent or Present. For the data that is present, the confidence level is high due to simplicity of the processing and structure of the data.The quality flag (column 1) has limited meaning for the EDRrecords. A value of 0 indicates present and completely validdata; a value of 1 indicates a record header line.Individual columns in the data records will contain theUNKNOWN_CONSTANT (-9999) where data is missing or unknown. Review:This archival data set was examined by a peer review panel prior to its acceptance by the Planetary Data System (PDS). The peer review was conducted in accordance with PDS procedures.Prior to creation of the final version of the archival data set, key elements of the archive were distributed for preliminary review. These included electronic versions of example PDS labels, CATALOG files, and Software Interface Specifications (SISs). These materials were distributed to PDS personnel, the experiment investigator, and others, as appropriate.Data Coverage and Quality:The Diviner instrument has a 98% data return rate of expected data.Data loss is typically seen during data transmission or spacecraft and instrument anomalies. Diviner performed a Warm Reset after failing to see a valid equator crossing from LRO on August 22, 2009. The Warm Reset was needed to clear the bad equator crossing value. Diviner lost a few soundings. The LRO spacecraft triggered a sun-safed event that powered off all instruments on October 10, 2009. Approximately eight hours of Diviner data was lost due to the anomaly. Two more sun-safed events occurred on both January 12, 2010 and February 9, 2010. The Diviner instrument was powered off for both events. On July 23, 2010Diviner was powered off for almost five hours during a spacecraft maneuverduring which Diviner data were not collected. On December 23, 2010Diviner was powered off during for about 12 hours during an eclipse.On February 23, 2011 Diviner was powered off for about 46 hours dueto a spacecraft safing event. On April 03, 2011 Diviner was powered offfor about 23 hours due to a spacecraft safing event. On June 06, 2011Diviner lost about 14 hours of data due to a Ka-comm problem. On March 22, 2012 Diviner was powered off for about 40 hours due to aspacecraft safing event. On September 04, 2012 Diviner was powered offfor about 17 hours due to a spacecraft safing event. One September 08, 2012 Diviner was powered off for about 13 hours due to a spacecraft safing event.The following files were affected by the anomalies and are either partial files or completely missing:2009082202_EDR.TAB - partial - missing data between times  02:03:55.171-02:04:06.422 due to invalid equator crossing from LRO. 2009101016_EDR.TAB - partial - missing data after 16:14:38.9802009101017_EDR.TAB through 2009101023_EDR.TAB ---------> 7 files missing2009101100_EDR.TAB - partial - missing data before 00:41:15.6072010011210_EDR.TAB - partial - missing data after 10:00:00:4682010011211_EDR.TAB through 2010011220_EDR.TAB ---------> 10 files missing2010011221_EDR.TAB - partial - missing data before 21:18:56:1942010020914_EDR.TAB - partial - missing data after 14:59:48:1822010020915_EDR.TAB through 2010021520_EDR.TAB --------> 150 files missing2010021521_EDR.TAB - partial - missing data before 21:54:34:3972010072414_EDR.TAB - partial - missing data after 14:34:04:2532010072415_EDR.TAB through 2010072418_EDR.TAB --------> 4 files missing2010072419_EDR.TAB - partial - missing data before 19:24:37:0582010122105_EDR.TAB - partial - missing data after 05:08:03:2972010122106_EDR.TAB through 2010122116_EDR.TAB --------> 11 files missing2010122117_EDR.TAB - partial - missing data before 17:08:15:1342011022314_EDR.TAB - partial - missing data after 14:24:57:2902011022315_EDR.TAB through 2011022512_EDR.TAB --------> 46 files missing2011022513_EDR.TAB - partial - missing data before 13:07:28:3802011040317_EDR.TAB - partial - missing data after 17:29:04:6982011040318_EDR.TAB through 2011040413_EDR.TAB --------> 20 files missing2011040414_EDR.TAB - partial - missing data before 14:44:47:9002011061409_EDR.TAB - partial - missing data after 09:37:20:5722011061410_EDR.TAB through 2011061423_EDR.TAB --------> 14 files missing2011061500_EDR.TAB - partial - missing data before 00:07:20:8692012032202_EDR.TAB - partial - missing data after 02:30:26:2152012032203_EDR.TAB through 2012032317_EDR.TAB --------> 39 files missing2012032318_EDR.TAB - partial - missing data before 18:15:475702012090405_EDR.TAB - partial - missing data after 05:15:27:4142012090406_EDR.TAB through 2012090420_EDR.TAB --------> 15 files missing2012090421_EDR.TAB - partial - missing data before 21:01:36:5752012090801_EDR.TAB - partial - missing data after 01:15:04:9082012090802_EDR.TAB through 2012090812_EDR.TAB --------> 11 files missing2012090813_EDR.TAB - partial - missing data before 13:51:51:6812013112704_EDR.TAB - partial - missing data after 04:09:51:689 2013112705_EDR.TAB through 2013112919_EDR.TAB --------> 63 files missing2013112920_EDR.TAB - partial - missing data before 20:51:58:203 2014022611_EDR.TAB - partial - missing data after 11:20:42:9622014022612_EDR.TAB through 2014022620_EDR.TAB --------> 9 files missing2014022621_EDR.TAB - partial - missing data before 21:29:57:7162014041504_EDR.TAB - partial - missing data after 04:25:43:2252014041505_EDR.TAB through 2014041516_EDR.TAB --------> 12 files missing2014041517_EDR.TAB - partial - missing data before 17:31:47:1792018013110_EDR.TAB - partial - missing data after 10:24:31.9602018013111_EDR.TAB through 2018013123_EDR.TAB --------> 13 files missing2018020200_EDR.TAB - partial - missing data before 00:57:11.9272018072717_EDR.TAB - partial - missing data after 17:13:00.7992018072718_EDR.TAB through 2018072802_EDR.TAB --------> 9 files missing2018072803_EDR.TAB - partial - missing data before 03:53:56.6302018121222_EDR.TAB - partial - missing data after 22:17:14:4502018121223_EDR.TAB through 2018121223_EDR.TAB --------> 1 files missing2018121300_EDR.TAB - partial - missing data before 00:24:51:2872019012102_EDR.TAB - partial - missing data after 02:08:03:7152019012103_EDR.TAB through 2019012109_EDR.TAB --------> 7 files missing2019012110_EDR.TAB - partial - missing data before 10:40:17:5552019121914_EDR.TAB - partial - missing data after 14:01:43:4422019121915_EDR.TAB through 2019121922_EDR.TAB --------> 8 files missing2019121923_EDR.TAB - partial - missing data before 23:38:34:2022021111609_EDR.TAB - partial - missing data after 19:01:33:957 2021111610_EDR.TAB through 2021111800_EDR.TAB --------> 39 files missing2021111801_EDR.TAB - partial - missing data before 01:00:01:705  2021111905_EDR.TAB - partial - missing data after 05:46:03:917 2021111906_EDR.TAB through 2021111919_EDR.TAB --------> 14 files missing2021111920_EDR.TAB - partial - missing data before 20:09:08:010 2022051601_EDR.TAB - partial - missing data after 01:20:33:7912022051602_EDR.TAB through 2022051613_EDR.TAB --------> 12 files missing2022051614_EDR.TAB - partial - missing data before 14:59:40:3942022110808_EDR.TAB - partial - missing data after 08:19:23:6062022110809_EDR.TAB through 2022110900_EDR.TAB --------> 16 files missing2022110901_EDR.TAB - partial - missing data before 01:49:45:808Limitations:Data seen immediately after the instrument is powered on or aftera restart is suspect for a few seconds to a few minutes. The pointinginformation is typically incorrect or missing.