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 MAHLI raw and calibrated archives in volumes volume_0XXX_raw and volume_0XXX_calibrated, respectively. During the course of the MSL mission the MAHLI 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 volume as a whole. ******** SECTION A ******** 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: MAHLI EDR & RDR PRODUCT TYPES UPDATED FOR THIS ARCHIVE: None 1. The following products were created with incorrect PICNOs for the following reason: sequence:mhli00196, sol:162 Assigned PICNO range Expected PICNO range ------------------------------ ------------------------------ 0162MH0000000000101950{I,E}01- 0162MH0019600100101950{I,E}01- 0162MH0000000000101959{I,E}01 0162MH0019601000101959{I,E}01 Reason: The sequence, mhli00196, was mistakenly commanded with tracking ID 0. The result is that neither the sequence ID nor the sequence line (command counter) were included in the PICNO, which is why the PICNO is populated with zeros. 2. Incorrect LED states PICNO range CDPID range ------------------------------ ----------- 0165MH0001880180102011O01- 2011-2025 0165MH0001880180102025O01 0165MH0001880180102011J00- 2011-2025 0165MH0001880180102025J00 0165MH0001880200102027P01- 2027-2041 0165MH0001880200102041P01 0165MH0001880210102043{N,Q}01- 2043-2055 0165MH0001880210102057{N,Q}01 Reason: When these images were acquired, all of the MAHLI LEDs were off (i.e., "0"). In the xml PDS labels, UV_LED 0 VIS1_LED 1 VIS2_LED 1 states the white LEDs were powered on (i.e., "1") which is incorrect. This is a result of a known bug in the MAHLI software. **************************************************************** **************************************************************** ******** 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_MSLMHL 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 MAHLI 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. 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.