Data Set Information
|
| DATA_SET_NAME |
LRO DLRE 4 CALIBRATED RADIANCE V1.0
|
| DATA_SET_ID |
LRO-L-DLRE-4-RDR-V1.0
|
| NSSDC_DATA_SET_ID |
|
| DATA_SET_TERSE_DESCRIPTION |
|
| DATA_SET_DESCRIPTION |
-------------------------------------------------------------------------+Data Product Overview :Every 2.048 seconds Diviner collects a data 'frame' containing the following:* 16 sets of science data, with each set containing 189 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. The RDR data tables are produced directly from the EDR data tables using Diviner software, geometry, and ephemeris data provided by the LRO project. Each Diviner RDR 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. Unlike the EDR data tables, which contain values for each of the 189 detectors in a single record (every 0.128 seconds), the RDR data tables have one record per detector. Therefore, for every EDR record there will be 189 detector-specific RDR records, each with the same 'date' and 'utc' time as the original EDR record.Due to the size of the RDR dataset, each RDR data table will cover ten minutes of time, one-sixth of the EDR data tables. In order to save space on disk and to facilitate faster downloading, the RDR data tables will be compressed using Info-ZIP (freely available utility).The RDR data product is considered to be foremost of scientific interest, and thus contains a minimal representation of engineering and housekeeping data needed to verify instrument status and data quality.Data Processing Level:The Diviner RDR data products are derived directly from the Diviner EDR data products and are considered 'Diviner Level 1'. It is similar to CODMAC Level 3 (NASA Level 1A) in that the data are reversibly calibrated and located in space, yet the content resembles more traditional CODMAC Level 4 (NASA Level 1B) data.Data Product Generation :The Diviner RDR data products and labels will be generated by the Diviner Instrument Team at JPL. The RDR data products will be derived from the EDR data products, merged with geometry and ephemeris data provided by the LRO Project, and formatted according to the RDR SIS.Data Flow :After an initial data validation period, the Diviner team at JPL will transfer the data tables and labels to the UCLA SOC, which will assemblethe archive volumes and transfer them to the PDS Geosciences Node.The Diviner RDR archive will be made available via data releases scheduled at three month intervals as specified in the Lunar Reconnaissance Orbiter Project Data Management and Archive 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.
|
| DATA_SET_RELEASE_DATE |
2023-12-15T00:00:00.000Z
|
| START_TIME |
2009-07-05T04:50:26.195Z
|
| STOP_TIME |
2023-09-16T12:00:00.027Z
|
| MISSION_NAME |
LUNAR RECONNAISSANCE ORBITER
|
| MISSION_START_DATE |
2009-06-18T12:00:00.000Z
|
| MISSION_STOP_DATE |
N/A (ongoing)
|
| TARGET_NAME |
MOON
|
| TARGET_TYPE |
SATELLITE
|
| INSTRUMENT_HOST_ID |
LRO
|
| INSTRUMENT_NAME |
DIVINER LUNAR RADIOMETER EXPERIMENT
|
| INSTRUMENT_ID |
DLRE
|
| INSTRUMENT_TYPE |
RADIOMETER
|
| NODE_NAME |
Geosciences
|
| ARCHIVE_STATUS |
ARCHIVED - ACCUMULATING
|
| CONFIDENCE_LEVEL_NOTE |
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 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 hours were affected by the anomalies and have either partialdata tables or are completely missing:2009082202** - partial - missing data between times 02:03:55.171 - 02:04:06.422 - Due to invalid equator crossing from LRO. 2009101016** - partial - missing data after 16:14:38.9802009101017** through 2009101023** ---------> 7 hours missing2009101100** - partial - missing data before 00:41:15.6072010011210** - partial - missing data after 10:00:00:4682010011211** through 2010011220** ---------> 10 hours missing2010011221** - partial - missing data before 21:18:56:1942010020914** - partial - missing data after 14:59:48:1822010020915** through 2010021520** --------> 150 hours missing2010021521** - partial - missing data before 21:54:34:3972010072414** - partial - missing data after 14:34:04:2532010072415** through 2010072418** --------> 4 hours missing2010072419** - partial - missing data before 19:24:37:0582010122105** - partial - missing data after 05:08:03:2972010122106** through 2010122116** --------> 11 hours missing2010122117** - partial - missing data before 17:08:15:1342011022314** - partial - missing data after 14:24:57:2902011022315** through 2011022512** --------> 46 hours missing2011022513** - partial - missing data before 13:07:28:3802011040317** - partial - missing data after 17:29:04:6982011040318** through 2011040413** --------> 20 files missing2011040414** - partial - missing data before 14:44:47:9002011061409** - partial - missing data after 09:37:20:5722011061410** through 2011061423** --------> 14 files missing2011061500** - partial - missing data before 00:07:20:8692012032202** - partial - missing data after 02:30:26:2152012032203** through 2012032317** --------> 39 files missing2012032318** - partial - missing data before 18:15:475702012090405** - partial - missing data after 05:15:27:4142012090406** through 2012090420** --------> 15 files missing2012090421** - partial - missing data before 21:01:36:5752012090801** - partial - missing data after 01:15:04:9082012090802** through 2012090812** --------> 11 files missing2012090813** - partial - missing data before 13:51:51:6812013112704** - partial - missing data after 04:09:51:6892013112705** through 2013112919** --------> 63 files missing2013112920** - partial - missing data before 20:51:58:2032014022611** - partial - missing data after 11:20:42:9622014022612** through 2014022620** --------> 9 files missing2014022621** - partial - missing data before 21:29:57:7162014041504** - partial - missing data after 04:25:43:2252014041505** through 2014041516** --------> 12 files missing2014041517** - partial - missing data before 17:31:47:1792018013110** - partial - missing data after 10:24:31.9602018013111** through 2018013123** --------> 13 files missing2018020100** - partial - missing data before 00:57:11.9272018072717** - partial - missing data after 17:13:00.7992018072718** through 2018072802** --------> 9 files missing2018072803** - partial - missing data before 03:53:56.6302018121222** - partial - missing data after 22:17:14:4502018121223** through 2018121223** --------> 1 files missing2018121300** - partial - missing data before 00:24:51:2872019012102** - partial - missing data after 02:08:03:7152019012103** through 2019012109** --------> 7 files missing2019012110** - partial - missing data before 10:40:17:5552019121914** - partial - missing data after 14:01:43:4422019121915** through 2019121922** --------> 8 files missing2019121923** - partial - missing data before 23:38:34:2022021111609** - partial - missing data after 19:01:33:9572021111610** through 2021111800** --------> 39 files missing2021111801** - partial - missing data before 01:00:01:7052021111905** - partial - missing data after 05:46:03:9172021111906** through 2021111919** --------> 14 files missing2021111920** - partial - missing data before 20:09:08:0102022051601** - partial - missing data after 01:20:33:7912022051602** through 2022051613** --------> 12 files missing2022051614** - partial - missing data before 14:59:40:3942022110808** - partial - missing data after 08:19:23:6062022110809** through 2022110900** --------> 16 files missing2022110901** - 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.Known Issues:1. Noise EventsA quality flag (qmi, bit 5) has been implemented to mark datacollected during noise periods. Episodic noise events of unknown origin are observed to affect a small fraction of Diviner's housekeeping and radiometric data. The noise signature in the radiometric data consists of simultaneous correlated signal spikes or offsets in all 189 Diviner detectors. Potential noise events arecataloged by reviewing one-hour plots of Diviner housekeeping data and flagging those periods in which noise is suspected. Noise events have been flagged from 2009-07-05 to 2010-12-15Noise events for the period 2010-12-15 to 2012-03-15 will beapplied in a later PDS data release.2. Geometric ErrorsNone.3. Radiometric LinearityIn the course of the analysis of the Diviner laboratory calibration data, concerns have developed regarding the linearity of the radiometric response of the instrument in the longer wavelength channels at temperatures higher than 300K. The current calibration algorithm assumes linear response at all signal levels.Brightness temperatures will be recalculated based on updated linearity parameters based on reanalysis of laboratory and in-flight data in updated versions of the dataset.4. Short Wavelength Spectral LeaksWe have evidence that the measured radiances in Channels 8 and 9 are affected by the intensity of reflected solar radiation. Only daytime data are affected and no evidence for similar spectral leaks has been identified in any other channels. Since the intensity of reflected solar radiation from the moon is correlated with temperature, the effects of the spectral leaks in these channels tend to be greatest at higher temperatures. The most pronounced effects are most evident at temperatures greater than 300K. However, pending further investigation, the radiometric accuracy of daytime data in Channels 8 and 9 should be considered suspect.5. Eclipse EventsA quality flag (qmi, bit 1) has been implemented to mark datacollected during eclipse periods. The eclipse period begins at enteringpenumbra and ends two hours after the exit from penumbra.
|
| CITATION_DESCRIPTION |
Paige et al., LRO DLRE LEVEL 4 RDR V1.0, NASA Planetary Data System, LRO-L-DLRE-4-RDR-V1.0, 2010.
|
| ABSTRACT_TEXT |
This data set consists of the Diviner Lunar Radiometer Experiment Reduced Data Records also known as RDRs. The DLRE is a surface pushbroom mapper that measures emitted thermal radiation and reflected solar radiation from the surface of the moon. Two Diviner solar channels measure 0.3-3 micrometers reflected solar radiation. Three Diviner channels near 8 micrometers classify regolith mineralogy by mapping the location of the Christiansen feature. The remaining four Diviner channels measure surface temperature in four spectral bands ranging from 12.5 micrometers to beyond 200 micrometers.
|
| PRODUCER_FULL_NAME |
DAVID PAIGE
|
| SEARCH/ACCESS DATA |
Geosciences Web Service
Geosciences Online Archives
Lunar Orbital Data Explorer
|
|
.png)
.png)
