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_XXXX.TXT, contains release notes and errata identified in the MSL Mastcam raw and calibrated archives in volumes volume_0XXX_raw and volume_0XXX_calibrated, respectively. During the course of the MSL mission the Mastcam 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. 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: 7 RELEASE DATE: 2014-12-05 DATA COVERAGE: 2014-03-28 to 2014-08-03 (Sols 584-707) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: Mastcam EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: 56 EDR & 224 RDR .LBL 1. Stuck pixel in the Mastcam Right Camera There continues to be a stuck pixel around location 1214x606 and appears to bleed down the column. This was first noticed on sol 392. The bleeding seems to change based on the camera temperature at which an image is acquired. 2. Unexpected scene and image content Some images did not contain their intended target and are documented here. When an error report was filed to document the issue, it is noted below. PICNO range Description ------------------------------ --------------------------------------- 0704MR0029860000402440{E,I}01 the arm was deployed prior to imaging blocking the view of the target and resulting in the imaging of the arm 4. Camera Data Product Identifier (CDPID) jumps The following products have CDPIDs which jump from 1024 to 5070 in the middle of a sequence. This jump is due to the way the DEA assigns CDPIDs to acquired products. Refer to the Data Product SIS for a description of the PICNO format. sequence: mcam02495, sol: 593 PICNO CDPID ----------------------------- ----- 0593ML0024950000301023{E,I}01 1023 0593ML0024950010301024{E,I}01 1024 0593ML0024950020205070{E,I}01 5070 0593ML0024950030205071{E,I}01 5071 0593ML0024950040205072{E,I}01 5072 0593ML0024950050205073{E,I}01 5073 0593ML0024950060205074{E,I}01 5074 0593ML0024950070205075{E,I}01 5075 0593ML0024950080205076{E,I}01 5076 0593ML0024950090205077{E,I}01 5077 The above jump occurred since the DEA already contained products with CDPIDs 1025 thru 5069. During acquisition, the images were assigned contiguous CDPIDs. After 1024, the DEA then assigned the next available CDPID of 5070. In addition, the CDPID counter in the PICNO also changed from 03 to 02 since only one series of products had been previously acquired with CDPIDs 5070 thru 5077. Despite this jump, all of these products are contiguous. Similarly, the following sequences also had CDPID jumps, however the jump occurred between two consecutive sequences: sequence: mcam02655, sol: 620 PICNO CDPID ----------------------------- ----- 0620ML0026550000302360{D,I}01 2360 0620ML0026550010302361{D,I}01 2361 0620ML0026550020302362{D,I}01 2362 0620ML0026550030302363{D,I}01 2363 0620ML0026550040302364{D,I}01 2364 0620ML0026550050302365{D,I}01 2365 0620ML0026550060302366{D,I}01 2366 0620ML0026550070302367{D,I}01 2367 sequence:mcam02656, sol:620 PICNO CDPID ----------------------------- ----- 0620ML0026560000205101{D,I}01 5101 0620ML0026560010205102{D,I}01 5102 0620ML0026560020205103{D,I}01 5103 0620ML0026560030205104{D,I}01 5104 0620ML0026560040205105{D,I}01 5105 0620ML0026560050205106{D,I}01 5106 0620ML0026560060205107{D,I}01 5107 0620ML0026560070205108{D,I}01 5108 **************************************************************** **************************************************************** ******** SECTION B ******** This section is provided for general notes concerning the archive as a whole. 1. 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. The following values within the xml and INDEX files for video products will be set to nil: xml --------------------------------- Under the attribute: Product_Observational:Observation_Area: Discipline_Area:Imaging:Instrument_State: Device_Temperatures:Device_Temperature: device_name for DEA HEAD_FPA ELECTRONICS ELECTRONICS_A ELECTRONICS_B the keywords: temperature_value temperature_status Under the attribute: Product_Observational:Observation_Area: Discipline_Area:geom Geometry: geom Geometry_Lander: geom Derived_Geometry the keywords: geom solar_azimuth geom solar_elevation INDEX ----------------------------- Under the attribute: Product_Observational:Observation_Area: File_Area_Observational:Table_Delimited: Record_Delimited:Field_Delimited:name INSTRUMENT_TEMPERATURE:FPA INSTRUMENT_TEMPERATURE:OPTICS SOLAR_AZIMUTH SOLAR_ELEVATION 2. Clarification of the "sequence_id" in the data product .xml 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 (.xml). This is the case when the Mastcam 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. 3. 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 miscellaneous_MSLMST 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 Mastcam 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. 4. When the Sequence ID reaches the maximum allowable value of mcam16383, the Sequqnce ID will rollover and begin back at mcam00001. 5. For each frame of a GOP, various keywords within the INDEX and xml files are only partially accurate due to the way the camera hardware operates. The camera only returns the coarse SCLK and not the fine SCLK, and as a result, the fine SCLKs need to be estimated with software. This estimate will not necessarily reflect the actual time in which the frames were acquired.