PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT INTERCHANGE_FORMAT = ASCII PUBLICATION_DATE = 2023-09-01 NOTE = "Comments on Mars Reconnaissance Orbiter Compact Reconnaissance Imaging Spectrometer for Mars, Experiment Data Record (EDR) and Calibration Data Record (CDR) Archives (ERRATA.TXT)" END_OBJECT = TEXT END INTRODUCTION This file contains an accumulation of corrections and notes for the MRO CRISM EDR and CDR Archives. The most recent entries are listed first. Entries from 9/8/07 and earlier are the errata for all CRISM data sets, not just EDRs and CDRs. CORRECTIONS AND NOTES Sept. 1, 2023. Release 66 ------------------------- 1. This release contains engineering status data through CRISM instrument turnoff. This is the final regular CRISM data release. Jun. 1, 2023. Release 65 ------------------------ 1. This release contains only engineering status data for the time CRISM was powered on. CRISM was idle from 2022_316 - 2022_341 and 2022_344 - 2022_357. 2. This release also fixes an issue with many previously released IR CDR ATF label files where the PRODUCT_ID was incorrectly given as ATF_IR___YYYY_DOY___20 instead of the base filename. 3. The files in 2013/2013_232/ATF/ have been renamed to include the date. 4. These 2 directories, which should never have been included in the archive, have been removed: 2010_069/ATF/backup/ and 2010_353/ATF/tmp/. Mar. 1, 2023. Release 64 ------------------------ 1. This release contains only engineering status data for the time CRISM was powered on. 2. MRO went into safe mode from 2022_288 - 2022_293 and 2022_307 - 2022_310. CRISM was off during these periods. Dec. 16, 2022. -------------- 1. The remaining CDR supporting data for the MSV TRDRs have been added to the archive. Coverage is from 2021 - 2022. Dec. 1, 2022. Release 63 ------------------------ 1. Release 62 was the last of CRISM's regular observing releases. Starting with 2022_128, only engineering data will be released until CRISM is shut off permanently. 2. MRO went into safe mode from 2021_211 - 2021_215. CRISM was off during this period. Sept. 1, 2022. Release 62 ------------------------- 1. No known errors or anomalies. Jun. 1, 2022. Release 61 ------------------------ 1. CDR supporting data for the newly added MSV TRDRs have been added to the archive. Coverage is from 2012 - 2020. Data for 2021 and onwards will be included in a future release. 2. The CRISM Data Product SIS (crism_dpsis.pdf) and the CRISM Archive Volume SIS (crism_avsis.pdf) have been updated with this release. 3. The reference catalog file (ref.cat) has also been revised. Mar. 1, 2022. Release 60 ------------------------ 1. MRO went into safe mode from 2021_225 - 2021_240. There are no CRISM science data during this period. 2. There are no CRISM data from 2021_268 - 2021_297 due to solar conjunction. Dec. 1, 2021. Release 59 ------------------------ 1. No known errors or anomalies. Sept. 1, 2021. Release 58 ------------------------- 1. MRO went into safe mode from 2021_073-2021_078 and 2021_084-2021_089. There are no CRISM science data during these periods. 2. CRISM was off for MRO relay support of Perseverance EDL from 2021_049-2021_054. There are no CRISM science data during this period. Jun. 1, 2021. Release 57 ------------------------ 1. No known errors or anomalies. Mar. 1, 2021. Release 56 ------------------------ 1. No known errors or anomalies. Dec. 1, 2020. Release 55 ------------------------ 1. MRO went into safe mode from 2020_165 - 2020_172. There are no CRISM science data during this period. Sept. 1, 2020. Release 54 ------------------------- 1. No known errors or anomalies. Jun. 1, 2020. Release 53 ------------------------ 1. No known errors or anomalies. Feb. 28, 2020. Release 52 ------------------------- 1. There are no CRISM data from 2019_230 - 2019_257 due to solar conjunction. 2. Some CDR data files from 2019_211 through 2019_213 that were missing from a previous release are redelivered. Nov. 27, 2019. Release 51 ------------------------- 1. No known errors or anomalies. Aug. 30, 2019. Release 50 ------------------------- 1. No known errors or anomalies. Jun. 1, 2019. Release 49 ------------------------ 1. CRISM stopped observing on 2018_288 (Oct. 15) in preparation for MRO's data relay tasks during Mars Insight arrival and landing. Observing resumed on 2018_335 (Dec. 1). Mar. 1, 2019. Release 48 ------------------------ 1. CRISM stopped observing on 2018_288 (Oct. 15) in preparation for MRO's data relay tasks during Mars Insight arrival and landing. Observing resumed on 2018_335. Nov. 30, 2018. Release 47 ------------------------- 1. MRO went into safe mode from 2018_214 - 2018_219. There are no CRISM science data during this period. Aug. 31, 2018. Release 46 ------------------------- 1. MRO went into safe mode from 2018_047 - 2018_061. There are no CRISM science data during this period. Jun. 1, 2018. Release 45 ------------------------ 1. No known errors or anomalies. Mar. 1, 2018. Release 44 ------------------------ 1. No known errors or anomalies. Dec. 1, 2017. Release 43 ------------------------ 1. There are no CRISM data from 2017_198 - 2017_220 due to solar conjunction. Sept. 1, 2017. Release 42 ------------------------- 1. No known errors or anomalies. Jun. 1, 2017. Release 41 ------------------------ 1. No known errors or anomalies. Mar. 1, 2017. Release 40 ------------------------ 1. CRISM was off from 2016_293 - 2016_297 during the European ExoMars Schiaparelli landing attempt. There are no CRISM science data during this period. Dec. 1, 2016. Release 39 ------------------------ 1. No known errors or anomalies. Sept. 1, 2016. Release 38 ------------------------- 1. MRO went into safe mode from 2016_114 - 2016_119. There are no CRISM science data during this period. June 1, 2016. Release 37 ------------------------ 1. All MRO instruments were powered off from 2016_024 - 2016_035 for spacecraft maintenance. There are no CRISM science data during this period. March 1, 2016. Release 36 ------------------------- 1. There are no data from 2015_151 - 2015_182 due to solar conjunction. 2. CRISM was off from 2015_307 - 2015_311 due to MRO non volatile memory ephemeris updates and maintenance. There are no CRISM science data during this period. December 1, 2015. Release 35 ---------------------------- 1. MRO went into safe mode from 2015_091 - 2015-094. There are no CRISM science data during this period. September 1, 2015. Release 34 ----------------------------- 1. No known errors or anomalies. June 1, 2015. Release 33 ------------------------ 1. MRO went into safe mode from 2014_239 - 2014_244. There are no CRISM science data during this period. March 2, 2015. Release 32 ------------------------- 1. No known errors or anomalies. December 1, 2014. Release 31 ---------------------------- 1. No known errors or anomalies. September 2, 2014. Release 30 ----------------------------- 1. No known errors or anomalies. June 2, 2014. Release 29 ------------------------ 1. No known errors or anomalies. March 3, 2014. Release 28 ------------------------- 1. No known errors or anomalies. December 1, 2013. Release 27 ---------------------------- 1. There are no data from 2013_090 to 2013_124 due to solar conjunction. September 1, 2013. Release 26 ----------------------------- 1. No known errors or anomalies. June 1, 2013. Release 25 ------------------------ 1. CRISM was powered off from 2012_222 - 2012_257 during the MSL landing. There are no CRISM science data during this period. 2. MRO went into safe mode ("CMIC reset"), and CRISM was automatically shut down on 2012_289. CRISM was re-powered on 2012_292, and observations resumed on 2012_293. There are no CRISM science data from 2012_290 - 2012_291. March 1, 2013. Release 24 ------------------------- 1. CRISM observations were cancelled around 2012_155 in order to investigate gimbal alarms. There are no CRISM science data for this date. 2. CRISM was powered off from 2012_217 - 2012_221 during the MSL landing. There are no CRISM science data during this period. December 1, 2012. Release 23 ---------------------------- 1. CRISM was powered off from 2012_045 - 2012_047 so MRO could conduct relay communication tests in varying EMI environments for the upcoming MSL landing. There are no CRISM science data during this period. 2. The EDR, DDR, and TRDR data files in 2007_240/FRT00007572 are redelivered with this release. The VNIR data received for this observation were incomplete at the time of original processing, which resulted in them being placed in 2007_240/EPF00007572. This EPF directory has been removed, and the FRT directory replaced. September 1, 2012. Release 22 ----------------------------- 1. MRO went into safe mode from 2011_311 - 2011_314. There are no CRISM science data during this period. June 1, 2012. Release 21 ------------------------ 1. MRO went into safe mode from 2011_264 - 2011_267. There are no CRISM science data during this period. March 1, 2012. Release 20 ------------------------- 1. The CRISM Data Product SIS (crism_dpsis.pdf) has been updated with this release. December 1, 2011. Release 19 ---------------------------- 1. There are no CRISM data between 2011_015 and 2011_054 due to solar conjuction. September 21, 2011 ------------------ 1. Some index table file names have changed. When a month is split across volumes, the DOY range is now appended to the index table name. See indxinfo.txt in the INDEX directory for more information. September 1, 2011. Release 18 ----------------------------- 1. CRISM was off due to an MRO flight software conflict in late December (2010_355 - 2010-361). There are no data for these dates. Also, there are no data after 2011_015 due to solar conjuction. August 15, 2011 --------------- 1. The CDRs for 2008_001 through 2010_039 have been reprocessed using version 3 of the radiometric calibration. June 1, 2011. Release 17 ------------------------ 1. CRISM was commanded off during the period 2010_223 - 2010_228 to investigate anomalous scan platform behavior. There are no data for these dates. Also, there was an MRO safe mode entry which powered CRISM off as part of the safing procedure on 2010_259. CRISM resumed observing on 2010_262. 2. The CRISM Data Product SIS (crism_dpsis.pdf) and Archive Volume SIS (crism_avsis.pdf) have been updated with this release. April 15, 2011 -------------- 1. The CDRs for 2006_270 through 2007_365, as well as some CDRs in the two-letter directories on volume mrocr_0001 have been reprocessed using version 3 of the radiometric calibration. March 1, 2011. Release 16 ------------------------- 1. CRISM observations were canceled on 2010_153 due to scan motor alarms. There are no data for this date. 2. The CRISM Data Product SIS (crism_dpsis.pdf) has been updated with this release. December 1, 2010. Release 15 ----------------------------- 1. The following documentation files have been updated with this release and are currently under review: crism_avsis.pdf and crism_dpsis.pdf (DOCUMENT directory). Please be aware that these files may undergo additional revisions as a result of this review. September 1, 2010. Release 14 ----------------------------- 1. There are no CRISM data from 2009_313 - 2009_349, because MRO was in safe mode. June 1, 2010. Release 13 ------------------------ 1. There are no CRISM data from 2009_239 - 2009_312, because MRO was in safe mode. March 8, 2010. Release 12 ------------------------- 1. Several CDR PDS labels from all releases list incorrect file sizes. These errors will be fixed, and the affected CDRs will be redelivered. 2. There are no CRISM data from 2009_155 - 2009_159 and from 2009_219 - 2009_220, because MRO was in safe mode. There are no CRISM data from 2009_149 - 2009_150 and 2009_172 - 2009_173 due to a CRISM cooler switch. December 8, 2009. Release 11 ---------------------------- 1. Several CDR PDS labels from all releases list incorrect file sizes. These errors will be fixed, and the affected CDRs will be redelivered. 2. There are no CRISM data from 2009_054 - 2009_061, because MRO was in safe mode. There are no CRISM data for 2009_099 and 2009_104 due to a CRISM cooler switch. September 8, 2009. Release 10 ----------------------------- 1. Several CDR PDS labels from all releases list incorrect file sizes. These errors will be fixed, and the affected CDRs will be redelivered. 2. CRISM was powered off while MRO was in solar conjunction from 2008_326 - 2008_354. For 2009_031, most of the observations were canceled because the cooler was not maintaining the IR detector temperature. The remaining observations were not received due to the following DSN problem: 'DR M105228. Weather. All telemetry lost during pass due to snow. Not requested for retransmission due to scheduled ACE not being available.' June 8, 2009. Release 9 ---------------------------- 1. Several CDR PDS labels from all releases list incorrect file sizes. These errors will be fixed, and the affected CDRs will be redelivered. March 9, 2009. Release 8 ---------------------------- 1. Several CDR PDS labels from all releases list incorrect file sizes. These errors will be fixed, and the affected CDRs will be redelivered. 2. CRISM was off from 2008_136 - 2008_149 (scheduled), and 2008_156 - 2008_158 (unscheduled resulting from Odyssey entering safe-mode) to avoid Electra interference during Phoenix EDL and early operations. 2008_150 and 2008_151 have CDR/ST data, but no EDR observations. CRISM was cooling down during this period. 3. The RECORD_TYPE keyword is missing from several BROWSE *_raw0.lbl files. This error was previously reported and has not yet been corrected. December 8, 2008. Release 7 ---------------------------- 1. Several CDR PDS labels from all releases list incorrect file sizes. These errors will be fixed, and the affected CDRs will be redelivered. 2. As part of the routine cooler de-icing process, CRISM was off from 2008_076 - 2008_101. Science observations stopped on 2008_072 and resumed on 2008_104. An additional cooler switch was necessary, so there were also no science observations on 2008_105 and 2008_106. There are engineering data (CDR/ST) only for 2008_073 - 2008_075, 2008_102, 2008_103, 2008_105, and 2008_106. 3. The RECORD_TYPE keyword is missing from several BROWSE *_raw0.lbl files. This error was previously reported and has not yet been corrected. September 8, 2008. Release 6 ---------------------------- The following minor errors occurred in PDS labels in this release. 1. RECORD_TYPE keyword All EDR labels of the form *_validation.lbl have the RECORD_TYPE keyword in the wrong location. This error was previously reported and has not yet been corrected. The RECORD_TYPE keyword is missing from several BROWSE *_raw0.lbl files. 2. 24 EDR data products are missing their associated PDS labels, and consequently are not listed in the index tables. The missing labels should be provided prior to Release 7. 3. The STOP_TIME keyword is "NULL" in the following data file: extras/ott/obs_id_2007_11_00.lbl The appropriate value should be supplied prior to release 7. June 9, 2008. Release 5 ------------------------ The following minor errors occurred in PDS labels in this release. 1. RECORD_TYPE keyword All EDR labels of the form *_validation.lbl have the RECORD_TYPE keyword in the wrong location. This error was previously reported and has not yet been corrected. The RECORD_TYPE keyword is missing from several BROWSE *_raw0.lbl files. 2. Several EDR data products are missing their associated PDS labels, and consequently are not listed in the index tables. These include 1 BROWSE and 66 EDR data products. The missing labels should be provided prior to Release 6. 3. The STOP_TIME keyword is "NULL" in the following data file: extras/ott/obs_id_2007_11_00.lbl The appropriate value should be supplied prior to release 6. March 7, 2008. Release 4 ------------------------ The following minor errors occurred in PDS labels in this release. 1. All EDR labels of the form *_validation.lbl and several BROWSE labels of the form *_browse_edr0.lbl have the RECORD_TYPE keyword in the wrong location. This error was previously reported and has not yet been corrected. 2. Several EDR data products are missing their associated PDS labels, and consequently are not listed in the index tables. These include 9 EDRs from Release 2 and 1838 from Release 4. The missing labels will be provided prior to Release 4. December 7, 2007. Release 3 --------------------------- The following minor errors occurred in PDS labels in this release. 1. BROWSE EDR labels from 2007_040 through 2007_116 are missing the required RECORD_TYPE keyword. They should have the statement RECORD_TYPE = UNDEFINED. September 8, 2007. Release 2 ---------------------------- The following minor errors occurred in PDS labels in this release. 1. Four TRDR labels refer to an ancillary housekeeping file that is missing. These labels are: trdr/2006/2006_345/ffc00002972/ffc00002972_01_if254l_trr0.lbl trdr/2006/2006_345/ffc00002972/ffc00002972_01_ra254l_trr0.lbl trdr/2006/2006_345/ffc00002974/ffc00002974_01_if254l_trr0.lbl trdr/2006/2006_345/ffc00002974/ffc00002974_01_ra254l_trr0.lbl 2. Several CDR labels list nonstandard values for the MRO:SPECTRAL_RESAMPLING_FLAG keyword. Acceptable values are 'ON' or 'OFF,' however several files (e.g. in the 'rf' directory) list 'YES', '1', or other values for this keyword. 3. BROWSE EDR labels from 2007_006 through 2007_039 are missing the required RECORD_TYPE keyword. They should have the statement RECORD_TYPE = UNDEFINED. 4. A few EDR data products are missing their associated PDS labels, and consequently are not listed in the index tables. These data products are: edr\2006\2006_350\frt00003664\frt00003664_07_sc166l_edr0.img edr\2006\2006_351\msp0000369e\msp0000369e_04_un255l_edr0.img edr\2006\2006_351\msp0000369e\msp0000369e_04_un255l_hkp0.tab edr\2006\2006_354\msp0000377d\msp0000377d_02_un255l_edr0.img edr\2006\2006_354\msp0000377d\msp0000377d_02_un255l_hkp0.tab edr\2006\2006_354\msp0000377d\msp0000377d_02_un255s_edr0.img edr\2006\2006_354\msp0000377d\msp0000377d_02_un255s_hkp0.tab edr\2006\2006_354\msp0000377e\msp0000377e_02_un255l_edr0.img edr\2006\2006_354\msp0000377e\msp0000377e_02_un255l_hkp0.tab June 8, 2007. Release 1 ----------------------- The following minor errors occurred in PDS labels in this release. 1. 27 Level-4 CDR labels, found in directories of the form CDR\NU\*, have invalid values for FILE_RECORDS. 2. All BROWSE EDR labels are missing the required RECORD_TYPE keyword. 3. ENVI header files in CDR directories are not referenced in their associated labels. The preceding errors will be corrected with Release 2.