PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT NOTE = "Release notes and errata for the MSL PLACES data set (ERRATA.TXT)" PUBLICATION_DATE = 2023-03-16 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 PLACES Rover Motion Counter RDR archive on the MSLPLC_1XXX volume. During the course of the MSL mission the PLACES operations team may update previously released data products or documentation. 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 entries 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 ******** 6. March 16, 2023 For Release 32, during the MSL PLACES archiving process the OPGS script flagged the following discrepancy (PLACES value versus spreadsheet value) for elevation on sol 3672: SOL: 3672, Fail elevation (98, 2704) MSL: -3858.77 -- PDS: -3859.470 -- Diff: 0.700000 The Localization Scientist MSL report indicates that OPGS reported an additional elevation value for Sol 3672, due to a second run of the PLACES query. The difference was less than 1 m elevation. Note that this took place on the sol with the site change from Site 98 to Site 99. 5. February 23, 2017 All localized_pos_demv2 and localized_interp_demv2 after Site 52, Drive 1162 should be ignored. 4. February 17, 2016 There are 5 site/drive/pose combinations where an error in the database prevented the values from being processed properly. The database errors have been fixed and these should appear properly in the next release. For this release, the reported position was 0,0,0 in global frame, so these entries have been manually deleted from the telemetry.csv, localized_interp.csv, and localized_interp_demv2.csv files (only the two drive=0 entries existed in the interp files). In all cases there are other poses available at the same site/drive, so the information loss borders on unnoticeable. The corresponding XML files in EXTRAS have NOT been edited. These positions are: 45,0,206 45,0,302 45,246,4 45,1618,2 47,1740,2 3. February 17, 2016 There have been a number of updates and additions in Release 11, most notably the addition of a Digital Elevation Model (DEM) image of the operational area. The SIS covers the changes in detail, with a summary in the change log at the end. 2. July 31, 2015 The localized_interp.csv and localized_pos.csv files were processed incorrectly. In these files, the "ROVER" frame entries with drive=0 exist solely to provide the rover orientation (roll/pitch/yaw) at the drive=0 location, because "SITE" frame by definition has roll=pitch=yaw=0. For these entries, there should be only one per Site, with pose=-1. Instead, there are sometimes multiple entries, with non-negative pose values. If you do not need roll/pitch/yaw, you can ignore these entries completely. If you do need roll/pitch/yaw, instructions are provided below. a.) For localized_interp.csv: Choose the entry with pose=0. Use the roll/pitch/yaw values for that entry, and ignore any other entries with different poses. (Non-0 pose values are not necessarily invalid, but the pose=0 is what corresponds to the site frame location.) b.) For localized_pos.csv: When a pose=0 entry is present, it should be used (same as above). When not present, go to localized_interp.csv and use the entry with the same site, where drive=0 and pose=0. Errors to be corrected in a future delivery. 1. March 16, 2015 The saved_frames.xml file in the EXTRAS/XML_ANCILLARY_DATA/ancillary directory is likely to be inaccurate due to how the saved frame data is being collected. This is addressed in the PLACES PDS SIS in the DOCUMENT directory of this volume. Users are advised to ignore this table for now; it is expected to be fixed in a future release. ******** SECTION B ******** This section is provided for general notes concerning the archive as a whole.