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: 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. At the time of this release, there are no general errors or notes to report.