PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2008-03-07 NOTE = "This file describes known errors or deficiencies in this archive volume set." END_OBJECT = TEXT END Users are encouraged to provide comments back to the PPI Node of the PDS if errors or omissions are found either in data or in documentation. Please send comments by e-mail or U.S. mail to the PPI Node PDS Operator: Internet pds_operator@igpp.ucla.edu Telephone (310) 206-6073 U.S. Mail PDS Operator c/o Dr. Raymond Walker 3845 Slichter Hall UCLA - IGPP Los Angeles, CA 90095-1567 An updated version of this file is maintained online at the Planetary Plasma Interactions Node of the Planetary Data System. The online errata list can be found on the World Wide Web at http://pds-ppi.igpp.ucla.edu/cgi-bin/ditdos?errata=COMIMI_0XXX. Cumulative errata for the COMIMI_0XXX volume set: Logical Volume Error/Variance Description ------------------------------------------------------------------------- 1) New Static Standard Values PRODUCT_TYPE {DATA, GEOMETRY, CALIBRATION, DOCUMENT, CATALOG, SOFTWARE ANCILLARY, BROWSE} HEADER object with HEADER_TYPE = TEXT. Software change requests have been submitted to the PDS to adopt these changes to the PDS standards but they have not yet been accepted. 2) Other non-standard practices PPI has created copies of the PDS catalog files in the EXTRAS/CATALOG directory with a '.TXT' extension. While this makes the files accessible to users with the Windows operating system, it is not a standard PDS practice. In order for PPI to be able to track all of the files associated with a data set (data, documents, software, etc.) and to be able to retrieve them on-demand through our web pages, PPI must include keywords in labels that some might find questionable. In particular, we associate the same start/stop time, targets, mission phases, etc. with a document that are used in the data set. Without these keywords, queries for Cassini MAG data between times A and B would not return the documents or software associated with the data. Due to the large number of data products anticipated for this volume set the CUMINDEX.TAB is expected to grow very large. As a result that file will only be included on the Reference Volume and on the last volume in the volume set. A copy will be maintained online at the PDS/PPI website (http://www.igpp.ucla.edu/cgi-bin/ditdos? volume=COMIMI_0000&folder=INDEX&file=CUMINDEX). 3) Known problems and the volumes they affect Volumes Error Description ------- ------------------------------------------------------------------ 0000 No INDEX.TAB file (there are not data products on this volume) 0001-end LEMMS Fine Rate channel definitions do not occur on day boundaries although the channel headers inherently do. Care must be taken when applying calibration information at these boundaries so that the calibration values for the appropriate channels are used. See the COMIMI_0000\CALIBRATION\MIMI_CALIBRATION_0000.CSV for the times when these changes occur. 0001-end 2008-03-20 CHEMS PHA data files include a field called RANGE which has a nominal value in the inclusive range from 0-6. It was discovered in late 2007 that the level 1 data files as derived from the CHEMS PHA telemetry data files includes an unexpected value of 7. This value has been filtered out of the originally delivered PDS data although the records for which this value is contained are still included in the data files but the field value has been set to blank which indicates a NULL value. The blank value has been corrected to a value of 7 in future deliveries and any effected data files will be corrected in the near future. Occurances of this problem has been enumerated in the list of errata files following this description. The format of these files is intentionally made as ASCII comma separated value (CSV) so that they can be easily opened in a variety of program such as Microsoft Excel. The fields for each file are: Field# Field Name Interpretation 1 Filename Original Level 1 source file Note that the conversion from the Level 1 filename to the PDS delivered filename is provided at the end of this errata file. 2 FileRec# The data record number within the file where the problem can be found. The data record count starts after all header records in the file are read and are directly associated with the data record number of the subsequent PDS delivered file. 3 EphTime Ephemeris time of data record. Note that multiple data records can have the same ephemeris time in some data files. 4 Year Year of the data record 5 DOY Day of year of the data record 6 Hour Hour of the data record 7 Min Minute of the data record 8 Sec Second of the data record 9 Range Range value that was found to be out of the nominally accepted values. Note that this value is not provided in the PDS delivered data file but is instead set to blank or NULL. Table of errata files: Year Errata File Number of Data Records 1999 CMICHP1999_Errata.csv 1315654 2000 CHICHP2000_Errata.csv 9511 2001 CHICHP2001_Errata.csv 43 2002 CHICHP2002_Errata.csv 20 2003 CHICHP2003_Errata.csv 21 2004 CHICHP2004_Errata.csv 1146 2005 CHICHP2005_Errata.csv 23020 2006 CHICHP2006_Errata.csv 343 2007 CHICHP2007_Errata.csv 9455 Filename conversion between Level 1 data files and PDS delivered data files is as follows (as of the time of writing of this errata only the CHEMS PHA data files include this error and hence only this filename conversion is included) CMICHP_vv_ccyydoyssee_Vff.TXT.GZ ==> CPHAv_ccyydoy_hhmm.CSV.GZ Where for CMICHP_vv_ccyydoyssee_Vff.TXT.GZ the lower case characters can be interpreted as: vv = data format version number as number then alpha (1A) cc = century yy = year of century doy = day of year ss = start hour of the day (always 00) ee = end hour of the day (always 23) ff = file version number Where for CPHAv_ccyydoy_hhmm.CSV.GZ the lower case characters can be interpreted as: v = data format version number cc = century yy = year of century doy = day of year hh = starting hour of day mm = starting minute of day In addition, a summary CHICHP_errata.csv file has been created to provide the data user a quick look as to the percentage of anomalous values exist within any particular data file. The fields of this file are: 1 Year Year of the data file 2 DOY Day of Year of the data file 3 #Anom Number of anomalous data records in the file 4 #Rec Total number of data records within the file 5 %Anom Percentage of anomalous data in the file