Experiment Data Record Software Interface Specification for the MESSENGER Mercury Atmospheric and Surface Composition Spectrometer/ Ultraviolet and Visible Spectrometer (MASCS/UVVS) SIE-06-044 D Prepared by: Ray Espiritu Erick Malaret Applied Coherent Technology Corporation Document Review This document and the archive it describes have been through PDS Peer Review and have been accepted into the PDS archive. William McClintock, MESSENGER Cognizant Co-Investigator/MASCS, has reviewed and approved this document. Noam Izenberg, MESSENGER MASCS Instrument Scientist, has reviewed and approved this document. Lyle Huber, PDS Atmospheres Node Representative, has reviewed and approved this document. Susan Ensor, MESSENGER Science Operations Center Lead, has reviewed and approved this document. Document Change History Revision Number Revision Date Author Section Remarks 1 6/23/06 Start of revision history. Version submitted to PDS for Release 4. 1.1 12/30/09 J. Ward, GEO TOC, 6.3.1, Appendix 1. Added page numbers to Table of Contents. 2. Updated column 17 of UVVS.FMT to match delivered file in LABEL directory. 1.2 1/7/10 J. Ward, GEO 5.3.4 Replaced sample PDS labels with new versions containing PRODUCT_VERSION_ID. 1.3 1/12/10 J. Ward, GEO 6.3.2, Appendix Updated column 64 of MASCS_HK.FMT to match delivered file in LABEL directory. 1.4 1/14//10 J. Ward, GEO Title Page Added “Experiment Data Record” to document title. 1.5 9/15/10 J. Ward, GEO 5.2, 5.3.4, 6.1.2, 6.1.3, 6.1.4 1. Updated to describe new macro-based files. 2. Updated data product naming convention. 3. Added EXTRAS directory tables. 1.6 12/09/10 J. Ward, GEO 7 Updated archive release schedule. 1.7 5/5/11 J. Ward, GEO 6.1.3, 6.1.4 Updated to reflect new data directory structure. 1.8 6/10/11 J. Ward, GEO 6.1.4 Updated EXTRAS directory contents. 1.9 6/14/11 S. Ensor, SOC Document Review Replaced signature page with Document Review information. 2.0 6/17/11 J. Ward, GEO 6.1.4 Renamed SUPERTABLE.XLS TO MASTER_CRUISE_TABLE.XLS. 2.1 12/21/11 J. Ward, GEO 6.1.4 Updated EXTRAS directory contents. 2.2 5/25/12 S. Ensor, SOC 2, 7, 6.2 1. Update document name Data Management and Science Analysis Plan to Data Management and Archiving Plan. Update references. 2. Reference Data Management and Archiving Plan for PDS release schedule and remove release schedule table B-1 from section 7. 3. Add mission phase for second year of orbital operations. 2.3 11/12/12 J. Ward, GEO 6.1.4 Updated EXTRAS directory contents. 2.4 7/7/2015 S.Ensor 5.4.2, Various, 6.1.2 Note use of clock partitions in time tags in product labels following January 8, 2013 S/C clock reset. Change “Experimental Data Record” to “Experiment Data Record” in text. Add mission phases for third – fifth year of orbital operations. Table of Contents 1. Purpose and Scope of Document 5 1.1 Purpose 5 1.2 Scope 6 2. Applicable Documents 6 3. Relationships with other Interfaces 6 4. Roles and Responsibilities 6 5. Data Product Characteristics and Environment 7 5.1 Overview 7 5.2 Data Product Overview 7 5.3 Data Processing 8 5.3.1 Data Processing Level 8 5.3.2 Data Product Generation 9 5.3.3 Data Flow 9 5.3.4 Labeling and Identification 12 5.4 Standards Used in Generating Data Products 14 5.4.1 PDS Standards 14 5.4.2 Time Standards 14 5.4.3 Coordinate Systems 14 5.4.4 Data Storage Conventions 15 5.5 Data Validation 15 6. Detailed Data Product Specifications 15 6.1 Data Archive Structure And Organization 15 6.1.1 Handling Errors 16 6.1.2 File Naming Conventions 16 6.1.3 Directory Structure and Contents for the MASCS EDR Archive Volume 17 6.1.4 Directory Contents 17 6.2 Data Format Description 20 6.3 Label and Header Descriptions 21 6.3.1 UVVS EDR Table Columns 21 6.3.2 MASCS_HK EDR Table Columns 24 7. Archive Release Schedule to PDS 34 8. Appendices 35 APPENDIX - UVVS.FMT FILE 35 APPENDIX - MASCS_HK.FMT FILE 40 APPENDIX - SPICE Kernel Files Used In Messenger Data Products 55 APPENDIX - CODMAC 56 APPENDIX - ACRONYMS 57 APPENDIX - MASCS Instrument Overview 59 1. Purpose and Scope of Document 1.1 Purpose This document will serve to provide users of the MESSENGER UltraViolet and Visible Spectrometer (UVVS) data products with a detailed description of the UVVS instrument (Figure 1: MASCS instrument) data product generation, validation and storage. The UVVS is one component of the Mercury Atmospheric and Surface Composition Spectrometer (MASCS) instrument. This SIS will address the UVVS component of the MASCS instrument. The UVVS data products are deliverable to the Planetary Data System (PDS) and the scientific community that it supports. All data formats are based on the PDS standard. In addition this SIS provides documentation on the format and content of the MESSENGER MASCS PDS Volume Archive. The document is both a data product SIS and an archive volume SIS. Figure 1: MASCS Instrument. 1.2 Scope This specification is useful to those who wish to understand the format and content of the UVVS Experiment Data Record (EDR) data products. Typically, these individuals include scientists, data analysts, and software engineers. The SIS applies to EDR data products produced during the course of MESSENGER mission operations. Reduced and Calibrated Data Records (RDR and CDRs) are outside the scope of this SIS and are described in a separate SIS document – the UVVS RDR SIS. RDRs and CDRs are also archived in their own, separate PDS archive volume. 2. Applicable Documents The MESSENGER UVVS SIS is responsive to the following Documents: * MESSENGER Mercury: Surface, Space Environment, Geochemistry, Ranging; A mission to Orbit and Explore the Planet Mercury, Concept Study, March 1999. Document ID number FG632/ 99-0479 * Planetary Data System Standards Reference, Aug 1, 2003, Version 3.6. JPL D-7669, Part-2. * MESSENGER Data Management and Archiving Plan. The Johns Hopkins University, APL. Document ID number 7384-9019 * [PLR] Appendix 7 to the discovery program Plan; Program Level Requirement for the MESSENGER Discovery project; June 20, 2001. * MASCS Users Guide. Laboratory for Atmospheric and Space Physics, University of Colorado. Document ID number 20580-T5-5103 * Instrument Calibration Report Mercury Atmospheric and Surface Composition Spectrometer 3. Relationships with other Interfaces The UVVS data products are stored on Hard Disk and in an SQL (Structured Query Language) relational database for rapid mission access during mission operations. The data products will be electronically transferred to the PDS Geosciences and Atmospheres Nodes according to the delivery schedule in the MESSENGER Data Management and Archiving Plan. The UVVS and VIRS EDRs (detailed in the VIRS EDR SIS) have some data that would be useful in cross-comparison, therefore both the UVVS and VIRS EDR data will be grouped together in the MASCS EDR volume archive stored at both PDS nodes. The data in the EDR files themselves will be stored in a PDS TABLE object as binary tables. 4. Roles and Responsibilities The roles and responsibilities of the instrument teams, Applied Physics Lab (APL), Applied Coherent Technology (ACT), and the Planetary Data System (PDS) are defined in the MESSENGER Data Management and Archiving Plan. 5. Data Product Characteristics and Environment 5.1 Overview The UVVS will help determine the composition of the atmosphere of Mercury by; a) Measuring the spatial and vertical distribution of known species (H, O, Na, K, Ca) b) Measuring the spatial and vertical distributions of previously undetected species (S, Si, Mg, Fe, OH) The UVVS will also help in the study of the neutral coronal gas and the measure of ionized atmospheric species (Ca II, Mg II, etc.). UVVS is a scanning grating spectrometer equipped with three photo multiplier detectors. The following is a brief description of the physical aspects of the instrument: Ultraviolet and Visible Spectrometer Focal length 125 mm Grating 1800 g/mm blazed at 300 nm Spectra resolution 0.5 nm FUV channel 1.0 nm MUV, VIS channels Wavelength range: FUV channel 115-190 nm (2nd order) MUV channel 160-320 nm (1st order) VIS channel 250-600nm (1st order) Detector: FUV channel Hamamatsu R 1081 PMT - CsI MUV channel Hamamatsu R 759 PMT - CsTe VIS channel Hamamatsu R 647 PMT - Bi Alkali Field of view: FUV, MUV, VIS 1.0° x 0.04° Atmosphere FUV, MUV, VIS 0.05° x 0.04° Surface An overview of the entire MASCS instrument is contained in Appendix – MASCS Instrument Overview. 5.2 Data Product Overview There are three UVVS EDR data products, one for each detector (FUV, MUV, VIS). The detectors may also be referred to as the Photomultiplier Tube detectors (FUV PMT, MUV PMT, VIS PMT). These are identified in the PDS label as “UVVSFUV”, “UVVSMUV” and “UVVSVIS” standard data products, respectively. There is also a MASCS housekeeping EDR data product generated by the MASCS instrument. This is identified in the PDS label as the “MASCSHK” standard data product. The housekeeping EDR is defined both in this SIS and in the MASCS VIRS SIS for completeness but is the same data product. Each UVVS EDR data product consists of two files. One file contains the data itself, and is arranged in a PDS binary table format. The other file is a PDS label file, which describes the content of the data file. The label file defines the start time and end of the observation, product creation time, the structure of the binary table and each of the different fields within the table. The UVVS EDR data products all have the same binary table format but contain data specific to the FUV, MUV, or VIS detector. The UVVS EDR data product contains all the data from one observation set. An observation set is defined in three ways. 1) Before adoption of macro- based commanding on the spacecraft, one observation set contains all the CCSDS (Consultative Committee for Space Data Systems) packets generated by one photomultiplier tube in a given hour of operation. UVVS produces one CCSDS packet per scan of the instrument grating (one scan may have repeated passes and/or a zigzag across a defined number of steps). 2) After macro-based commanding of the instrument commenced, an observation set consists of the all scans and packets produced by a single macro call. The exception to this is case 3) for very long executions of high-data rate macros that produce hundreds of megabytes of calibrated data. These “fat” macros are cut subdivided into several hour chunks. A variable number of EDR products are generated each day depending on the UVVS observation plan. Each UVVS macro-based EDR contains N records, where N is based on the length of the macro, and 1 record per packet. The MASCS housekeeping EDR product contains the data from all housekeeping CCSDS packets generated in a single day. The day is defined as a 24-hour period starting from 00:00:00 to 23:59:59.999 UTC. 5.3 Data Processing 5.3.1 Data Processing Level For MESSENGER there is one archive for the UVVS instrument. The archive includes level 2 (or above) CODMAC (Committee on Data Management and Computation) data, SPICE files, standard data products, relevant software, and documentation describing the generation of the products, (see APPENDIX – CODMAC). Each product will have a unique file name across all UVVS data products (see section 6.1.2). All data level products will be stored at the Applied Physics Lab – Science Operations Center (APL/SOC). Level-1 CODMAC data will be received at the SOC where it will be ingested via an automatic data processing system and stored in a database reserved for the UVVS. Bundled with the sensor spectral data products will be scientific and engineering housekeeping data sampled by the UVVS instrument at the same time as the integral spectra onboard the spacecraft. Data downlink is telemetered through NASA’s Deep Space Network (DSN) managed by the Jet Propulsion Laboratory in Pasadena, CA, and then forwarded to APL. Inputs to the SOC will consist of telemetry in the form of CCSDS packets. The data will be available via a real-time TCP stream service and post pass FTP file service. Level-0 UVVS raw spectral and engineering data is then broken out of the data stream and stored online at the SOC. The SOC will produce early versions of the data products by utilizing SPICE kernels to enable a “quick look” functionality that lets users view the coverage areas recorded by the sensor. The early versions will be of the same type, content, and format as the final science products with default information for unknown data. Unknown data refers to the values for the PDS keywords: SPACECRAFT_POSITION_VECTOR, SUN_POSITION_VECTOR, and the target latitude and longitude keywords. The values for these keywords will be calculated via the use of SPICE kernels and will be filled in prior to delivery to PDS. 5.3.2 Data Product Generation The UVVS EDR files will be produced by the SOC, which will be operated jointly by APL and ACT. The ‘PIPE-MASCS2EDR’software converts the data to the proper PDS labeled format. This software is not part of the deliverable to the PDS archive. The EDR data products are made available to the MESSENGER Science Team during the mission for initial evaluation and validation. At the end of the evaluation and validation period, the data are organized and stored in the directory structure described in section 6.1.3 for transmittal to the Geoscience and Atmospheres Nodes. The transmittal process is described in the following section, Data Flow. PDS will then provide public access to the data products through its online data distribution system. These products will be used for engineering support, direct science analysis, and construction of other science products. Although there is enough information in the header to perform some processing, for more sophisticated processing, ancillary data will be required. Examples of ancillary data include calibration files, viewing geometry files, (e.g. SPICE kernels), index tables, etc. Calibration files and their use will be described in the UVVS RDR SIS and VIRS RDR SIS as well as in the MASCS Instrument Calibration Report. The GEOMETRY.TXT file mentioned in section 6.1.4 will contain the SPICE kernel types that will be needed by a user to generate viewing geometry. The SPICE kernel files will be archived with the PDS NAIF Node. 5.3.3 Data Flow The MESSENGER SOC operates under the auspices of the MESSENGER Project Scientist to plan data acquisition and generate and validate data archives. The SOC supports and works with the MOC, the Science Team, instrument scientists, and the PDS. The SOC will be located at the Johns-Hopkins University Applied Physics Lab (JHU/APL). During the mission operations phase the SOC will produce early versions of products that can be used by the science and instrument teams. The MESSENGER SOC will deliver data to both the PDS Geosciences and Atmospheres Nodes in standard product packages according to the schedule outlined in the MESSENGER Data Management and Archiving Plan. The UVVS and VIRS archive volumes (detailed in separate VIRS SIS) will be archived at both Nodes. Each package will comprise both data and ancillary data files, organized into directory structures consistent with the volume design described in Section 6.1.3. In the week prior to the delivery date the directory structure will be compressed into a single “zip archive” file for transmittal to both PDS Nodes. The zip archive preserves the directory structure internally so that it can be recreated after electronic delivery to the PDS Node. The zip archive file is transmitted to the PDS Node via FTP to an account set up by the receiving Node. Also transmitted will be a checksum file created using the MD5 algorithm. This provides an independent method of verifying the integrity of the zip file after it has been sent. Within days of transmittal the PDS Node will acknowledge receipt of the archive and checksum file. If acknowledgement is not received, or if problems are reported, the MESSENGER SOC will immediately take corrective action to effect successful transmittal. After transmittal the PDS Node will uncompress the zip archive file and check for data integrity using the checksum file. The Node will then perform any additional verification and validation of the data provided and will report any discrepancies or problems to the MESSENGER SOC. It is expected that the Node will perform these checks in about two weeks. After inspection has been completed to the satisfaction of the PDS Node, the Node will issue to the MESSENGER SOC acknowledgement of successful receipt of the data. Following receipt of a data delivery each Node will organize the data into PDS volume archive structure within its online data system. The Node will generate all of the required files associated with a PDS archive volume (index file, readme files, etc) as part of its routine processing of incoming MASCS data. Newly delivered data will be made available publicly from PDS once accompanying labels and other documentation have been validated. 5.3.4 Labeling and Identification The PDS label file and the EDR data file conform to the PDS version 3 standards. For more information on this standard consult the PDS Standards Reference document. The purpose of the PDS label is to describe the data product as well as provide ancillary information about the data product. The EDR data file will contain the data itself in a binary table format. There will be one detached PDS label file for every data file. There are four standard data products, “UVVSFUV”, “UVVSMUV”, “UVVSVIS”, “MASCSHK” (Section 5.2). The data files are linked to the standard data product via the STANDARD_DATA_PRODUCT_ID. The following is an example of the contents of the UVVS EDR PDS label. Details about the label format are specified in section 6.3. EXAMPLE PDS LABEL FOR THE Messenger EDR DATA PRODUCTS PDS_VERSION_ID = "PDS3" RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 7332 FILE_RECORDS = 480 PRODUCT_ID = "UFE_MC4_07_09343_064005_DAT" PRODUCT_VERSION_ID = "V1 " PRODUCT_CREATION_TIME = 2010-09-02T18:24:24 PRODUCT_TYPE = "EDR" SOFTWARE_NAME = "PIPE-MASCS2EDR" SOFTWARE_VERSION_ID = "1.0" INSTRUMENT_HOST_NAME = "MESSENGER" INSTRUMENT_NAME = " MERCURY ATMOSPHERIC AND SURFACE COMPOSITION SPECTROMETER" INSTRUMENT_ID = "MASCS" DETECTOR_ID = "UVVS" DATA_SET_ID = "MESS-E/V/H-MASCS-2-UVVS-EDR-V1.0" STANDARD_DATA_PRODUCT_ID = "UVVSFUV" MISSION_PHASE_NAME = "MERCURY 4 CRUISE" TARGET_NAME = "VENUS" TARGET_DESC = "Venus-As-Star Cal" START_TIME = 2009-12-09T06:40:05 STOP_TIME = 2009-12-09T10:07:39 SPACECRAFT_CLOCK_START_COUNT = "168828279" SPACECRAFT_CLOCK_STOP_COUNT = "168840733" ^TABLE = "UFE_MC4_07_09343_064005.DAT" OBJECT = TABLE COLUMNS = 27 INTERCHANGE_FORMAT = BINARY ROW_BYTES = 7332 ROWS = 480 DESCRIPTION = " This table contains MESSENGER UVVS spectra collected by the FUV detector and instrument engineering data. Detailed descriptions for the parameters defined below are contained in the EDR SIS document. The complete column definitions are contained in an external file found in the DATA directory of the archive volume. " ^STRUCTURE = "UVVS.FMT" END_OBJECT = TABLE END The following is an example of the contents of the MASCS housekeeping EDR PDS label. The housekeeping EDR contains instrument parameters that may be useful in analyzing the UVVS data. Details about the label format are specified in section 6.3 Label and Header Descriptions. The large amount of table fields in the housekeeping EDR necessitate the use of an external format (.FMT) file which contains all the fields for the housekeeping EDR. This format file will be placed at the top-level of the MASCS data folder to optimize archive space. The complete layout of the format file can be found in APPENDIX – MASCS_HK.FMT. EXAMPLE PDS LABEL FOR THE MASCS HOUSEKEEPING EDR PDS_VERSION_ID = "PDS3" RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 254 FILE_RECORDS = 1177 PRODUCT_ID = "MASCS_HK_09285_DAT" PRODUCT_VERSION_ID = "V1 " PRODUCT_CREATION_TIME = 2009-10-22T07:45:44 PRODUCT_TYPE = "EDR" SOFTWARE_NAME = "PIPE-MASCS2EDR" SOFTWARE_VERSION_ID = "1.1" INSTRUMENT_HOST_NAME = "MESSENGER" INSTRUMENT_NAME = " MERCURY ATMOSPHERIC AND SURFACE COMPOSITION SPECTROMETER" INSTRUMENT_ID = "MASCS" DATA_SET_ID = {"MESS-E/V/H-MASCS-2-UVVS-EDR-V1.0","MESS-E/V/H-MASCS-2-VIRS-EDR-V1.0"} STANDARD_DATA_PRODUCT_ID = "MASCSHK" MISSION_PHASE_NAME = "MERCURY 3 FLYBY" TARGET_NAME = "MERCURY" START_TIME = 2009-10-12T00:00:08 STOP_TIME = 2009-10-12T19:32:24 SPACECRAFT_CLOCK_START_COUNT = "163793074" SPACECRAFT_CLOCK_STOP_COUNT = "163863410" ^TABLE = "MASCS_HK_09285.DAT" OBJECT = TABLE COLUMNS = 95 INTERCHANGE_FORMAT = BINARY ROW_BYTES = 254 ROWS = 1177 DESCRIPTION = " This table contains MASCS Housekeeping data. Voltage, current, and temperature parameters are converted from raw DN counts into engineering data values. Detailed descriptions for the parameters defined below are contained in the EDR SIS. The complete column definitions are contained in an external file found in the DATA directory of the archive volume. " ^STRUCTURE = "MASCS_HK.FMT" END_OBJECT = TABLE END 5.4 Standards Used in Generating Data Products 5.4.1 PDS Standards The UVVS EDR data products are constructed according to the data object concepts developed by the PDS. By adopting the PDS format, the UVVS EDR data products are consistent in content and organization with other planetary data collections. In the PDS standard, the EDR data file is grouped into one or more objects with PDS labels describing the objects. For UVVS the archive uses a detached PDS label, denoting that the data is contained in a separate file rather than being contained within the PDS label file. The data itself is stored as a PDS binary table object. 5.4.2 Time Standards The SC_TIME field matches the spacecraft time in integer seconds that is transmitted to MESSENGER subsystems by the Integrated Electronics Module (IEM). It is intended to be the Mission Elapsed Time (MET). MET = 0 is August 3, 2004, at 05:59:16 UTC, which is 1000 seconds prior to the MESSENGER launch. Relativistic effects and circumstances occurring during the mission would result in MET not being a true account of seconds since launch. Following a planned spacecraft clock reset1 on January 8, 2013, partition numbers (1/, or 2/) were added to product labels to disambiguate MET seconds after the spacecraft clock reset (if partition number is not present, SPICE defaults to partition 1/). For this reason the SPICE spacecraft clock coefficients file is included as part of the archive in order to calculate the conversion between MET and UTC. 5.4.3 Coordinate Systems Table 1 lists the computational assumptions for the geometric and viewing data provided in the PDS label. There are two coordinate systems in use: 1) the celestial reference system used for target and spacecraft position and velocity vectors; and 2) the planetary coordinate system for geometry vectors and target location. The celestial coordinate system is J2000 (Mean of Earth equator and equinox of J2000). The planetary coordinate system is planetocentric. TABLE 1. - COMPUTATIONAL ASSUMPTIONS <> The start time of observation (MET) is used for the geometric element computations. <> Label parameters reflect observed, not true, geometry. Therefore, light-time and stellar aberration corrections are used as appropriate. <> The inertial reference frame is J2000 (also called EME2000). <> Latitudes and longitudes are planetocentric. <> The "sub-point" of a body on a target is defined by the surface intercept of the body-to-target-center vector. This is not the closest point on the body to the observer. <> Distances are in km, speeds in km/sec, angles, in degrees, angular rates in degrees/sec, unless otherwise noted. <> Angle ranges are 0 to 360 degrees for azimuths and local hour angle. Longitudes range from 0 to 360 degrees (positive to the East). Latitudes range from -90 to 90 degrees. <> SPICE kernel files used in the geometric parameters is outlined in APPENDIX – SPICE Kernel Files Used in MESSENGER Data Products. 5.4.4 Data Storage Conventions The data are organized following PDS standards and stored on hard disk and an SQL (Structured Query Language) relational database for rapid access during mission operations. The MESSENGER SOC will transfer data to PDS via electronic transfer and delivery methods as detailed in section 5.3.3. After verification of the data transfer PDS will provide public access to MESSENGER science data products through its online data distribution system. Binary files are all fixed-length, stored in big-endian format, and identified with the 3 letter extension “.DAT”. ASCII files are fixed length, separated by commas, and character fields are enclosed in double quotation marks (“). ASCII files are identified by the 3 letter extension “.TAB”. Data will be stored under a unique file name as defined in Section 6.1.2 5.5 Data Validation The UVVS EDR data products will be validated by the MASCS/UVVS Instrument scientist for science content and for compliance with PDS archive standards and the MESSENGER Data Management and Archiving Plan. 6. Detailed Data Product Specifications 6.1 Data Archive Structure And Organization The MESSENGER UVVS data set is a static dataset. Static data sets, once produced and validated, are not subject to update or modification. The UVVS Calibrated and Reduced Data Set, which is contained in a separate archive volume, is a dynamic dataset. Dynamic data sets have the inherent property that they continue to evolve and improve as the knowledge of the mission parameters improve. These data sets are periodically updated or replaced with new versions, and are likely to be updated by post-mission data analysis programs. As an example, the calibration files continue to evolve as knowledge of the MASCS sensor, as well as of the pointing accuracy of the MESSENGER spacecraft improves. Calibration has not been performed on the data products stored in the EDR data archive volume. The EDR data archive volume is meant to contain the data in a format close to that received from the MESSENGER spacecraft. The UVVS RDR data archive volume, which is separate from the EDR data archive volume, will contain calibrated data records and reduced data records created via calibration performed on the EDR data set. This calibration process is documented in the MASCS Instrument Calibration Report as well as in the UVVS RDR SIS. 6.1.1 Handling Errors It is inevitable that errors will be introduced into the archive even with data validation procedures applied to the volumes. As errors are discovered, they are reported to the MESSENGER SOC. An ERRATA report file is maintained to track and document all discovered errors during the mission, including any EDRs that are revised during the course of the mission. Revised EDRs or EDRs that were missing from a previous PDS delivery will be provided at the next scheduled PDS delivery or at the final PDS delivery as needed. PDS will then replace the outdated files with the revised EDR files in the data directories of the archive volume. The ERRATA report file is archived in the ROOT directory of the PDS archive volume. 6.1.2 File Naming Conventions The general form of the UVVS data file name is “UdL_mmm_XX_YYDDD_HHMMSS” where: U: UVVS d: detector (F – FUV, M – MUV, V – VIS) L: data-level. E=EDR, C=CDR, R=RDR mmm: Mission phase EAC = Earth cruise to Earth flyby EAF = Earth flyby VC1 = cruise, post Earth flyby to pre-Venus 1 flyby VF1 = Venus 1 flyby VC2 = cruise, post Venus 1 to pre-Venus 2 flyby VF2 = Venus 2 flyby MC1 = cruise, post Venus 2 to pre-Mercury 1 flyby MF1 = Mercury 1 flyby MC1 = cruise, post Mercury 1 to pre-Mercury 2 flyby MF2 = Mercury 2 flyby MC3 = cruise, post Mercury 2 to pre-Mercury 3 flyby MF3 = Mercury 3 flyby MC4 = cruise, post Mercury 3 to pre-orbit insertion ORB = Orbit insertion till end of nominal orbit mission OB2 = second year of orbital operations OB3 = third year of orbital operations OB4 = fourth year of orbital operations OB5 = fifth year of orbital operations XX: two digit macro id. It will be 00 for data created prior to the existence of UVVS macros or when PIPE cannot determine the macro id used. YY: two digit year in UTC converted from the first MET in the EDR. DDD: three digit day of year in UTC converted from the first MET in the EDR. HHMMSS: six digit hour, minute, second in UTC converted from the first MET in the EDR. The general form of the MASCS housekeeping EDR will be “MASCS_HK_YYDDD”, where: MASCS_HK: Identifies the MASCS Housekeeping EDR YY : two digit year in UTC time converted from the first MET in the EDR. DDD: three digit day of year in UTC converted from the first MET in the EDR. The housekeeping EDR is common to both the UVVS and VIRS subsystems. For the UVVS EDR and housekeeping EDR the binary table file will end with a “.DAT” extension and the detached PDS label file will end with a “.LBL” extension. 6.1.3 Directory Structure and Contents for the MASCS EDR Archive Volume Table 2 shows the directory structure overview for the MASCS EDR Archive Volume. Note that the volume contains UVVS, VIRS, and HK EDRs. Details for the VIRS EDRs are contained in a separate VIRS SIS document. This archive volume is stored at both the Atmospheres and Geosciences PDS Nodes for reasons stated in section 3. A detailed description of the directory tree is provided following TABLE 2. Empty directories are not included on the volume. TABLE 2 Directory Structure Overview __________________________________|__________________________________ | | | | | | |