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: 13 RELEASE DATE: 2016-12-05 DATA COVERAGE: 2016-03-27 to 2016-08-01 (Sols 1294-1417) PRODUCT TYPES RELEASED FOR THIS ARCHIVE: Mastcam EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. 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 ------------------------------ ------------------------------------ 1305ML0062020000405737{E,I}01- a drive fault caused hardware to be 1305ML0062020030405740{E,I}01 in the field of view; an error report was filed 1321MR0063080010700626{E,I}01 unintended hardware in the field of view; no error report was filed 1326ML0063280010406088I01- target was in shadow which prevented 1326ML0063280140406101I01 effective multispectral evaluation; 1326ML0063280020406089E01 no error report was filed 1326ML0063280040406091D01 1326ML0063280060406093D01 1326ML0063280080406095D01 1326ML0063280100406097D01 1326ML0063280120406099D01 1326ML0063280140406101D01 1326MR0063280000700642I01- target was in shadow which prevented 1326MR0063280140700656I01 effective multispectral evaluation; 1326MR0063280020700644E01 no error report was filed 1326MR0063280040700646D01 1326MR0063280060700648D01 1326MR0063280080700650D01 1326MR0063280100700652D02 1326MR0063280120700654D01 1326MR0063280140700656D01 1336ML0064110000600112I01 unintended hardware in the field of view; no error report was filed 1336ML0064130000600117I01 unintended hardware in the field of view; no error report was filed 1342MR0064420000700908I01 target was farther away than usual, 1342MR0064420010700909{E,I}01- and the offset between frames was too 1342MR0064420090700917{E,I}01 high; non-overlapping frames resulted in gaps in the mosaic 1352ML0064980010600403I01- unintended hardware in the field of 1352ML0064980060600408I01 view; no error report was filed 1352ML0064980070600409{E,I}01- 1352ML0064980090600411{E,I}01 1352ML0064980360600438{E,I}01- 1352ML0064980370600439{E,I}01 1352ML0064980380600440I01- 1352ML0064980450600447I01 1352ML0064980470600449I01- 1352ML0064980500600452I01 1352ML0064980510600453{E,I}01- 1352ML0064980520600454{E,I}01 1352MR0064980010701107I01- unintended hardware in the field of 1352MR0064980020701108I01 view; no error report was filed 1352MR0064980030701109{E,I} 1352MR0064980040701110I01- 1352MR0064980060701112I01 1352MR0064980070701113{E,I}01 1352MR0064980380701144I01- 1352MR0064980440701150I01 1352MR0064980470701153I01- 1352MR0064980500701156I01 1352MR0064980510701157{E,I}01 1357ML0066130000600865{E,I}01- a drive fault caused hardware to be 1357ML0066130030600868{E,I}01 in the field of view; an error report was filed 1382ML0067720030601389{D,I}01 a mis-command in this setup sequence 1382MR0067720020701790{D,I}01 led to the target (Sun) not being centered and resulted in missing the target (Phobos) in mcam06773 2. "sequence_id" different for some data products due to a rover anomaly On Sol 1389, an anomaly occurred on board the rover, which required some previously acquired data products still residing on the rover to be downlinked in a different manner. As a result, these products exhibit the same symptoms with their SEQUENCE_ID keywords as documented in number 7 of this section. The following sequences will contain effected products: Sequence ID ----------- mcam06485 mcam06491 mcam06492 mcam06495 mcam06600 mcam06606 mcam06736 mcam06800 mcam06802 mcam06803 mcam06808 mcam06809 mcam06810 mcam06811 mcam06812 mcam06818 3. Stuck pixel in the Mastcam Left Camera There continues to be a stuck pixel at location 1069x33 (in a full-frame image) and appears to bleed down the column. This was first noticed on sol 779. 4. Stuck pixel in the Mastcam Right Camera There continues to be a stuck pixel around location 1214x606 (in a full- frame image) 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. **************************************************************** **************************************************************** ******** 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.