PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_SET_ID = "VEX-E/V-SPICE-6-V1.0" PRODUCT_ID = "ERRATA" PRODUCT_CREATION_TIME = 2008-09-15 OBJECT = TEXT INTERCHANGE_FORMAT = ASCII PUBLICATION_DATE = 2009-03-01 NOTE = "Information about errors in this dataset" END_OBJECT = TEXT END This is a list of known errors within this dataset. 1. All labels for binary kernels (SPK, CK, binary PCK) miss the FILE_RECORDS keyword which is required if RECORD_TYPE is set to FIXED_LENGTH. 2. Although there is a value ("SPICE KERNELS") for the keyword INSTRUMENT_NAME specially made for SPICE, this keyword has been set to "N/A" for all the labels in this dataset. 3. The NAIF_INSTRUMENT_ID has been set to "N/A" for all the labels in this dataset, except for Instrument Kernels (IK) and C Kernels (CK). 4. Note that all the labels for the kernels in this dataset have SPACECRAFT_CLOCK_START_COUNT and SPACECRAFT_CLOCK_STOP_COUNT set to N/A. The authors of the dataset think that it is not appropriate to put a clock count value for a product that was generated on ground. 5. No CKs for PFS and VIRTIS are provided in this dataset. This will be fixed in a future release of this dataset (not necessarily the next one). 6. Instrument Kernels (IK) for VERA, SPICAV and MAG are missing, since they are unavailable at the moment this release of the SPICE dataset was compiled. This will be fixed in a future release of this dataset. 7. DATA_SET_NAME, INSTRUMENT_ID and ORBIT_NUMBER are provided because they are mandatory keywords in the Venus Express archive. INSTRUMENT_NAME and ORBIT_NUMBER are set to "N/A". 8. The coverage for the kernel VEX_SA_2009_V0032.BC starts on 2008-12-31T23:59:60.266. The reason for that is that a leapsecond occurred on that date (hence the 60 seconds on the date string). The START_DATE keyword on the label was set to 2008-12-31T23:59:59, to allow the label to pass the software checks. 9. Note that the number of SPKs and CKs in /EXTRAS/MK/VEX_V04.TM overflow the SPKBSR and CKBSR segment buffers making the use of this file very slow. Although there is not solution for this problem at the moment this file was created, it will likely be fixed when toolkit N65 is released.