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: 15 RELEASE DATE: 2017-08-01 DATA COVERAGE: 2016-11-09 to 2017-03-26 (Sols 1515-1648) 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 or the target was unobservable and are documented here. When an error report was filed to document the issue, it is noted below. PICNO range Description ------------------------------ ------------------------------------ 1536ML0078700010604514{E,I}01 drill fault prior to drilling, no 1536MR0078700000104991I01- hole was drilled to document; an 1536MR0078700010104992{E,I}01 error report was filed 1543ML0079200010604635I01- drill fault precluded mast movement, 1543ML0079200070604640I01 mast was looking below the horizon 1543ML0079210010604641I01- when these images were acquired (it 1543ML0079210030604643I01 should have been pointed towards the 1543ML0079220010604644I01- sky), hence unattended hardware in 1543ML0079220070604649I01 field of view; an error report was filed 1575MR0080200010800265{E,I}01 arm fault left unintended hardware in 1575MR0080200020800266{E,I}01 field of view, an error report was filed 1609MR0082270000800971I01 unintended hardware in field of view, 1609MR0082270010800972{E,I}01 no error report was filed 1618MR0082830000801147I01- unintended hardware in field of view 1618MR0082830010801148I01 due to MAHLI fault; an error report was filed 1619MR0082910000801168{E,I}01 unintended hardware in field of view due to MAHLI fault; an error report was filed 1619ML0082930010505717{E,I}01- unintended hardware in field of view 1619ML0082930050505721{E,I}01 due to MAHLI fault; an error report was filed 2. Tau divergence between the M34 and M100 cameras There continues to be a tau divergence between the two cameras. All images with a instrument_elevation above 65 degrees for the M34 and 45 degrees for the M100 could be impacted by this contamination and should be used with caution. Images above 85 degrees for the M34 and 75 degrees for the M100 have the highest risk of contamination. Starting around image 1576MR0080270020800284{C,I}0{0,1} (Release 0015), the tau values from the left (M34) and right (M100) Mastcam images began to diverge. Tau values calculated from the M100 images (440nm) showed an increase compared to values calculated from the M34 images (880nm). This effect is believed to result from contamination of sand in the sunshade partially covering the camera lens at elevations significantly above horizontal. Though both cameras are impacted, the effect is more pronounced and prevalent in the M100. 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.