PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2013-05-20 NOTE = "Release notes and errata for MSL MARDI EDR and RDR volumes" END_OBJECT = TEXT END Users are encouraged to provide comments to the PDS Imaging Node if errors are found either in data or in documentation in this archive. Please send comments by e-mail or U.S. mail to the Imaging Node: PDS Imaging Node California Institute of Technology Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 Web: http://img.pds.nasa.gov/index.html This file, ERRATA.TXT, contains release notes and errata identified in the MSL MARDI EDR and RDR archive on volumes MSLMRD_0XXX. During the course of the MSL mission the MARDI science team may update previously released data products or documentation; for example, updates may occur due to changes in calibration data or procedures. Updates will be reported in this file. Older versions of data and documentation will not be retained in the archive. Section A of this file contains an entry for each MSL release with general information about the contents of the release, in order from newest to oldest. Updates to previously released files are reported in these entries, along with any known errata. Section B of this file contains general notes, if any, concerning the archive as a whole. ******** SECTION A ******** RELEASE NUMBER: 31 RELEASE DATE: 2022-12-05 DATA COVERAGE: 2022-03-24 to 2022-07-30 (Sols 3424-3547) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 3427MD0012760000202657{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3424; an error report was filed 3429MD0012770000202658{E,I}01 due to a rover issue, the drive did did not complete; this is repeat imaging from sols 3424 and 3427; an error report was filed 3434MD0012800000202660{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sols 3424, 3427, 3429 3433, and 3434; an error report was filed **************************************************************** **************************************************************** RELEASE NUMBER: 30 RELEASE DATE: 2022-08-01 DATA COVERAGE: 2021-11-07 to 2022-03-24 (Sols 3290-3423) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 3304MD0012160000202602{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3286; an error report was filed 3351MD0012360000202618{E,I}01 due to a rover issue, the drive did did not complete; this is repeat imaging from sol 3351; an error report was not filed **************************************************************** **************************************************************** RELEASE NUMBER: 29 RELEASE DATE: 2022-03-16 DATA COVERAGE: 2021-07-30 to 2021-11-07 (Sols 3193-3289) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None No new errata have been identified in this release. **************************************************************** **************************************************************** RELEASE NUMBER: 28 RELEASE DATE: 2021-12-06 DATA COVERAGE: 2021-03-24 to 2021-07-30 (Sols 3069-3192) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 3104MD0011580000202544{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3089; an error report was filed 3107MD0011590000202545{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3089 and sol 3104; an error report was filed 3122MD0011650000202551{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3120; an error report was filed 3127MD0011660000202552{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3120 and sol 3122; an error report was filed 3135MD0011670000202553{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 3120, sol 3122 and sol 3127; an error report was filed **************************************************************** **************************************************************** RELEASE NUMBER: 27 RELEASE DATE: 2021-08-02 DATA COVERAGE: 2020-11-07 to 2021-03-23 (Sols 2935-3068) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 2998MD0011200000202232{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 2995; an error report was filed **************************************************************** **************************************************************** RELEASE NUMBER: 26 RELEASE DATE: 2021-03-16 DATA COVERAGE: 2020-07-30 to 2020-11-07 (Sols 2838-2934) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 2865MD0010870000202201{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sols 2829, 2837, 2839, 2842, 2857, 2859, 2860, 2861, and 2862; an error report was filed 2. Meta-kernel setup file updated The MMM_CHRONOS_V04.TM file in the EXTRAS directory has been updated. Please see Section B, number 16, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 25 RELEASE DATE: 2020-12-04 DATA COVERAGE: 2020-03-25 to 2020-07-30 (Sols 2714-2837) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 2736MD0010430000202157{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 2734; an error report was filed **************************************************************** **************************************************************** RELEASE NUMBER: 24 RELEASE DATE: 2020-07-31 DATA COVERAGE: 2019-11-08 to 2020-03-25 (Sols 2580-2713) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 2636MD0010110000201758{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 2633; an error report was filed 2647MD0010150000201762{E,I}01 due to a rover issue, the drive did did not execute; this is repeat imaging from sol 2645; an error report was filed 2688MD0010250000201772{E,I}01 due to an arm fault, the drive did did not execute; this is repeat imaging from sol 2686; an error report was filed **************************************************************** **************************************************************** RELEASE NUMBER: 23 RELEASE DATE: 2020-03-16 DATA COVERAGE: 2019-07-31 to 2019-11-08 (Sols 2483-2579) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Meta-kernel setup file updated The MMM_CHRONOS_V03.TM file in the EXTRAS directory has been updated. Please see Section B, number 15, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 22 RELEASE DATE: 2019-12-05 DATA COVERAGE: 2019-03-26 to 2019-07-31 (Sols 2359-2482) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Updated keywords for video products The keywords INSTRUMENT_TEMPERATURE, MSL:INSTRUMENT_TEMPERATURE_STATUS, SOLAR_AZIMUTH, SOLAR_ELEVATION have been set to NULL/UNK for all video products except the first frame. Please see Section B, number 14, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 21 RELEASE DATE: 2019-08-01 DATA COVERAGE: 2018-11-08 to 2019-03-26 (Sols 2225-2358) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 2293MD0009080000201413{E,I}01 due to an arm fault, the drive did did not execute; this is repeat imaging from sol 2291; an error report was filed 2. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. **************************************************************** **************************************************************** RELEASE NUMBER: 20 RELEASE DATE: 2019-03-15 DATA COVERAGE: 2018-08-01 to 2018-11-08 (Sols 2128-2224) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None No new errata have been identified in this release. **************************************************************** **************************************************************** RELEASE NUMBER: 19 RELEASE DATE: 2018-12-05 DATA COVERAGE: 2018-03-26 to 2018-08-01 (Sols 2004-2127) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Global Dust Storm Impacts The global dust storm of Mars year 34 significantly impacted the opacity in Gale Crater. Images that were acquired from sols 2082-2150 may be impacted due to the off-nominal lighting conditions. 2. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 2084MD0008150000201070{E,I}01 due to an arm fault, the drive did not execute; this is repeat imaging from sol 2054; no error report was filed 2087MD0008170000201072{E,I}01 due to a mobility fault, the drive did not execute; this is repeat imaging from sol 2086; no error report was filed 3. Update to INSTRUMENT_TEMPERATURE and MSL:INSTRUMENT_TEMPERATURE_STATUS keywords Two keywords in the GROUP = INSTRUMENT_STATE_PARMS, INSTRUMENT_TEMPERATURE and MSL:INSTRUMENT_TEMPERATURE_STATUS, have been updated to include valid values, if applicable. Please see Section B, number 13, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 18 RELEASE DATE: 2018-08-01 DATA COVERAGE: 2017-11-08 to 2018-03-26 (Sols 1870-2003) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Updated AUTO_EXPOSURE_DATA_CUT keyword The keyword AUTO_EXPOSURE_DATA_CUT in the GROUP = IMAGE_REQUEST_PARMS has been updated to include valid values, if applicable. Please see Section B, number 12, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 17 RELEASE DATE: 2018-03-16 DATA COVERAGE: 2017-08-01 to 2017-11-08 (Sols 1773-1869) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 1792MD0007270000200773{E,I}01 due to an arm fault, the drive did did not execute; this is repeat imaging from sol 1789; an error report was filed **************************************************************** **************************************************************** RELEASE NUMBER: 16 RELEASE DATE: 2017-12-05 DATA COVERAGE: 2017-03-26 to 2017-08-01 (Sols 1649-1772) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: 4 EDR .LBLs & 16 RDR .LBLs 1. Updated product types Incorrect information was found in some sol 1591 RATIONALE_DESC keywords. RATIONALE_DESC has been corrected and the following product's .LBLs have been updated to include PRODUCT_VERSION_ID = V2.0. The data products themselves have not changed. PICNOs with updated LBLs in RELEASE 0016: ------------------------- 1591MD0006060000200656{E,I}01 1591MD0006070000200657{E,I}01 1591MD0006080000200658{E,I}01 1591MD0006090000200659{E,I}01 2. MARDI Instrument Description Paper A technical paper entitled, "The Mars Science Laboratory (MSL) Mast cameras and Descent imager: Investigation and instrument descriptions" has been added to the DOCUMENT directory, MSL_MASTCAM_MARDI_INSTRUMENT_DESCRIPTIONS.PDF. This paper describes the Mast cameras and Descent imager (MARDI) instrument on the Curiosity rover. **************************************************************** **************************************************************** RELEASE NUMBER: 15 RELEASE DATE: 2017-08-01 DATA COVERAGE: 2016-11-09 to 2017-03-26 (Sols 1515-1648) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Unexpected scene and image content Some images did not contain their intended target or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNOs Description ------------------------------ ---------------------------------- 1575MD0005950000200645{E,I}01 due to an arm fault, the drive did did not execute; this is repeat imaging from sol 1574; an error report was filed 2. Flat-field processing of RDR products removed Flat-field processing of RDR products has been removed. Please see Section B, number 10, below, for more details. 3. Meta-kernel setup file updated The MMM_CHRONOS_V02.TM file in the EXTRAS directory has been updated. Please see Section B, number 11, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 14 RELEASE DATE: 2017-03-16 DATA COVERAGE: 2016-08-01 to 2016-11-09 (Sols 1418-1514) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Incorrect CDPID counters in certain PICNOs It was noticed that a processing issue caused certain products in Release 0012 to receive incorrect CDPID counters within their PICNOs (positions 16-17). These products were given a value of 03 when they should have been given a value of 02. Assigned PICNO range Expected PICNO range ------------------------------ -------------------------- 1179MD0004470000300002{E,I}01 1179MD0004470000200002{E,I}01 2. Updates to MODEL_COMPONENT_3 and MODEL_COMPONENT_4 in the Camera Model Data Elements section of the .LBL Changes have been made to two keywords in the .LBL files, MODEL_COMPONENT_3 and MODEL_COMPONENT_4 in the Camera Model Data Elements section of the .LBL, specifically the GEOMETRIC_CAMERA_MODEL_PARMS group. Please see Section B, number 9, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 13 RELEASE DATE: 2016-12-05 DATA COVERAGE: 2016-03-27 to 2016-08-01 (Sols 1294-1417) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Updates to RADIANCE_OFFSET, RADIANCE_SCALING_FACTOR, and RADIOMETRIC_CORRECTION_TYPE Changes have been made to three keywords in the .LBL files, RADIANCE_OFFSET, RADIANCE_SCALING_FACTOR, and RADIOMETRIC_CORRECTION_TYPE. Please see Section B, numbers 6 and 7, below, for more details. 2. Meta-kernel and CHRONOS setup files added to volume Two files used for product generation have been added to the EXTRAS directory, a meta-kernel file, MMM_CHRONOS_V01.TM, and a CHRONOS setup file, MSL_CONSTANTS_V1.TXT. Please see Section B, number 8, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 12 RELEASE DATE: 2016-08-01 DATA COVERAGE: 2015-11-10 to 2016-03-27 (Sols 1160-1293) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. PICNO lookup tables have been added to the INDEX directory Two tables, one for EDRs and one for RDRs, have been added to the INDEX directory which correlate PDS PICNOs with the daily, operationally produced PICNOs. Please see Section B, number 4, below, for more details. 2. SEQUENCE_ID has been added to *INDEX.TAB files The SEQUENCE_ID keyword has been added to the {EDR,RDR}INDEX.TAB and {EDR,RDR}_CMDX.TAB files. Please see Section B, number 5, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 11 RELEASE DATE: 2016-03-16 DATA COVERAGE: 2015-08-02 to 2015-11-10 (Sols 1063-1159) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None No new errata have been identified in this release. **************************************************************** **************************************************************** RELEASE NUMBER: 10 RELEASE DATE: 2015-12-04 DATA COVERAGE: 2015-03-28 to 2015-08-02 (Sols 939-1062) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None No new errata have been identified in this release. **************************************************************** **************************************************************** RELEASE NUMBER: 9 RELEASE DATE: 2015-07-31 DATA COVERAGE: 2014-11-10 to 2015-03-28 (Sols 805-938) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Drive video with incorrect Camera Data Product Identifiers (CDPID) On sol 651, mrdi00249 acquired 278 frames of a video of a drive. The resulting products had incorrect CDPIDs due to a MARDI flight software bug. While the PICNOs and .LBL files were manually changed to contain the correct CDPID, the binary .DAT files still retain the original, incorrect CDPIDs that were actually downlinked from the rover. PICNO range CDPID range -------------------------- ----------- 0651MD0002490000101736M01- 1736-1749 0651MD0002490000101749M01 0651MD0002490000101751M01- 1751-1758 0651MD0002490000101758M01 2. Updates to CONTACT_SENSOR_STATE and CONTACT_SENSOR_STATE_NAME Changes have been made to two keywords in the .LBL files, CONTACT_SENSOR_STATE and CONTACT_SENSOR_STATE_NAME. Please see Section B, below, for more details. 3. Updates to the MARDI camera model The camera model has been updated for MARDI. Please see Section B, below, for more details. **************************************************************** **************************************************************** RELEASE NUMBER: 8 RELEASE DATE: 2015-03-16 DATA COVERAGE: 2014-08-03 to 2014-11-10 (Sols 708-804) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Drive video with lower than expected number of saved images On sol 787, the drive video contained several unexpected skips, or no apparent overlap between frames. These were seen between the following images: PICNO range CDPID range ------------------------------ ----------- 0787MD0003310010102747{M,Q}01- 2747-2748 0787MD0003310010102748{M,Q}01 0787MD0003310010102757{M,Q}01- 2757-2758 0787MD0003310010102758{M,Q}01 0787MD0003310010102761{M,Q}01- 2761-2762 0787MD0003310010102762Q01 0787MD0003310010102762Q01- 2762-2763 0787MD0003310010102763{M,Q}01 0787MD0003310010102763{M,Q}01- 2763-2764 0787MD0003310010102764{M,Q}01 0787MD0003310010102781{M,Q}01- 2781-2782 0787MD0003310010102782{M,Q}01 While this is a MARDI flight software issue and an error report was filed, it should be noted that there is nothing wrong with the products themselves. The PICNOs are correct and the CDPIDs are sequential. The issue is only apparent when the images are played as a video; the video occasionally "jumps" due to the lack of overlap between frames. **************************************************************** **************************************************************** RELEASE NUMBER: 7 RELEASE DATE: 2014-12-05 DATA COVERAGE: 2014-03-28 to 2014-08-03 (Sols 584-707) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Drive video with incorrect Camera Data Product Identifiers (CDPID) On sol 651, mrdi00249 acquired 278 frames of a video of a drive. The resulting products had incorrect CDPIDs due to a MARDI flight software bug. While the PICNOs and .LBL files were manually changed to contain the correct CDPID, the binary .DAT files still retain the original, incorrect CDPIDs that were actually downlinked from the rover. PICNO range CDPID range -------------------------- ----------- 0651MD0002490000101736Q01- 1736-2013 0651MD0002490000102013Q01 0651MD0002490000101808M01- 1808-1810 0651MD0002490000101810M01 0651MD0002490000101843M01- 1843-1845 0651MD0002490000101845M01 2. Drive video saturation The sol 651 drive video was severely overexposed. The rover orientation before the drive had the MARDI viewing a shadowed surface, which is when autoexposure ran. However, once the drive began (and after autoexposure had already run), the rover did a turn and the exposed surface under the MARDI was in sun light causing nearly all the images in the video to be overexposed. PICNO range CDPID range -------------------------- ----------- 0651MD0002490000101736Q01- 1736-2013 0651MD0002490000102013Q01 0651MD0002490000101808M01- 1808-1810 0651MD0002490000101810M01 0651MD0002490000101843M01- 1843-1845 0651MD0002490000101845M01 3. Twilight image DN levels are lower than expected On sol 660, a commanding error in mrdi00259 caused the autoexposure algorithm to fail. The resulting image has DN values of ~0-12 (black) and excessive EMI noise. This image was also downlinked uncompressed and exhibited the same DN values and EMI noise. PICNO ----------------------------- 0660MD0002590000102023{I,E}01 0660MD0002590000102023B00 **************************************************************** **************************************************************** RELEASE NUMBER: 6 RELEASE DATE: 2014-08-01 DATA COVERAGE: 2013-11-10 to 2014-03-28 (Sols 450-583) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. **************************************************************** **************************************************************** RELEASE NUMBER: 5 RELEASE DATE: 2014-03-17 DATA COVERAGE: 2013-08-11 to 2013-11-10 (Sols 360-449) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. **************************************************************** **************************************************************** RELEASE NUMBER: 4 RELEASE DATE: 2013-12-13 DATA COVERAGE: 2013-05-09 to 2013-08-10 (Sols 270-359) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. **************************************************************** **************************************************************** RELEASE NUMBER: 3 RELEASE DATE: 2013-08-30 DATA COVERAGE: 2013-02-06 to 2013-05-08 (Sols 180-269) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. The MARDI EDL imaging sequence was part of the spacecraft Entry, Descent, and Landing (EDL) action. This required the sequence to be hardcoded into the EDL timeline instead of being run as an imaging sequence that is uplinked a few sols prior to execution, as is done during landed operations. Therefore, for all EDL data: SEQUENCE_ID = aut_04096 In addition, as noted in the PDS Data Product SIS, any image acquired during EDL is assigned the product identifier 000000000. The following is the first PICNO generated from the EDL sequence: 0000MD0000000000100001{I,E}01 All MARDI images acquired post-EDL conform to the PICNO scheme outlined in the PDS Data Product SIS. 2. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. **************************************************************** **************************************************************** RELEASE NUMBER: 2 RELEASE DATE: 2013-06-10 DATA COVERAGE: 2012-11-06 to 2013-02-05 (Sols 90-179) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. The MARDI EDL imaging sequence was part of the spacecraft Entry, Descent, and Landing (EDL) action. This required the sequence to be hardcoded into the EDL timeline instead of being run as an imaging sequence that is uplinked a few sols prior to execution, as is done during landed operations. Therefore, for all EDL data: SEQUENCE_ID = aut_04096 In addition, as noted in the PDS Data Product SIS, any image acquired during EDL is assigned the product identifier 000000000. The following is the first PICNO generated from the EDL sequence: 0000MD0000000000100001{I,E}01 All MARDI images acquired post-EDL conform to the PICNO scheme outlined in the PDS Data Product SIS. 2. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. **************************************************************** **************************************************************** RELEASE NUMBER: 1 RELEASE DATE: 2013-06-10 DATA COVERAGE: 2012-03-12, 2012-04-20, 2012-06-14 (Cruise) 2012-08-06 to 2012-11-05 (Sols 0-89) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: MARDI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. CRUISE products During cruise, a single checkout sequence was run on 3 different dates, March 12, 2012, April 20, 2012, and June 14, 2012. Each execution acquired two images plus an 8-image EDL practice video. At the end of acquisition, the products were erased. a. Missing video product During the April 20, 2012 checkout, the MARDI cruise sequence executed successfully and thumbnails were received for both images plus all 8 images of the EDL video. However, only the 2 image products and 7 of the 8 video products were received. One video product never made it to the group. The thumbnail, CRU_MD0000060030000019Q01_XXXX does not have a corresponding video product. b. In the PDS labels, SEQUENCE_ID = aut_04096 for all MARDI EDR cruise images. This is a known rover flight software bug. c. No RDRs were produced for this data set. 2. The MARDI EDL imaging sequence was part of the spacecraft Entry, Descent, and Landing (EDL) action. This required the sequence to be hardcoded into the EDL timeline instead of being run as an imaging sequence that is uplinked a few sols prior to execution, as is done during landed operations. Therefore, for all EDL data: SEQUENCE_ID = aut_04096 In addition, as noted in the PDS Data Product SIS, any image acquired during EDL is assigned the product identifier 000000000. The following is the first PICNO generated from the EDL sequence: 0000MD0000000000100001{I,E}01 All MARDI images acquired post-EDL conform to the PICNO scheme outlined in the PDS Data Product SIS. 3. Clarification of the "SEQUENCE_ID" in the data product .LBL file versus the "Sequence ID" in the Product Identifier described in the MMM PDS Data Product Software Interface Specification (SIS) As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. ******** SECTION B ******** This section is provided for general notes concerning the archive as a whole. 1. In Releases 0001-0008, the CONTACT_SENSOR_STATE keyword indicates values of "OPEN" and "CLOSED" when these values should be "CONTACT" and "NO CONTACT", respectively. This mis-mapping appears in the MSL_MMM_EDR_RDR_DPSIS.PDF SIS, plus all products and PDS labels. Starting with Release 0009 and onwards, this issue has been corrected in the MSL_MMM_EDR_RDR_DPSIS.PDF SIS plus all products and PDS labels. 2. In Releases 0001-0008, the CONTACT_SENSOR_STATE_NAME values are incorrectly identified in the MSL_MMM_EDR_RDR_DPSIS.PDF SIS, plus all products and PDS labels. Based on flight software, values for this keyword are correct in Release 0009 onwards. Releases 0001-0008 (Incorrect) Bit mapping: ------------------------------------------- Bit 0 - "MALHI SWITCH 1" Bit 1 - "MALHI SWITCH 2" Bit 2 - "DRT SWITCH 1" Bit 3 - "DRT SWITCH 2" Bit 4 - "DRILL SWITCH 1" Bit 5 - "DRILL SWITCH 2" Bit 6 - "APXS DOOR SWITCH" Bit 7 - "APXS CONTACT SWITCH" Release 0009 and onwards (Correct) Bit mapping: ----------------------------------------------- Bit 0 - "APXS CONTACT SWITCH 1" Bit 1 - "APXS CONTACT SWITCH 2" Bit 2 - "DRILL SWITCH 1" Bit 3 - "DRILL SWITCH 2" Bit 4 - "MALHI SWITCH 1A" Bit 5 - "MALHI SWITCH 1B" Bit 6 - "MALHI SWITCH 2A" Bit 7 - "MALHI SWITCH 2B" 3. In Releases 0001-0008, the MARDI orientation in the camera model is incorrect. In previous releases, the values in the camera model had been flipped 180 degrees. For Release 0009 and onwards, the orientation of the MARDI in the camera model is reverted to its nominal values, i.e., the MARDI is pointing straight down in the rover frame with "up" in the image pointing to the rear of the rover. 4. In Releases 0001-0011, the version ID in the PICNO (see section 3.4.1 of MSL_MMM_EDR_RDR_DPSIS.PDF) does not necessarily match the daily, operational version of the same product. Due to the fact that there can be multiple versions of a product (e.g., partials) received during operations, this value is incremented for each version of a product received. However, for PDS archiving, when applicable, only the full and complete version of a product is archived which will receive the lowest version ID possible for that type of product. In most cases, this is a value of 1. As a result, the PDS products archived in Releases 0001-0011 do not necessarily reflect the same version ID seen in the corresponding final, complete version of a daily, operations-received product. To account for this, lookup tables which correlate the operational PICNO to the PDS PICNO for Releases 0001-0011 have been provided in the INDEX directory. There is one table for EDR and one table for RDR products. Starting with Release 0012, all full versions of every operationally- produced product will be available in the MARDI PDS volume, and partial products will be taken into consideration when assigning the PICNO version number. This will ensure that all PICNOs in the PDS volume match with the corresponding daily, operational version of the same product. 5. The SEQUENCE_ID keyword has been added to {EDR,RDR}INDEX.TAB and {EDR,RDR}_CMDX.TAB files This keyword already existed in each data product's .LBL file, but has now been added to the .TAB files for easy reference. The {EDR,RDR}_CMDX.TAB files for Releases 0001-0011 have been backfilled and now include this keyword in the Release 0012 volumes onwards. As stated in the File Naming Convention section of the SIS, the first six digits of the product identifier (Sequence ID) are reflected in the SEQUENCE_ID keyword value in the data product label file (.LBL). This is the case when the MARDI data are downlinked via the original sequence that acquired the data as recorded in the product identifier. Occasionally, the data are requested to be downlinked differently than acquired (e.g., a different compression); this is done by sending a new sequence, which is recorded in the SEQUENCE_ID. In this case, the FSW inserts the new sequence information into the SEQUENCE_ID keyword value. As a result, the first six digits of the product identifier (as originally acquired) and the SEQUENCE_ID keyword value (as downlinked) are not the same. 6. In Releases 0001-0011, all RDR products had values for two keywords, RADIANCE_OFFSET and RADIANCE_SCALING_FACTOR, when in fact, any color- corrected RDR products should have values of N/A. This was corrected for Release 0012 and onwards. RDR RADIANCE values -------------------------- _DRXX float value _DRLX float value _DRCX N/A _DRCL N/A 7. In Releases 0001-0011, all DRXX RDR products had an incorrect value of N/A for the keyword RADIOMETRIC_CORRECTION_TYPE when it should have been MMMRAD1. This was corrected for Release 0012 and onwards. 8. In Release 0013, two NAIF-related files have been added to provide additional information: a meta-kernel file, MMM_CHRONOS_V01.TM, and a CHRONOS setup file, MSL_CONSTANTS_V1.TXT. These files can be found in the EXTRAS directory. The meta-kernel file provides a list of kernels used to generate the data sets for each release. The CHRONOS setup file provides a partial set of parameters needed for SPICE's CHRONOS utility program - a program used by MSL to support time conversions (primarily to and from LTST). This file is used to generate the MARDI data sets and is not available on the NAIF site. 9. In Releases 0001-0013, the camera model for the MARDI thumbnail products was incorrect. For Release 0014 and onwards, it has been adjusted so that pixels are center-aligned with their parent, full size image. The affected values are the H and V vectors (MODEL_COMPONENT_3 and MODEL_COMPONENT_4) in the GEOMETRIC_CAMERA_MODEL_PARMS group in the .LBL file. 10. In Releases 0001-0014, flat-field calibration was applied to RDR products. For Release 0015 and onwards, the flat-field processing of RDR products will no longer be applied. The flat that was being used is unacceptably noisy for MARDI and is not useful in data generation. 11. The NAIF-related file in the EXTRAS directory, MMM_CHRONOS_V02.TM, which is a meta-kernel file, has been updated to reflect updated kernel files from NAIF. The SCLKSCET file updated from a version 0014 to a version 0015. 12. In Releases 0001-0017, the AUTO_EXPOSURE_DATA_CUT keyword in the GROUP = IMAGE_REQUEST_PARMS had NULL values. For Release 0018 onwards, the keyword has been updated to now include valid values in the .LBL file, if applicable. 13. In Releases 0001-00018, the INSTRUMENT_TEMPERATURE and MSL:INSTRUMENT_TEMPERATURE_STATUS keywords in the GROUP = INSTRUMENT_STATE_PARMS reported incorrect values. For Release 0019 onwards, the following updates have been made: INSTRUMENT_TEMPERATURE:DEA_TEMP The value will always be NULL. INSTRUMENT_TEMPERATURE:FPA_TEMP The value will always be NULL. INSTRUMENT_TEMPERATURE:ELECTRONICS_A The value will be NULL if no value is reported by the rover flight software. INSTRUMENT_TEMPERATURE:ELECTRONICS_B The value will be NULL if no value is reported by the rover flight software. INSTRUMENT_TEMPERATURE_STATUS:ELECTRONICS_B The status will be 0 if the rover flight software indicates a nominal value is available, otherwise a non-zero value will be reported. 14. When acquiring video products, the product for the first frame captures values for the current state of the rover. However, all subsequent frames within that video retain the rover state values from the first frame. As a result, some values are not accurate after the first frame. For Release 0022 onwards, the following values within the LBL and TAB files for video products will be set to NULL/UNK: LBL --------------------------------- INSTRUMENT_TEMPERATURE MSL:INSTRUMENT_TEMPERATURE_STATUS SOLAR_AZIMUTH SOLAR_ELEVATION TAB ----------------------------- INSTRUMENT_TEMPERATURE:FPA INSTRUMENT_TEMPERATURE:OPTICS SOLAR_AZIMUTH SOLAR_ELEVATION 15. The NAIF-related file in the EXTRAS directory, MMM_CHRONOS_V03.TM, which is a meta-kernel file, has been updated to reflect updated kernel files from NAIF. The SCLKSCET file updated from a version 0015 to a version 0016. 16. The NAIF-related file in the EXTRAS directory, MMM_CHRONOS_V04.TM, which is a meta-kernel file, has been updated to reflect updated kernel files from NAIF. The SCLKSCET file updated from a version 0016 to a version 0017.