[Venus Express]-[SPICAV/SOIR] To Planetary Science Archive Interface Control Document VEX_BIRA_AR_02 Issue 004 21 April 2008 Prepared by: Arnaud MAHIEUX Verified by: Eddy NEEFS Institute: Belgian Institute for Space Aeronomy Ringlaan 3 B-1180 Brussels Belgium Change Log Date Sections Changed Reasons for Change 20/09/2006 All Creation of document from template 2/12/2006 All Corrections applied by M. Barthelemy Addition of reference spectra, BROWSE directory, … 15/12/2006 2.4.5 – 3.1.1.2 2.4.4 Addition BROWSE directory on PSA level 1B Extended description DOCUMENT directory 17/08/2007 All Updating for delivery to ESA 12/10/2007 2.3.2.1 – 2.3.2.4 2.4.3.2 – 2.4.3.3 2.4.5 – 3.1.1.1 Modify some mistakes previously not corrected 21/01/2008 2.3.2.2, 2.3.2.3, 2.3.2.4, 2.4.5, 2.4.6, 3.1.3, 3.1.4 Appendix: Content of the directories Appendix: Data product design Regression files description added, new naming of occultations description, additional wavenumber column 21/04/2008 All Reply to peer review RIDs Table of Contents Change Log 2 Table of Contents 3 1. Introduction 4 1.1. Purpose and Scope 4 1.2. Archiving Authorities 4 1.3. Contents 4 1.4. Intended Readership 4 1.5. Applicable Documents 5 1.6. Relationships to Other Interfaces 5 1.7. Acronyms and Abbreviations 5 1.8. Contact Names and Addresses 6 2. Overview of Instrument Design, Data Handling Process and Data Product 7 2.1. Instrument Design 7 2.1.1. Instrument description 7 2.1.2. Operational aspects 10 2.2. Scientific Objectives 13 2.3. Data Handling Process: SPICAV data processing, retrieval algorithms, and definitions of data levels 14 2.3.1. SOIR data processing, retrieval algorithms 14 2.3.2. Definitions of data levels 14 2.4. Overview of Data Products 22 2.4.1. Instrument Calibrations 22 2.4.2. In-Flight Data Products 22 2.4.3. Software 22 2.4.4. Documentation 23 2.4.5. Quick look products (BROWSE-directory) 24 2.4.6. Quick look products (EXTRAS-directory) 25 2.4.7. Derived and other Data Products 25 2.4.8. Ancillary Data Usage 25 2.4.9. Geo index files 26 2.5. Standards 26 2.5.1. PDS standard 26 2.5.2. Time Standards 27 2.5.3. Reference Systems 27 3. Archive Format and Content 27 3.1. Format and Conventions 28 3.1.1. Deliveries and Archive Volume Format 28 3.1.3. Data Set Name and Data Set ID Formation 34 3.1.3. Data Directory Naming Convention 36 3.1.4. Filenaming Convention 36 APPENDIX 1: Content of directories 38 APPENDIX 2: Data Product Design 43 Data product design - PSA level 1B 43 Data product design - PSA level 2 47 APPENDIX 3: Label keywords descriptions 52 Change Log 2 Table of Contents 3 1. Introduction 4 1.1. Purpose and Scope 4 1.2. Archiving Authorities 4 1.3. Contents 4 1.4. Intended Readership 4 1.5. Applicable Documents 5 1.6. Relationships to Other Interfaces 5 1.7. Acronyms and Abbreviations 5 1.8. Contact Names and Addresses 6 2. Overview of Instrument Design, Data Handling Process and Data Product 7 2.1. Instrument Design 7 2.1.1. Instrument description 7 2.1.2. Operational aspects 10 2.2. Scientific Objectives 13 2.3. Data Handling Process: SPICAV data processing, retrieval algorithms, and definitions of data levels 14 2.3.1. SOIR data processing, retrieval algorithms 14 2.3.2. Definitions of data levels 14 2.4. Overview of Data Products 22 2.4.1. Instrument Calibrations 22 2.4.2. In-Flight Data Products 22 2.4.3. Software 22 2.4.4. Documentation 23 2.4.5. Quick look products (BROWSE-directory) 24 2.4.6. Derived and other Data Products 25 2.4.7. Ancillary Data Usage 25 2.5. Standards 26 2.5.1. PDS standard 26 2.5.2. Time Standards 27 2.5.3. Reference Systems 27 3. Archive Format and Content 27 3.1. Format and Conventions 27 3.1.1. Deliveries and Archive Volume Format 27 3.1.3. Data Set Name and Data Set ID Formation 34 3.1.3. Data Directory Naming Convention 36 3.1.4. Filenaming Convention 36 APPENDIX: Content of directories 38 APPENDIX Data Product Design 43 Data product design - PSA level 1B 43 Data product design - PSA level 2 47 APPENDIX Label keywords descriptions 53 1. Introduction 1.1. Purpose and Scope This EAICD (Experimenter to (Science) Archive Interface Control Document) is exclusively dedicated to the SOIR channel of the SPICAV/SOIR instrument on board Venus Express. The purpose of this EAICD is two fold. First it provides users of the SOIR instrument with detailed description of the product and a description of how it was generated, including data sources and destinations. Secondly, it is the official interface between the SOIR instrument team and the archiving authority. 1.2. Archiving Authorities The Planetary Data System Standard is used as archiving standard by * NASA for U.S. planetary missions, implemented by PDS * ESA for European planetary missions, implemented by the Research and Scientific Support Department (RSSD) of ESA ESA implements an online science archive, the ESA’s Planetary Science Archive (PSA), * to support and ease data ingestion * to offer additional services to the scientific user community and science operations teams as e.g.: o search queries that allow searches across instruments, missions and scientific disciplines o several data delivery options as * direct download of data products, linked files and data sets * ftp download of data products, linked files and data sets The PSA aims for online ingestion of logical archive volumes and will offer the creation of physical archive volumes on request. 1.3. Contents This document describes the data flow of the SOIR instrument on VENUS EXPRESS from the S/C until the insertion into the PSA. It includes information on how data were processed, formatted, labeled and uniquely identified. The document discusses general naming schemes for data volumes, data sets, data and label files. Standards used to generate the product are explained. Software that may be used to access the product is explained. The design of the data set structure and the data product is given, with examples in appendix. 1.4. Intended Readership Any potential user of the SOIR data, and the staff of the archiving authority (Planetary Science Archive, ESA, RSSD, design team). 1.5. Applicable Documents AD1 VENUX EXPRESS - SPICAV - EAICD (Experiment to (Science) Archive Interface Control Document), Feb 14 2006, issue 00, Maud Barthelemy SA_VEX_ARCH_001 AD2 Planetary Data System (PDS) Preparation Workbook Feb 17 1995, version 3, JPL, D-7669, Part 1 AD3 Planetary Data System (PDS) Standards Reference, August 1 2003, version 3.6, JPL, D-7669, Part 2 AD4 Planetary Science Archive, Experiment Data Release Concept, Technical Proposal SOP-RSSD-TN015 AD5 Venus Express - SPICAV (SPICAM-Light + SOIR) - TC & TM parameters and formats related to SOIR SPV-BIRA-SP-06 AD6 ROSETTA/MEX/VEX Mission Control System Data Delivery Interface Document (DDID), issue C1 VEX-ESC-IF-5003 AD7 VEX BE Soft Reference and User Manual VEXBErefxxx.doc AD8 VEX SPICAV Flight User/Operations Manual SPV-DES-032 1.6. Relationships to Other Interfaces Changes in the standard SOIR data products would require changes to this document. 1.7. Acronyms and Abbreviations DDS Data Disposition System DPU Dedicated Processor Unit EAICD Experimenter to (Science) Archive Interface Control Document IASB Institut d'Aéronomie Spatiale de Belgique IKI Institute Kosmitcheski Isledovanie IR Infra Red MPS Mission Planning System N/A Not Applicable PDS Planetary Data System PSA Planetary Science Archive SA Service d'Aéronomie, CNRS SPICAV Spectroscopy for the Investigation of Characteristics of the Atmosphere of VENUS SIR SPICAV Sensor IR SU Sensor Unit SUV SPICAV Sensor UV SOIR Solar Occultation IR sensor TC Telecommand TM Telemetry UV Ultra Violet 1.8. Contact Names and Addresses Data preparation and final products delivery into the PSA are provided by the SOIR staff at the BIRA-IASB, Brussels, Belgium. NEEFS Eddy SPICAV-SOIR Co-Investigator SPICAV-SOIR Project Manager 32 (0) 2 373 03 62 eddy.neefs@bira-iasb.be BIRA MAHIEUX Arnaud SPICAV-SOIR Project Engineer 32 (0) 2 373 04 75890 98 66 arnaud.mahieux@bira-iasb.be BIRA 2. Overview of Instrument Design, Data Handling Process and Data Product 2.1. Instrument Design 2.1.1. Instrument description SOIR is a new compact space borne high resolution spectrometer developed for the ESA Venus Express spacecraft. It operates in the IR wavelength range of 2.325 to 4.25 µm and measures absorption spectra of minor constituents in Venus’ atmosphere. It uses a novel echelle grating with groove density of 4 lines per mm in a Littrow configuration, in combination with an IR Acousto-Optic Tunable Filter for order sorting and an actively cooled HgCdTe Focal Plane Array of 256 by 320 pixels. It is designed to obtain an Instrument Line Profile, full width at half maximum (FWHM), of 0.2 cm-1 and a Sampling Interval of 0.1 cm-1 per pixel over the whole spectral range The FOV in the spatial direction is limited to 30', in order to avoid solar limb darkening effects (apparent solar diameter at Venus is 44’). For the spectral direction, perpendicular to the spatial direction, the FOV is 2' (good height resolution during the inversion process of the Venus occultation data). Hence, a rectangular field of view of 2' by 30' is defined. The attitude of the VEX spacecraft during an occultation observation is controlled such that the boresight of the SOIR instrument is pointing the Sun and that the long side of the rectangular FOV remains parallel to the planet’s limb when altitude of measurement equals 65km. The mass of SOIR is 6.5 kg and its volume to 414 by 254 by 210 mm3. A periscope-like device is added to the side wall of the instrument, since the VEX solar viewing boresight is at an angle of 60° with respect to the SOIR optical axis. SOIR is thermally qualified for an operational temperature range between -20 °C and +40 °C and a non-operational between -30 °C and +50 °C. Figure 1: Optical layout of SOIR spectrometer SOIR uses an echelle grating as a diffracting device; this grating type is known to yield high reciprocal dispersion and high throughput in a compact design. Since an echelle, like all gratings, is generating overlapping orders, an order sorting filtering was required, in this case a tunable bandpass filter. Compared to orthogonal cross-dispersion solutions using prisms or low dispersion gratings, this technique allows the imaging of longer spectral lines on the detector and hence a larger binning factor along the lines, which results in higher signal-to-noise ratios. In SOIR the bandpass filter is an Acousto Optical Tunable Filter (AOTF). It has both the advantage of avoiding mechanical moving mechanisms and of a quick random access to any grating order by electronic control. Moreover, by deactivating the AOTF, one can stop all solar input to the spectrometer; this allows measuring a thermal background spectrum that can be subtracted from the observed spectrum. The spectrometer is composed of three main parts: (a) the front-end part which collects the solar light, defines the FOV and restricts the observed wavelength domain; (b) the spectrometer itself which realizes the free spectral range and the ILP and finally (c) the detector system that records the spectra according to a spectral sampling interval. Figure 1 shows the lay-out of the SOIR spectrometer. The front-end starts at the AOTF entrance optics (1) that reduce the diameter of the incoming light beam so that it becomes compatible with the AOTF acceptance aperture. In the intermediate image plane of the entrance optics a first diaphragm (2) is placed that limits the FOV to slightly larger than the desired FOV. Then the beam enters the AOTF (3) to filter out unwanted orders. When activated with an RF signal, the AOTF directs the small fraction of the beam that corresponds to the wavelength domain to be analyzed along its optical axis. The AOTF exit optics (4) images the beam on the spectrometer entrance slit (5), which is the entrance aperture for the spectrometer part of the instrument. A collimating lens (6) captures the light passing through the spectrometer entrance slit, collimates and transports it as a parallel beam to the dispersing element (7), the echelle grating located between collimator lens and imaging lens. Finally, the light diffracted by the grating is imaged via a camera lens (8) on the detector (9). Figure 2: Realistic layout of SOIR optics In order to obtain a compacted optical scheme for the high-resolution spectrometer part, a quasi-Littrow configuration was selected, in which the function of the collimation lens and of the imaging lens are merged into a single off-axis parabolic mirror. An additional benefit is that no co-alignment of two separate lenses is needed. In the detailed optical scheme and the associated ray tracing scheme, see Figure 2, the main recognizable optical units are: the entrance optics (1), the diaphragm (2), the AOTF (3), the AOTF exit optics (4), the spectrometer slit (5), the off-axis parabolic mirror (6), the echelle grating (7), the folding mirror (8), the detector optics (9) and finally the detector (10). Table 1 gives an overview of the main characteristics of the SOIR instrument. Value or range Units Wavelength range 2.32 to 4.25 µm Wavenumber range 2353 to 4310 cm-1 Spectral sampling interval 0.1 cm-1/pixel Instrument Line Profile 2 (FWHM) pixels Resolving power 23200 to 43100 ?/??=?/?? Spectral field of view 2 arc minutes Spatial field of view 30 arc minutes Entrance aperture diameter 20 mm Mass 6.5 kg Dimensions (w/o periscope) 414 x 254 x 210 mm3 Table 1: Main characteristics of the SOIR instrument 2.1.2. Operational aspects The SOIR instrument executes two operational phases in sequence: pre-cooling phase with duration T1 and observation phase with duration T2 (divided in a series of time equidistant 1 second observations, each composed of a number of spectral recordings packed into a single TM packet, together with housekeeping information related to the observation). After power-up, 2 types of TC packets are sent to SOIR by the SPICAV DPU: the first type contains all parameters related to the pre-cooling phase of the SOIR detector system and the second type contains all the parameters to define the operation of SOIR observation phase, see Figure 3. Upon reception of the first TC packet of type 1 the precooling phase is started. During this phase a TC packet of type 1 is sent every second. These packets are invitations to SOIR to send TM packets. Note that in the precooling phase the TM packets do not contain scientific data. Only housekeeping is sent, see Figure 4. Upon reception of the first TC packet of type 2 the observation phase starts during which every second a TC packet of type 2 is sent to invite SOIR to send TM packets that do contain scientific and housekeeping, see Figure 4. Figure 3: Flow diagram of SOIR operation Figure 4: Telecommand and telemetry scheme Spectra recordings contained within one observation may be taken in either of 3 ways: * AOTF frequency hopping: During each observation up to 4 random AOTF frequencies (hopping) and hence non-contiguous small wavelength domains are recorded (Figure 5). Figure 5: Frequency hopping * Single parameter stepping: During each observation a series of up to 4 wavelength domains is recorded. The parameters defining each of the domains are identical, except one which is incremented by a fixed amount from domain to domain. Single parameter stepping can be executed either continuous from one observation to the next or with a reset to a value specified by TC at each observation. A special case of single parameter stepping is AOTF frequency stepping (Figure 6): the AOTF frequency is incremented by a fixed frequency step for each sequential spectral domain, while all other parameters remain unchanged. Figure 6: General scheme for frequency stepping * Automatic window stepping: The detector is read-out completely by reading sequentially windows of 8 lines. Observations start with the detector window positioned at line 1 and for subsequent observations the window is shifted by 8 lines. In total 32 observations are required to read out the complete detector array (Figure 7). Figure 7: Automatic window stepping 2.2. Scientific Objectives The general SPICAV/SOIR scientific objectives are: Chemistry: Simultaneous measurements of O3 and H2O will allow validating and/or modifying chemistry models, from which will be derived an assessment of the oxidation environment (effect of solar UV, O3, H2O2, O, on minerals and oxidation molecules). Structure/Dynamics/Meteorology: Vertical profiles of density / temperature (20-160 km) will provide unique information about the global structure and dynamics of the atmosphere, in particular in the altitude region crucial for aerocapture and aerobraking, and a better understanding of meteorological systems. Clouds/dust/aerosols: Occultation measurements will allow the detection, measurement and characterization of the physical nature of aerosols, dust particles, and their vertical distribution. Ionosphere/escape rate: Vertical profiling of daylight aeronomic emissions (H, C, O, CO, CO2+) will allow to adjust a comprehensive model of the ionosphere, from which an estimate of escape processes may be derived (evolution of the atmosphere), and to study the interaction with the solar wind. The main SOIR target components are listed in Table 2. Species Spectral range (mm ) Altitude, precision/threshold CO2 2.7 , 4.3 60-200 km CO2 isotopes H2O 2.56 60-105 km HDO 2.56, 3.7 60-90 km H218O 2.56 Similar to HDO CO 2.35 60-150 km, 600 ppb OCS 3.44 130 H2S 2.63, 3.7 150 HCl 3.6 30 HF 2 1 SO2 4.0 60-70 km, 1.7 ppb ? C2H6 3.4 50 ppb Table 2: Main SOIR target components 2.3. Data Handling Process: SPICAV data processing, retrieval algorithms, and definitions of data levels 2.3.1. SOIR data processing, retrieval algorithms The data collected between each switch ON and switch OFF of SOIR is downlinked from the S/C to ESOC and stored on the Data Disposition System (DDS). From there it will be retrieved via ftp and stored at BIRA-IASB. Data from the DDS-files will be treated and processed at different levels, internal to the BIRA-IASB data collection structure (SOIR internal data levels). Some of these levels will be converted into deliverable PDS format levels. Retrieval algorithms and software which will be used throughout the processing steps, starting at download from DDS and stepping up from low to high archiving levels are developed at BIRA-IASB in python programming language. 2.3.2. Definitions of data levels 2.3.2.1. SOIR internal data levels Level 0.0: dds-file Level 0.1a: SOIR raw data * source dds file * product 1 raw bin files (pure telemetry) * product 2 raw csv files with updated time tag information, housekeeping values, TC copy (standard format) * structure one file per second throughout complete precooling and observation phase * data contents ADC code afo pixel number Level 0.1B: SOIR raw data in PDS format (see below) Level 0.2: SOIR data after correction step 1 * source level 0.1 csv files * action correct for non-linear detector behaviour * product csv files (standard format) * structure one file per second throughout complete precooling and observation phase * data contents arbitrary signal units afo pixel number Level 0.3: SOIR data after correction step 2 * source level 0.2 csv files * action 1. selection of useful observation period 2. division full sun reference spectrum corrected for linear time dependency of sun intensity due to spacecraft drift (linear regression of reference solar spectrum) 3. faulty pixels treatment 4. pixel-to-wavenumber conversion 5. split each selected file into 4 files (one per order) 6. separate combined sunset + sunrise observations into one sunrise and one sunset * product 1 csv files (standard format) * structure up to 4 files per second for the selected period (up to 4 orders observed per second) * data contents transmission (0 ? T ? 1) afo wavenumber * product 2 file lin_regr_coeff (csv-format) * data contents : the linear regression coefficients used for the reference solar spectrum for every pixel, for every scanned order, and for every bin Level 1.0: SOIR calibrated data in PDS format (see below) Level 2.0: SOIR science data in PDS format (see below) 2.3.2.2. Data levels deliverable to PSA The internal SOIR levels that are converted into PDS format and deliverable to PSA, are shown in Table 3. SOIR LEVEL CONTENTS PSA LEVEL CODMAC PRODUCT TYPE 0.1B raw data 1B 2 EDR – Experiment Data Record 1.0 calibrated data 2 3 RDR – Reduced Data Record 2.0 science data 3 5 DDR –Derived Data Record Table 3: Conversion between internal SOIR levels and deliverable PSA levels. Level 0.1B: SOIR raw data in PDS format * product .TAB files and associated .LBL files * structure 1 table with science contents + 2 tables with additional data (telecommand TC 1, telecommand TC 2) * science data contents ADC code afo pixel number * additional data contents telecommands of type 1 (precooling phase) and type 2 (observation phase) Level 1.0: SOIR calibrated data in PDS format * product .TAB files and associated .LBL files * structure up to 4 8 tables with science contents (1 2 tables per order, one defining the full sun reference spectrum using a linear regression as a function of time, and one containing the transmittance of each order) + 2 tables with additional data (telecommand TC 2, treatment) * science data contents time, transmission afo wavenumber, housekeeping, attitude, regression coefficients defining the linear regression of the full sun spectrum as a function of time * additional data contents telecommand of type 2 (observation phase), treatment Level 2.0: SOIR science data in PDS format * product TBD * structure TBD * science data contents TBD * additional data contents TBD A description of the data files will be given (per level) in the SOIR_DATAFILE_DESC.TXT file in the DOCUMENT directory. 2.3.2.3. PSA data level 1b construction philosophy All the data of the precooling phase (answers to TC1 type commands) and all the data of the observation phase (answers to TC2 type commands) are considered, regardless their scientific usefulness. Assume that the precooling phase lasts Npre seconds and the observation phase Nobs seconds. Each second an observation is made. Source files used for level 1b construction are the Npre + Nobs csv-files at internal SOIR level 0.1. Directory naming is based on the date of the observation YYYYMMDD, while the filenames contain both date YYYYMMDD and time hhmmss of the observation. This level has been split in pre-flight and in-flight data: ../Archiving/VEXSPI_0.1_SR_(...)/DATA/pre-flight/YYYYMMDD_ind1_ind2/csv-files/tmYYYYMMDDhhmmss.csv ../Archiving/VEXSPI_0.1_SR_(...)/DATA/in-flight/YYYYMMDD_ind1_ind2/csv-files/tmYYYYMMDDhhmmss.csv with YYYY=year, MM=month, DD=day, hh=hours, mm=minutes, ss=seconds, ind1=keyword indicating the observation period (e.g. interference, pointing, mtp01, …) , ind2=keyword indicating a subdivision in the observation period (e.g. day1, test3, occ12, …) Example: Sept 12th 2006, MTP 05, Occultation 13 Precooling phase: Npre = 598 - start 2h54’21” – end 3h04’18”: ../Archiving/VEXSPI_0.1_SR_(...)/DATA/in-flight/20060912_mtp005_occ13/csv-files/tm20060912025421.csv ... ../Archiving/VEXSPI_0.1_SR_(...)/DATA/in-flight/20060912_mtp005_occ13/csv-files/tm20060912030418.csv Observation phase: Nobs = 593 - start 3h04’22” – end 3h14’14”: ../Archiving/VEXSPI_0.1_SR_(...)/DATA/in-flight/20060912_mtp005_occ13/csv-files/tm20060912030422.csv ... ../Archiving/VEXSPI_0.1_SR_(...)/DATA/in-flight/20060912_mtp005_occ13/csv-files/tm20060912031414.csv From these (Npre + Nobs) source files the PSA data level 1b is constructed resulting in 1 science data table and 2 additional data tables (each table with its associated PDS label). All tables are in ASCII-format. The directory structure and file naming convention and the file contents are discussed in detail further on. Hence the PDS data set for one occultation consists of: 1 science data table and 1 associated label containing time, spectra and housekeeping data: ../VEXSPI_1003_1B/DATA/YYYYMMDD_IND1_IND2/YYYYMMDD_IND1_IND2_IND_OBS.TAB ../VEXSPI_1003_1B/DATA/YYYYMMDD_IND1_IND2IND/YYYYMMDD_IND1_IND2_IND_OBS.LBL 1 additional data table for “telecommand 1” (TC1 suffix) and its associated label: ../VEXSPI_1003_1B/DATA/YYYYMMDD_IND1_IND2/YYYYMMDD_IND1_IND2_IND_TC1.TAB ../VEXSPI_1003_1B/DATA/YYYYMMDD_IND1_IND2/YYYYMMDD_IND1_IND2_IND_TC1.LBL 1 additional data table for “telecommand 2” (TC2 suffix) and its associated label: ../VEXSPI_1003_1B /DATA/YYYYMMDD_IND1_IND2/YYYYMMDD_IND1_IND2_IND_TC2.TAB ../VEXSPI_1003_1B /DATA/YYYYMMDD_IND1_IND2/YYYYMMDD_IND1_IND2_IND_TC2.LBL with IND1=keyword indicating the observation period. IND1 can have the following values: * CO1, CO2 (check out 1 resp 2) * PO1, PO2 (pointing test 1 resp 2) * IFT_1, IFT_2, IFT_3, IFT_4 (interference test 1 thru 4) * VCO (Venus commissioning) * Mxx (MTP xx period). with IND2=keyword ordering the occultations inside an occultation period. IND2 can have the following values: * Oyy, where letter ‘O’ stands for ‘occultation’, and yy for the serial number inside this MTP period * Syy, where letter ‘S’ stands for ‘special measurement, and yy for the serial number inside this MTP period Example: Sept 12th 2006, MTP 05, Occultation 13 ../VEXSPI_1003_1B /DATA/20060912_M05_O13/20060912_M05_013_OBS.TAB ../VEXSPI_1003_1B /DATA/20060912_M05_O13/20060912_M05_013_OBS.LBL ../VEXSPI_1003_1B /DATA/20060912_M05_O13/20060912_M05_013_TC1.TAB ../VEXSPI_1003_1B /DATA/20060912_M05_O13/20060912_M05_013_TC1.LBL ../VEXSPI_1003_1B /DATA/20060912_M05_O13/20060912_M05_013_TC2.TAB ../VEXSPI_1003_1B /DATA/20060912_M05_O13/20060912_M05_013_TC2.LBL The science data tables contain all information that can be catalogued per second: time, spectrum, housekeeping. One column is added to distinguish precooling from observation phase data. Its format is shown in Table 4. C1 time C2 phase C3 bin0 … C10 bin7 C11 housekeeping T1 … T4 I1 … I320 I1 … I320 H1 … H16 Table 4: PSA level 1B science data table – TAB-file format Ci (i=1 to 11) are 11 columns * C1 = 4 time items Ts (s=1 to 4) corresponding to the time stamps within 1 second observation (format "2006-08-09T01:30:53.000") (4 x 23 bytes, type character) * C2 = phase ("P" for precooling, "O" for observation phase) (2 bytes, type character) * C3 to C10 = 8 spectrum bins (bin0 through bin7) each bin consisting of 320 items Ij (j=1 to 320) corresponding to pixelj (8 x 320 x 10 bytes, type ASCII_integer) * C11 = 16 housekeeping items Hk (k=1 to 16) (16 x 11 bytes, type ASCII_real) The tables contain Npre + Nobs rows. See appendix 2 for column contents details. The additional data tables for the SOIR telecommand of type 1 (issued to start the precooling phase) and type 2 (issued to start the observation phase) both have the format shown in Table 5. C1 telecommand parameter name C2 telecommand parameter value Table 5: PSA level 1B additional data table for TC1 and TC2 – TAB-file format * C1 = name of the telecommand parameter (e.g. dpss, aofs1, deit3, …) (8 bytes, type character) * C2 = value of the telecommand (8 bytes, type ASCII_integer) The TC1 table contains 10 rows; the TC2 table contains 31 rows. 2.3.2.4. PSA data level 2 construction philosophy Only the “useful” part (= the actual occultation) of the observation phase is considered. Assume a certain occultation containing N observations (= N seconds) at the internal SOIR level 0.3. Assume that in each observation (each second) spectra from P orders are registered. N is typically around 60120, P can vary from 1 to 4. Directory naming is based on the date of the observation YYYYMMDD, while the filenames contain both date YYYYMMDD and time hhmmss of the observation. Source files used for level 2 construction are the N x P internal level 0.3 science csv-files ../Archiving/VEXSPI_0.3_SR_(…)/DATA/in-flight/YYYYMMDD_mtp0aa_occbbXoccbb_c/csv/tmYYYYMMDDhhmmss_orderxxxD.csv and the corresponding attitude csv-file ../Archiving/ATTITUDE_FILES/MTPaa/YYYYMMDD_qqq.csv and the corresponding regression coefficient file of the full sun spectrum ../Archiving/VEXSPI_0.3_SR_(…)/DATA/in-flight/YYYYMMDD_mtp0aa_occbb_c/csv/lin_regr_coeff.csv with YYYY=year, MM=month, DD=day, hh=hours, mm=minutes, ss=seconds, 0aa=mtp number, bb=occultation number in current mtp, c being equal to ‘i’ in a ingress case or to ‘e’ in a egress case, xxx=order number, D a letter present in case a given order has been scanned more than once during the occultation (not always present), and qqq=orbit number and X a suffix which may exist or not, characterizing a typical property of the occultation (i.e. ‘l’ or ‘c’, ‘_miniscan’ see remark underneath). Remark: in the case a sunrise or sunset observation was part of a combined sunset/sunrise observation, the value of bb can exceptionally be composed of the occultation number in current mtp + a letter (“c” in case of sunset, ”l” in case of sunrise) or a group of letter, for example “_miniscan”). It will not be mentioned after anymore. Example: Sept 12th 2006, MTP 05, Orbit 144, Ingress, Occultation 13, P = 4 (orders per observation) Observation (second) N = 1 (3h09’033h08’22”) ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm20060912030903tm20060912030822_order126.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm20060912030822903_order127.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm20060912030822903_order128.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm20060912030822903_order129.csv ... Observation (second) N = 60 119 (3h10’023h10’00”) ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm200609120310020_order126.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm200609120310020_order127.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm200609120310002_order128.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/ tm200609120310002_order129.csv ../Archiving/ATTITUDE_FILES/MTP05/20060912_144.csv ../Archiving/VEXSPI_0.3_SR_(...)/DATA/in-flight/20060912_mtp005_occ13_i/csv/lin_regr_coeff.csv From these (N x P + 2) source files the PSA data level 2 is constructed resulting in 2P science data tables and 2 additional data tables (each table with its associated PDS label). All tables are in ASCII-format. The directory structure and file naming convention and the file contents are discussed in detail further on. Hence the PDS data set for one occultation consists of : P science data tables and P associated labels containing time, spectra, housekeeping and attitude data ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx.TAB ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx.LBL P additional data tables and P associated labels containing corresponding to the regression coefficient of the full sun spectrum file as a function of time ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_Rxxx.TAB ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_Rxxx.LBL P science data tables and P associated labels containing time, spectra, housekeeping and attitude data ../VEXSPI_1003_LEV2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx.TAB ../VEXSPI_1003_LEV2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx.LBL 1 additional data table for “telecommand” (TC2 suffix) and its associated label ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_TC2.TAB ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_TC2.LBL 1 additional data table for “treatment” (TRT_suffix) and its associated label ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_TRT.TAB ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_TRT.LBL with YYYY=year, MM=month, DD=day, aa=mtp number, t=occultation type (O for a single observation (sunrise, sunset, nadir, calibration), C for a sunset that was part of a sunrise + sunset combination, L for a sunrise that was part of a sunrise + sunset combination), bb=occultation number in current mtp, xxx=order number. Example: Sept 12th 2006, MTP 05, Orbit 144, Occultation 13, P = 4 (orders per observation) ../VEXSPI_2003_2/DATA/20060912_M05_O13C13/20060912_M05_CO13_126.TAB ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_126.LBL ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_127.TAB ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_127.LBL ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_128.TAB ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_128.LBL ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_129.TAB ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_129.LBL ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R126.TAB ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R126.LBL ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R127.TAB ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R127.LBL ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R128.TAB ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R128.LBL ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R129.TAB ../VEXSPI_2003_2/DATA/20060912_M05_C13/20060912_M05_C13_R129.LBL ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_TC2.TAB ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_TC2.LBL ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_TRT.TAB ../VEXSPI_2003_2/DATA/20060912_M05_CO13/20060912_M05_CO13_TRT.LBL The science data tables contain all information that can be catalogued per second in the observation for one specific order time, spectrum, housekeeping, attitude of the S/C. It has the format shown in Table 6. C1 time C2 wavenumber bin 1 C3 wavenumber bin 2 C4 bin 1 C5 bin 2 C6 housekeeping C7 attitude W1 … W320 W1 … W320 I1 … I320 I1 … I320 H1 … H16 A1 … A22 C1 time C2 wavenumber C3 bin 1 C4 bin 2 C5 housekeeping C6 attitude W1 … W320 I1 … I320 I1 … I320 H1 … H16 A1 … A28 Table 6: PSA level 2 science data table – TAB-file format Ci (i=1 to 67) are 67 columns * C1 = time stamp corresponding to the order in the filename (format "2006-08-09T01:30:53.000") (23 bytes, type character) * C2 = wavenumber for bin 1 consisting of 320 items Wj (j=1 to 320). Each wavenumber Wj corresponds to one pixelj (320 x 7 bytes, type ASCII_real) * C3 = wavenumber for bin 2 consisting of 320 items Wj (j=1 to 320). Each wavenumber Wj corresponds to one pixelj (320 x 7 bytes, type ASCII_real) * C2 = wavenumber consisting of 320 items Wj (j=1 to 320). Each wavenumber Wj corresponds to one pixelj (320 x 7 bytes, type ASCII_real) * C43 = spectrum from bin 1, consisting of 320 items Ij (j=1 to 320) corresponding to wavenumber Wj (320 x 10 bytes, type ASCII_real) * C54 = spectrum from bin 2, consisting of 320 items Ij (j=1 to 320) corresponding to wavenumber Wj (320 x 10 bytes, type ASCII_real) * C65 = 16 housekeeping items Hk (k=1 to 16) (16 x 11 bytes, type ASCII_real) * C76 = 22 attitude items Am (m=1 to 22) (22 x 14 bytes, type ASCII_real) See appendix 2 for column contents details. The additional data table contains the regression coefficient file of the full sun spectrum for this occultation. It has the format shown in Table 7. C1 bin number C2 ‘a’ coefficient of regression C3 ‘b’ coefficient of regression a1 … a320 b1 … b320 Table 7 : PSA level 2 data table contains the regression coefficient of the full sun spectrum – TAB-file format * C1 = bin number (1 byte, type ASCII_integer)) * C2 = 320 “a”-regression coefficients aj (j=1 to 320), for each pixel one (320 x 11 bytes, type ASCII_integer) * C3 = 320 “b”-regression coefficients bj (j=1 to 320), for each pixel one (320 x 11 bytes, type ASCII_integer) The additional data table for telecommand contains the SOIR telecommand of type 2 issued to start the observations for this occultation. It has the format shown in Table 8. C1 telecommand parameter name C2 telecommand parameter value Table 8 : PSA level 2 additional data table for TC2 – TAB-file format * C1 = name of the telecommand parameter (e.g. dpss, aofs1, deit3, …) (8 bytes, type character) * C2 = value of the telecommand (8 bytes, type ASCII_integer) The table contains 31 rows. The additional data table for telecommand contains the SOIR telecommand of type 2 issued to start the observations for this occultation. It has the format shown in Table 7. C1 telecommand parameter name C2 telecommand parameter value Table 7 PSA level 2 additional data table for TC2 – TAB-file format * C1 = name of the telecommand parameter (e.g. dpss, aofs1, deit3, …) (8 bytes, type character) * C2 = value of the telecommand (8 bytes, type ASCII_integer) The table contains 31 rows. The science data table for treatment contains the history of processes the SOIR data underwent from their retrieval from the DDS until their insertion in PSA level 2. It has the format shown in Table 9Table 8. C1 treatment action name C2 treatment action value Table 98 : PSA level 2 additional data table for TC2 – TAB-file format * C1 = name of the treatment action (e.g. 0.1_to_0.2_script_version, 0.2_to_0.3_wavenumber_correction_file, 0.3_to_1.0_PDS_creation, …) (40 bytes, type character) * C2 = value of the treatment action (16 bytes, type character) The table contains 6 rows. 2.3.2.5. PSA data level 3 construction philosophy Not used for SOIR. 2.4. Overview of Data Products 2.4.1. Instrument Calibrations All information about calibration is related to the flight model. Information needed to calibrate the SOIR data will be given in the SOIR_CALIBRATION_DESC.TXT file in the DOCUMENT directory. These documents explain how the in-flight calibration is done for the observations with the SOIR sensors. The software used to apply these calibrations is described in the SOIR_CALIBRATION_SOFTWARE.TXT document in the DOCUMENT directory. An article on SOIR calibration (published in Applied Optics) is also part of the DOCUMENT directory. 2.4.2. In-Flight Data Products During the active mission SOIR data from the CRUISE and NOMINAL phases will be collected. A SOIR data set will be defined for each data product level. 2.4.3. Software The SOIR data pass through a number of different software filters, all written in the python programming language. 2.4.3.1. Extraction from DDS – level 0.1 creation After extraction from the VEX DDS the SOIR data file is loaded into a software tool with several functions * graphical presentation of scientific data contents, second per second * graphical presentation of intensity profile throughout complete observation * graphical presentation of housekeeping values * conversion of raw DDS data to internal SOIR level 0.1 data (csv-files). Also .bin- and/or .png-files can be created upon demand 2.4.3.2. Level 0.2 and 0.3 creation The level 0.1 .csv-files are used to produce level 0.2 csv-files which contain data that are corrected for the non-linearity of the detector response. No input parameters are needed. The file conversion is strictly one to one (same number of files on level 0.2 as on level 0.1) The level 0.2 .csv-files are used to produce level 0.3 csv-files which contain data that are wavenumber calibrated (pixel number converted to wavenumber) and that have been scaled with respect to the intensity level of the full solar spectrum (reference). 2.4.3.3. PDS file creation The internal SOIR level 0.1 .csv-files are transformed (without modification to the scientific contents) into PDS format files corresponding to the PSA level 1B The internal SOIR level 0.3 .csv-files are transformed into PDS format files corresponding to the PSA level 2 Geometric attitude files (one file per observation) are generated with dedicated software using SPICE routines and SPICE kernels. These files are used to extract the relevant attitude parameters (corresponding to the zone of interest of the observation), which are then inserted in the level 1.0 (PSA level 2) data files. Relevant calibration software will be archived in the DOCUMENT directory (since the software modules are not compliant with the PSA prescription rules, hence can not be placed in the SOFTWARE directory). Information needed to read the data files will be given in the SOIR_DATAFILE_DESC.TXT file in the DOCUMENT directory. The SPICAV SOIR data can be read using the new version SBN (Small Bodies Node) software written in IDL as available for download in April 2005 from http://pdssbn.astro.umd.edu/nodehtml/software.shtml. 2.4.4. Documentation This document (EAICD) will be provided in the DOCUMENT directory in PDF and ASCII format. The SPICAV Flight User Manual (FUM) and other technical document which could be helpful to use data will be provided in the DOCUMENT directory in PDF or Microsoft Word format. The following SPICAV documents will be present in the DOCUMENT directory of each archive volume * INSTRUMENT_DESC.TXT: this document contains a description of the SOIR instrument. * SOIR_DATAFILE_DESC.TXT: this document contains a description of the SOIR data files of all PSA levels. * SOIR_CALIBRATION_DESC.TXT: this document describes the calibration of the SOIR data on the 1.0 level (PSA level 2). * INSTRUMENT_MODE_DESC.TXT: this document describes the different operating mode of the SOIR spectrometer. * SOIR_DATA_QUALITY_DESC.TXT: this document gives for each product an overview of the quality checks and parameters. * SOIR_CALIBRATION_SOFTWARE.TXT: this document describes the software used to calibrate the SOIR data (go from raw PSA level 1B to calibrated PSA level 2 data) The following RSSD documents will be present in the DOCUMENT directory of each archive volume * OBSERVATION_TYPE_DESC.TXT: this document gives the definition of the OBSERVATION_TYPE keyword values. * VEX_ORIENTATION_DESC.TXT: this document describes the convention used to describe the VEX orientation * VEX_POINTING_MODE_DESC.TXT: this document describes the values for the SPACECRAFT_POINTING_MODE keyword * VEX_SCIENCE_CASE_ID_DESC.TXT: this file describes 10 typical VEX modes of observations, called “science cases”. 2.4.5. Quick look products (BROWSE-directory) Users of the SOIR archive can make use of the BROWSE directory to have a quick look into the available data products. The structure and naming conventions for the BROWSE directory are completely identical to that of the DATA directory. PSA LEVEL 1B For each observation the following product is available in the BROWSE directory 1 jpeg file (.JPG) and its associated label containing an intensity plot of the observation ../VEXSPI_1003_1B/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_INT.JPG ../VEXSPI_1003_1B/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_INT.LBL Example Sept 12th 2006, MTP 05, Orbit 144, Occultation 13, P = 4 (orders per observation) ../VEXSPI_1003_1B/BROWSE/20060912_M05_O13C13/20060912_M05_CO13_INT.JPG ../VEXSPI_1003_1B/BROWSE/20060912_M05_CO13/20060912_M05_CO13_INT.LBL PSA LEVEL 2 For each observation the following products are available in the BROWSE directory (assuming P is the number of orders measured in that observation) P jpeg files (.JPG) and P associated labels containing an overview picture of all spectra taken in a given order during the observation plus 1 jpeg file (.JPG) containing the overall intensity plot of the observation (intensity in each bin afo time). ../VEXSPI_2003_2/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx.JPG ../VEXSPI_2003_2/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx.LBL ../VEXSPI_2003_2/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_INT.JPG ../VEXSPI_2003_2/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_INT.LBL with YYYY=year, MM=month, DD=day, aa=mtp number, t=occultation type (O for a single observation (sunrise, sunset, nadir, calibration), C for a sunset that was part of a sunrise + sunset combination, L for a sunrise that was part of a sunrise+sunset combination), bb=occultation number in current mtp, xxx=order number. Example Sept 12th 2006, MTP 05, Orbit 144, Occultation 13, P = 4 (orders per observation) ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_126.JPG ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_126.LBL ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_127.JPG ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_127.LBL ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_128.JPG ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_128.LBL ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_129.JPG ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_129.LBL ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_INT.JPG ../VEXSPI_2003_2/BROWSE/20060912_M05_O13C13/20060912_M05_O13C13_INT.LBL In the INDEX directory a BROWSE_INDEX .TAB-file and associated .LBL-file describe the contents of the BROWSE directory. Note that the last column of the BROWSE_INDEX refers to the fact whether a file in the BROWSE directory has a PRIMARY or SECONDARY status. Distinction is needed since the BROWSE directory contains 2 types of files each pointing to the same data source. 2.4.65. Quick look products (EXTRAS-directory) Some extra quick look products are also produced. They concern the same figures as the ones described in the BROWSE directory, but they are presented as animated GIF files. P animated gif files (.GIF) and P associated labels containing an measurement by measurement animation of all spectra taken in a given order during the observation ../VEXSPI_1003_2/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx_ANIM.GIF ../VEXSPI_1003_2/BROWSE/YYYYMMDD_Maa_tbb/YYYYMMDD_Maa_tbb_xxx_ANIM.LBL with YYYY=year, MM=month, DD=day, aa=mtp number, t=occultation type (O for a single observation (sunrise, sunset, nadir, calibration), C for a sunset that was part of a sunrise + sunset combination, L for a sunrise that was part of a sunrise+sunset combination), bb=occultation number in current mtp, xxx=order number. Example Sept 12th 2006, MTP 05, Orbit 144, Occultation 13, P = 4 (orders per observation) ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_126_ANIM.GIF ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_126_ANIM.LBL ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_127_ANIM.GIF ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_127_ANIM.LBL ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_128_ANIM.GIF ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_128_ANIM.LBL ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_129_ANIM.GIF ../VEXSPI_2003_2/EXTRAS/20060912_M05_O13C13/20060912_M05_O13C13_129_ANIM.LBL 2.4.76. Derived and other Data Products Delivery of any other derived data or data products resulting from cooperation with other instrument teams is not foreseen. 2.4.87. Ancillary Data Usage SPICE files produced by PST/ESTEC in collaboration with NAIF/JPL from the VENUS Express orbit files generated by ESOC will be used in our data processing chain, in particular to generate geometry and attitude files. SPICE files are available from the following file servers: At ESTEC FTP Server ftp://gorilla.estec.esa.int/pub/projects/VenusExpress/data/spice/ At NAIF FTP Server: ftp://naif.jpl.nasa.gov/pub/naif/VEX Available SPICE files are: 1. SPK spacecraft/planet/satellites/asteroids ephemeris data kernel files 2. EK event kernel – no EK available for VENUS EXPRESS 3. CK C-matrix instrument attitude kernel files 4. LSK leap second kernel files 5. FK frame kernel files 6. IK instrument kernel files 7. PCK planetary constant kernel files 8. SCLK spacecraft clock kernel files Orbit numbering files, which are derived data product from the VEX kernel data set, are also available at ESTEC or NAIF FTP Servers (in the ORBNUM directory). SPICE subroutines are also available at ftp://naif.jpl.nasa.gov/pub/naif/toolkit/ to help the use of these kernels and tutorials and documentation can be retrieved from http://naif.jpl.nasa.gov/naif/tutorials.html and http://naif.jpl.nasa.gov/naif/documentation.html. 2.4.89. Geo index files One geometry index .TAB-file with its associated .LBL-file is generated for the whole data set : ../VEXSPI_2003_2/INDEX/GEO_VENUS.LBL ../VEXSPI_2003_2/INDEX/GEO_VENUS.TAB The .TAB-file is a list of consecutive footprints, one footprint for every observation in the data set. Each footprint consists of a number of lines in the table, each line corresponding to a measurement, i.e. there are as much lines in the footprint as there are seconds in the observation. The footprint however is limited to measurements that have a tangential height of the SOIR boresight between 220 and 40 km (last column in GEO index table). It is possible that for certain measurements (highest or lowest tangential heights) no measurements were taken. In that case N/A values (999.999 or -999.999) are placed in the table for geometric parameters that can not be calculated. Each line in the GEO index table contains a number of geometric parameters describing the exact location of each measurement. The geometric parameters are documented in the corresponding DESCRIPTION fields in the .LBL-file. The 6 parameters describing the footprint are (START_POINT_LATITUDE, START_POINT_LONGITUDE), (CENTER_LATITUDE, CENTER_LONGITUDE), (END_POINT_LATITUDE, END_POINT_LONGITUDE). The CENTER point is the tangential point itself projected on a 60 km altitude shell around Venus. The START point and END point are points at the left and the right of the CENTER point, so that at each measurement (each second) not one point but one line is defined as footprint of the measurement. The complete footprint of the observation is then a sequence of such traces or the contour described by the extremes of the traces (the START and the END points). START and END point are situated in a tangential plain to the planet, perpendicular to the boresight, at a distance of 10 km (when the tangential height is between 40 and 100 km) and at variable distance (when the tangential height is between 100 and 220 km). This variable distance is calculated by linear regression between the 2 following (tangential height, distance to center)-points : (100 km, 10 km), (250 km, 500 km). 2.5. Standards 2.5.1. PDS standard The PDS standard used to describe data products in the SOIR archive is that of PDS version 3.6 [2]. Each PDS archived product is described using label objects that provide information about the data types of stored values. In order to identify and describe the organization, content, and format of each data product, PDS requires a distinct data product label for each individual data product file. This data product label can be attached or detached from the data. The SOIR PDS data product label is detached from the data and resides in a separate file which contains a pointer to the data product file. There is one detached label file for every data product file. The label file should have the same base name as its associated data file, but the extension is .LBL. Each PDS label must begin with the PDS_VERSION_ID data element. This element identifies the published version of the standards to which the label adheres. For labels adhering to the standards version 3.6 the appropriate value is “PDS3”: PDS_VERSION_ID = PDS3 PDS data product labels contain data element informations that describe important attributes of the physical structure of a data product file. The PDS file characteristic data elements are: RECORD_TYPE , RECORD_BYTES , FILE_RECORDS. The RECORD_TYPE data element identifies the record characteristics of the data product file. The RECORD_BYTES data element identifies the number of bytes in each physical record in the data product file. The FILE_RECORDS data element identifies the number of physical records in the file. The following data identification elements must be included in product labels for all spacecraft science data products: DATA_SET_ID , PRODUCT_ID , INSTRUMENT_HOST_NAME , INSTRUMENT_NAME , TARGET_NAME , START_TIME , STOP_TIME , SPACECRAFT_CLOCK_START_COUNT , SPACECRAFT_CLOCK_STOP_COUNT , PRODUCT_CREATION_TIME. The PDS requires a separate data object definition within the product label for each object in the product, to describe the structure and associated attributes of each constituent object. Object definitions are of the form: OBJECT = aaa where aaa is the name of the data object ... END_OBJECT = aaa The PDS uses a pointer within the product labels to identify the file location for all objects which are described in the label file. For example ^SOIR_TABLE = "20060809_M04_O03C03_120.TAB" 2.5.2. Time Standards The PDS formation rule for dates and time in UTC is: YYYY-MM-DDThh:mm:ss.fff or YYYY-DDDThh:mm:ss.fff With YYYY = year (0000-9999), MM = month (01-12), DD = day of month (01-31), DDD = day of year (001-366), T = date/time separator, hh = hour (00-23), mm = minute (00-59), ss = second (00-59), fff = fractions of second (000-999) (restricted to 3 digits) The START_TIME and STOP_TIME data elements required in data product labels and catalog templates use the UTC format. Times in any format other than the ISO/DIS 8601 format described above are considered to be in a format native to the data set, and thus “native times”. The spacecraft clock reading often provides the essential timing information for a space-based observation. Therefore, the elements SPACECRAFT_CLOCK_START_COUNT and SPACECRAFT_CLOCK_STOP_COUNT are required in labels describing space-based data. This value is formatted as a string to preserve precision. Spacecraft clock counts shall be represented as a right-justified character string field with a maximum length of thirty characters. The SPACECRAFT_CLOCK_START_COUNT and SPACECRAFT_CLOCK_STOP_COUNT represent the on-board time counters (OBT) of the spacecraft and instrument computers. This OBT counter is given in the headers of the experiment telemetry source packets. It contains the data acquisition start time as 32 bit of unit seconds followed by 16 bit of fractional seconds. The time resolution of the fractional part is 2^-16 = 1.52×10^-5 seconds. Thus the OBT is represented as a decimal real number in floating-point notation with 5 digits after the decimal point. A reset of the spacecraft clock is represented by an integer number followed by a slash, e.g. “1/” or “2/”. Examples SPACECRAFT_CLOCK_START_COUNT = "1/21983325.39258" SPACECRAFT_CLOCK_START_COUNT = "21983325.39258" SPACECRAFT_CLOCK_START_COUNT = "2/0000325.39008" 2.5.3. Reference Systems The SOIR data products are not projected into any coordinate system, however some basic geometric parameters are provided in the data files (described in the associated detached labels) and in the GEO_VENUS index tables. 3. Archive Format and Content This section describes the format of SOIR Archive Volumes. Data in the archive will be formatted in accordance with Planetary Data System specifications [2]. 3.1. Format and Conventions 3.1.1. Deliveries and Archive Volume Format 3.1.1.1. SPICAV Deliveries At the end of the priority phase the data will be delivered to PSA at ESTEC. BIRA-IASB is the single point of contact for the PSA archive team and for data distribution (during priority phase). Deliveries to the PSA will be made by the SOIR archive team. Target date for delivery of SOIR data (both PSA level 1b and 2) to PSA is 4 months after the end of a specific VEX mission phase. 3.1.1.2. Archive Volume Format and Concept of Deliveries The SOIR_ARCHIVE volume set contains 3 archive volumes, each corresponding to a specific data level (Figure 8) * VEXSPI_1003_1B SOIR data level 0.1b = PSA data level 1b * VEXSPI_2003_2 SOIR data level 1.0 = PSA data level 2 * VEXSPI_3003_3 SOIR data level 2.0 = PSA data level 3 (TBD) Figure 8 SOIR archive directory structure Each SPICAV archive volume has the name of the VOLUME_ID. In each archive volume, the following standard directories are included: * DATA contains one or more subdirectories of data products with data files (.TAB) and detached label files (.LBL) * CATALOG PDS catalogue files * INDEX indices to assist in locating data of interest + GEO_VENUS index (footprints) * DOCUMENT documentation, supplementary and ancillary information to assist in understanding and using the data products. + calibration software * CALIB calibration files to process the data * SOFTWARE not used * GEOMETRY: not used * BROWSE At PSA level 1B intensity plot. At PSA level 2 1 intensity plot, P order overview plots, * EXTRAS (only at level2) P order animations (P = number of orders measured during a certain observation) In the ROOT directory of each archive volume, 2 files give an overview of the archive volume in ASCII format (AAREADME.TXT file) and a description of the volume in PDS format (VOLDESC.CAT file). Within the Planetary Science Archive (PSA) the archive volume represents an online delivery. Deliveries are based on the concept of a release and a revision of a well-defined period of time. This concept [4] allows the delivery of experiment data without the delivery of all supplementary information, that has already been delivered at the first initial delivery of a fully PDS compatible archive volume, containing the VOLDESC.CAT file and all necessary CATALOG, DOCUMENT, INDEX, DATA,… directories and their content. The usage of the release object is not fully compliant with the PDS standard 3.6, however the full data set itself is PDS compatible. This concept should be transparent to the end user. 3.1.1.3. VOLDESC.CAT file The VOLDESC.CAT file gives a description of the archive volume in a PDS format. Example PSA level 2 SOIR data volume, release 0001, revision 0000 PDS_VERSION_ID = PDS3 RELEASE_ID = 0001 REVISION_ID = 0000 OBJECT = VOLUME DATA_SET_ID = "VEX-Y/V-SPICAV-3-SOIR-V1.0" DESCRIPTION = "This volume contains the PSA level 2 SOIR data" MEDIUM_TYPE = "ONLINE" PUBLICATION_DATE = 2006-10-05 VOLUME_FORMAT = "ISO-9660" VOLUME_ID = VEXSPI_2003 VOLUME_NAME = "VOLUME 3: SPICAV SOIR VENUS EXPRESS DATA" VOLUME_SERIES_NAME = "MISSION TO VENUS" VOLUME_SET_NAME = "VENUS EXPRESS SPICAV DATA PRODUCTS" VOLUME_SET_ID = BE_BIRA_IASB_VEXSPI_2000 VOLUME_VERSION_ID = "VERSION 1" VOLUMES = 1 OBJECT = CATALOG ^DATA_SET_CATALOG = "DATASET.CAT" ^INSTRUMENT_CATALOG = "INST.CAT" ^INSTRUMENT_HOST_CATALOG = "INSTHOST.CAT" ^MISSION_CATALOG = "MISSION.CAT" ^REFERENCE_CATALOG = "REFERENCE.CAT" ^DATA_SET_RELEASE_CATALOG = "RELEASE.CAT" ^SOFTWARE_CATALOG = "SOFTWARE.CAT" END_OBJECT = CATALOG OBJECT = DATA_PRODUCER INSTITUTION_NAME = "BELGIAN INSTITUTE FOR SPACE AERONOMY" FACILITY_NAME = "N/A" FULL_NAME = "EDDY NEEFS" ADDRESS_TEXT = "RINGLAAN 3 1180 BRUSSELS" END_OBJECT = DATA_PRODUCER END_OBJECT = VOLUME END 3.1.1.3.1. VOLUME_ID The VOLUME_ID of a SOIR archive volume is composed by combining the following fields * the mission identifier VEX * the instrument identifier SPI * an underscore * a 4 digit sequence number dedicated to the SOIR data: 1003 (L1B), 2003 (L2), 3003 (L3) Hence the VOLUME_ ID for SOIR is VEXSPI_1003 (L1B), VEXSPI_2003 (L2), VEXSPI_3003 (L3). If a volume is refurbished because of errors in the initial production, the VOLUME_ID remains the same while the VOLUME_VERSION_ID is incremented. 3.1.1.3.2. VOLUME_SET_ID Each SOIR archive volume is also identified by a VOLUME_SET_ID composed by combining the following fields * the country abbreviation BE * the government branch BIRA * the discipline IASB * the mission identifier VEX * the instrument identifier SPI * a 4 digit sequence number The VOLUME_SET_ID for SOIR is BE_BIRA-IASB_VEXSPI_1000 (L1B) , BE_BIRA-IASB_VEXSPI_2000 (L2) , BE_BIRA-IASB_VEXSPI_3000 (L3) , 3.1.1.3.3. RELEASE_ID and REVISION_ID A data set release (or volume release) contains data from a well-defined period of time and is identified by a RELEASE_ID keyword. The first release (RELEASE_ID = 0001) is a fully validated, complete PSA data set. A volume release is made of at least one revision the initial revision. The initial revision contains the initial data of a data set release and is identified by a REVISION_ID equal to 0000. All labels within the first release will also contain the keywords RELEASE_ID = 0001 REVISION_ID = 0000 A following revision of the data set release (updated files, supplementary files, deleted files) would need the value of the REVISION_ID incremented by one (eg. RELEASE_ID = 0001, REVISION_ID = 0001). Labels of the updated files will have the keywords RELEASE_ID = 0001 REVISION_ID = 0001 Any further release covering a following period of time would need the value of the RELEASE_ID incremented by one, with an initial revision (eg. RELEASE_ID = 0002, REVISION_ID = 0000). The new data labels will contain the keywords RELEASE_ID = 0002 REVISION_ID = 0000 The VOLDESC.CAT file shall contain the keywords RELEASE_ID and REVISION_ID set to the latest RELEASE_ID and within this release to the latest REVISION_ID. 3.1.1.3.4. CATALOG object The VOLDESC.CAT file contains a CATALOG object with pointers to catalog files stored in the CATALOG directory. Files in the CATALOG directory provide a top-level understanding of the mission, spacecraft, instruments, and data sets. One of these files, the RELEASE.CAT catalog file, contains a release object, which fully defines the releases and revisions of deliveries. 3.1.1.4. The release object A release object needs to be included in each archive volume to fully describe each release and revision within this release. This object is not PDS-compliant. Example PSA level 2 SOIR data volume, release 0001, revision 0000 PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = "E.NEEFS, 2006-10-06 (original)" RECORD_TYPE = STREAM RELEASE_ID = 0001 REVISION_ID = 0000 OBJECT = DATA_SET_RELEASE DATA_SET_ID = "VEX-Y/V-SPICAV-3-SOIR-V1.0" RELEASE_ID = 0001 DESCRIPTION = " This release contains the PSA level 2 data of the SOIR instrument on board of spacecraft Venus Express. These data underwent a number of correction and calibration procedures. This release contains data measured between May 12th 2006 (orbit 21) and August 31st 2006 (orbit 132). Revision 0000 contains the original delivery. " OBJECT = REVISION REVISION_ID = 0000 REVISION_DATE = 2006-10-06 REVISION_MEDIA = "ONLINE" DESCRIPTION = "FIRST DELIVERY: RELEASE 0001,REVISION: 0000" END_OBJECT = REVISION END_OBJECT = DATA_SET_RELEASE END A release will concern a well-defined period of time, based on the nominal science mission timeline, as shown in the SOIR archive volume delivery schedule (section 0). Each release will be described in this file by a DATA_SET_RELEASE object, containing all keyword-value pairs that are necessary to identify the release (DATA_SET_ID, RELEASE_ID, DESCRIPTION, …). The DESCRIPTION part of the DATA_SET_RELEASE object will contain the full history of the release including all previous revisions. Each revision of a release is added in the release catalog object and all necessary information about this revision is given by a REVISION object. A revision of this release might be added after improvement of the data. Example PSA level 2 SOIR data volume, release 0001, revision 0001 PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = "E.NEEFS, 2006-10-07 (original)" RECORD_TYPE = STREAM RELEASE_ID = 0001 REVISION_ID = 0000 OBJECT = DATA_SET_RELEASE DATA_SET_ID = "VEX-Y/V-SPICAV-3-SOIR-V1.0" RELEASE_ID = 0001 DESCRIPTION = " This release contains the PSA level 2 data of the SOIR instrument on board of spacecraft Venus Express. These data underwent a number of correction and calibration procedures. This release contains data measured between May 12th 2006 (orbit 21) and August 31st 2006 (orbit 132). Revision 0000 contains the original delivery. " OBJECT = REVISION REVISION_ID = 0000 REVISION_DATE = 2006-10-06 REVISION_MEDIA = "ONLINE" DESCRIPTION = "FIRST DELIVERY: RELEASE 0001,REVISION: 0000" END_OBJECT = REVISION OBJECT = REVISION REVISION_ID = 0001 REVISION_DATE = 2006-10-07 REVISION_MEDIA = "ONLINE" DESCRIPTION = "RELEASE 0001,REVISION: 00001, Modification of the label files" END_OBJECT = REVISION END_OBJECT = DATA_SET_RELEASE END A following release of a new well defined period of time in the archive volume will be described by a new DATA_SET_RELEASE object in the same RELEASE.CAT file. Example PSA level 2 SOIR data volume, release 0002, revision 0000 PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = "E.NEEFS, 2006-10-08 (original)" RECORD_TYPE = STREAM RELEASE_ID = 0002 REVISION_ID = 0000 OBJECT = DATA_SET_RELEASE DATA_SET_ID = "VEX-Y/V-SPICAV-3-SOIR-V1.0" RELEASE_ID = 0002 DESCRIPTION = " This release contains the PSA level 2 data of the SOIR instrument on board of spacecraft Venus Express. These data underwent a number of correction and calibration procedures. This release contains data measured between September 1st 2006 (orbit 133) and November 30th 2006 (orbit 223). Revision 0000 contains the original delivery. " OBJECT = REVISION REVISION_ID = 0000 REVISION_DATE = 2006-10-08 REVISION_MEDIA = "ONLINE" DESCRIPTION = "SECOND DELIVERY: RELEASE 0002,REVISION: 0000" END_OBJECT = REVISION END_OBJECT = DATA_SET_RELEASE OBJECT = DATA_SET_RELEASE DATA_SET_ID = "VEX-Y/V-SPI-1-SOIRSPECTRA-V1.0" RELEASE_ID = 0001 DESCRIPTION = " This release contains the PSA level 2 data of the SOIR instrument on board of spacecraft Venus Express. These data underwent a number of correction and calibration procedures. This release contains data measured between May 12th 2006 (orbit 21) and August 31st 2006 (orbit 132). Revision 0000 contains the original delivery. " OBJECT = REVISION REVISION_ID = 0000 REVISION_DATE = 2006-10-06 REVISION_MEDIA = "ONLINE" DESCRIPTION = "FIRST DELIVERY: RELEASE 0001,REVISION: 0000" END_OBJECT = REVISION OBJECT = REVISION REVISION_ID = 0000 REVISION_DATE = 2006-10-07 REVISION_MEDIA = "ONLINE" DESCRIPTION = "RELEASE 0001,REVISION: 00001, Modification of the label files" END_OBJECT = REVISION END_OBJECT = DATA_SET_RELEASE END 3.1.1.5. Index files The PDS standard defines index files containing information that allows a user to locate data of interest. The index table files below the INDEX directory cover all data set releases and revisions. Therefore the index table files will contain at least two columns named RELEASE_ID and REVISION_ID. The index label files describing the index table files shall contain the keywords RELEASE_ID and REVISION_ID, set to the latest RELEASE_ID and within this release to the latest REVISION_ID (same as the VOLDESC.CAT file). The INDEX directory will contain 3 types of index files INDEX.TAB : the index into the DATA directory BROWSE.TAB : the index into the BROWSE directory GEO_VENUS.TAB : the footprints of all the observations in the data set To each .TAB file is associated a detached .LBL label file. 3.1.2. Data Set Name and Data Set ID Formation Each PDS data set must have a unique name (DATA_SET_NAME) and a unique identifier (DATA_SET_ID). The name and identifier should be composed based on the following elements * Instrument host name : VENUS EXPRESS * Target : e.g. VENUS/SKY * Instrument host ID : VEX * Target ID : e.g. V (VENUS), Y (SKY/CRUISE) * Instrument ID : SPICAV * Data processing level number : see below * Mission phase abbreviation (optional) : see below * Description (optional) : see below * Version number : e.g. V1.0 Within the DATA_SET_NAME, elements are separated by blanks. Within the DATA_SET_ID, elements are separated by hyphens. Multiple instrument hosts, instruments or targets are referenced in the DATA_SET_NAME or DATA_SET_ID by concatenation of the values with a forward slash, "/", which is interpreted as "and." Data processing level number The data processing level number is the National Research Council (NRC) Committee on Data Management and Computation (CODMAC) data processing level number Level Type Data Processing Level Description 1 Raw Data Telemetry data with data embedded 2 Edited Data Corrected for telemetry errors and split or de-commutated into a data set for a given instrument. Sometimes called Experimental Data Record (EDR). 3 Calibrated Data Edited data that are still in units produced by instrument, but that have been corrected so that values are expressed in or are proportional to some physical unit such as radiance. No resampling, so edited data can be reconstructed. 4 Resampled Data Data that have been resampled in the time or space domains in such a way that the original edited data cannot be reconstructed. Could be calibrated in addition to being resampled. 5 Derived Data Derived results, as maps, reports, graphics, etc. 6 Ancillary Data Nonscience data needed to generate calibrated or resampled data sets. Consists of instrument gains, offsets, pointing information for scan platforms, etc. 7 Correlative Data Other science data needed to interpret space-based data sets. 8 User Description Description of why the data were required, any peculiarities associated with the data sets, and enough documentation to allow secondary user to extract information from the data. Mission phase abreviation (optional) Data set type is the concatenation of the data type and of the PRODUCT_TYPE keyword (e.g. EDR, RDR) provided in each PDS data product labels. Description (optional) The CODMAC level for some of the datasets is the same, and this means the end user has no way of knowing which dataset he is looking at from the data processing level number alone. Therefore, in order to help the end user, the STANDARD_DATA_PRODUCT_ID keyword has been added to all of SPICAV data product labels and the value of this keyword is given in the Description component of the DATA_SET_ID. The value must be no more that 4 characters long. The STANDARD_DATA_PRODUCT_ID for SOIR is “SOIR” For the different SOIR levels the corresponding CODMAC level and PRODUCT_TYPE are given in Figure 9 SOIR LEVEL CONTENTS PSA LEVEL CODMAC PRODUCT TYPE 0.1B raw data 1B 2 EDR – Experiment Data Record 1.0 calibrated data 2 3 RDR – Reduced Data Record 2.0 science data 3 5 DDR –Derived Data Record Figure 9 Correspondence between SOIR, PSA and CODMAC levels For a data set containing the first version of SOIR data collected from the SPICAV instrument on Venus Express during the cruise and Venus nominal phases The DATA_SET_NAME for SOIR would be * VENUS EXPRESS SKY/VENUS SPICAV 2 SOIR V1.0 for PSA level 1B data * VENUS EXPRESS SKY/VENUS SPICAV 3 SOIR V1.0 for PSA level 2 data The DATA_SET_ID for SOIR would be * VEX-Y/V-SPICAV-2-SOIR-V1.0 for PSA level 1B data * VEX-Y/V-SPICAV-3-SOIR-V1.0 for PSA level 2 data 3.1.3. Data Directory Naming Convention In the DATA directory, data are stored in subdirectories For PSA level 1B Subdirectories correspond to observation periods during cruise phase (e.g. pointing test) or medium term planning observation phases (MTP). ../VEXSPI_1003_1B/DATA/YYYYMMDD_ IND/(files) with IND=keyword indicating the observation period. ind can have the following values * CO1, CO2 (check out 1 resp 2) * PO1, PO2 (pointing test 1 resp 2) * IFT_1, IFT_2, IFT_3, IFT_4 (interference test 1 thru 4) * VCO (Venus commissioning) * Mxx (MTP xx period). For PSA level 2 Subdirectories correspond to individual observations, i.e. one subdirectory per observation day in orbit around Venus. ../VEXSPI_2003_2/DATA/YYYYMMDD_Maa_tbb/(files) with YYYY=year, MM=month, DD=day, aa=mtp number, t=occultation type (O for a single observation (L for sunrise, C for sunset, O for nadir, or calibration), C for a sunset that was part of a sunrise+sunset combination, L for a sunrise that was part of a sunrise+sunset combination), bb=occultation number in current mtp. One exception : the occultation taken during Venus Commissioning ../VEXSPI_2003_2/DATA/YYYYMMDD_VCO_O01/(files) 3.1.4. Filenaming Convention For PSA level 1B Data product files provided at PSA level 1B are ../YYYYMMDD_IND_OBS.TAB (science data) ../YYYYMMDD_IND_TC1.TAB (telecommand type 1) ../YYYYMMDD_IND_TC2.TAB (telecommand type 2) with IND=keyword indicating the observation period (see above). For PSA level 2 Data product files provided at PSA level 2 are ../YYYYMMDD_Maa_tbb_xxx.TAB (science data) ../YYYYMMDD_Maa_tbb_Rxxx.TAB (regression coefficients of full sun spectrum) ../YYYYMMDD_Maa_tbb_xxx.TAB (science data) ../YYYYMMDD_Maa_tbb_TC2.TAB (telecommand type 2) ../YYYYMMDD_Maa_tbb_TRT.TAB (treatment) with YYYY=year, MM=month, DD=day, aa=mtp number, t=occultation type (L for sunrise, C for sunset, O for nadir or calibrationO for a single observation (sunrise, sunset, nadir, calibration), C for a sunset that was part of a sunrise+sunset combination, L for a sunrise that was part of a sunrise+sunset combination), bb=occultation number in current mtp, xxx=order number. Associated detached label files follow the same filenaming convention with the .LBL extension. APPENDIX 1: Content of directories Archive Directory ../VEXSPI_1003_1B ../VEXSPI_2003_2 ../VEXSPI_3003_3 Root Directory ../CATALOG ../DATA ../DOCUMENT ../INDEX ../BROWSE ../EXTRAS (only on PSA level 2) AAREADME.TXT VOLDESC.CAT Catalog Directory CATINFO.TXT DATASET.CAT INST.CAT INSTHOST.CAT MISSION.CAT REFERENCE.CAT SOFTWARE.CAT RELEASE.CAT Index Directory INDXINFO.TXT INDEX.TAB INDEX.LBL BROWSE.TAB BROWSE.LBL GEO_VENUS.TAB GEO_VENUS.LBL Data Directory For PSA level 1B /20051125_CO1 /... /20051127_PO1 /... /20051128_PO1 /... /20051129_PO1 /... /20051214_IFT_1 /... /20051214_IFT_2 /... /20051214_IFT_3 /... /20051214_IFT_4 /... /20060116_PO2 /... /20060117_PO2 /... /20060118_PO2 /... /20060221_CO2 /... /20060509_VCO /... /20060510_VCO /... /20060512_VCO /... /20060526_M01 /... /20060527_M01 /... /20060530_M01 /... /20060805_M04 /... /20060807_M04 /... /20060809_M04 /20060809_M04_OBS.LBL /20060809_M04_OBS.TAB /20060809_M04_TC1.LBL /20060809_M04_TC1.TAB /20060809_M04_TC2.LBL /20060809_M04_TC2.TAB /20060810_M04 /... /20060812_M04 /... /20060813_M04 /... /20060815_M04 /... /20060817_M04 /... /20060820_M04 /... /20060823_M04 /... /20060828_M05 /... /... /20060913_M05 /... /... For PSA level 2 /20060512_VCO_O01 /... /20060526_M01_O01C01 /... /20060527_M01_CO02 /... /20060530_M01_CO03 /... /20060805_M04_O01 /... /20060807_M04_CO02 /... /20060809_M04_CO03 /20060809_M04_CO03_120.LBL /20060809_M04_CO03_120.TAB /20060809_M04_CO03_121.LBL /20060809_M04_CO03_121.TAB /20060809_M04_CO03_122.LBL /20060809_M04_CO03_122.TAB /20060809_M04_CO03_123.LBL /20060809_M04_CO03_123.TAB /20060809_M04_C03_R120.LBL /20060809_M04_C03_R120.TAB /20060809_M04_C03_R121.LBL /20060809_M04_C03_R121.TAB /20060809_M04_C03_R122.LBL /20060809_M04_C03_R122.TAB /20060809_M04_C03_R123.LBL /20060809_M04_C03_R123.TAB /20060809_M04_TC2.LBL /20060809_M04_TC2.TAB /20060809_M04_TRT.LBL /20060809_M04_TRT.TAB /20060810_M04_LO04 /... /20060812_M04_CO05 /... /20060813_M04_LO06 /... /20060815_M04_CO07 /... /20060817_M04_LO08 /... /20060820_M04_LO09 /... /20060823_M04_LO10 /... /20060828_M05_LO01 /... /... /20060913_M05_CO14 /... /... Browse Directory For PSA level 1B /20060512_VCO_O01 /... /20060526_M01_O01 /... /20060527_M01_O02 /... /20060530_M01_O03 /... /20060805_M04_O01 /... /20060807_M04_O02 /... /20060809_M04_O03 /20060809_M04_O03_INT.JPG /20060809_M04_O03_INT.LBL /20060810_M04_O04 /... /20060812_M04_O05 /... /20060813_M04_O06 /... /20060815_M04_O07 /... /20060817_M04_O08 /... /20060820_M04_O09 /... /20060823_M04_O10 /... /20060828_M05_O01 /... /... /20060913_M05_O14 /... /... For PSA level 2 /20060512_VCO_O01 /... /20060526_M01_O01 /... /20060527_M01_O02 /... /20060530_M01_O03 /... /20060805_M04_O01 /... /20060807_M04_O02 /... /20060809_M04_O03 /20060809_M04_O03_120.LBL /20060809_M04_O03_120.JPG /20060809_M04_O03_121.LBL /20060809_M04_O03_121.JPG /20060809_M04_O03_122.LBL /20060809_M04_O03_122.JPG /20060809_M04_O03_123.LBL /20060809_M04_O03_123.JPG /20060809_M04_O03_INT.JPG /20060809_M04_O03_INT.LBL /20060810_M04_O04 /... /20060812_M04_O05 /... /20060813_M04_O06 /... /20060815_M04_O07 /... /20060817_M04_O08 /... /20060820_M04_O09 /... /20060823_M04_O10 /... /20060828_M05_O01 /... /... /20060913_M05_O14 /... /... Extras Directory Only for PSA level 2 /20060512_VCO_O01 /... /20060526_M01_O01 /... /20060527_M01_O02 /... /20060530_M01_O03 /... /20060805_M04_O01 /... /20060807_M04_O02 /... /20060809_M04_O03 /20060809_M04_O03_120_ANIM.LBL /20060809_M04_O03_120_ANIM.GIF /20060809_M04_O03_121_ANIM.LBL /20060809_M04_O03_121_ANIM.GIF /20060809_M04_O03_122_ANIM.LBL /20060809_M04_O03_122_ANIM.GIF /20060809_M04_O03_123_ANIM.LBL /20060809_M04_O03_123_ANIM.GIF /20060810_M04_O04 /... /20060812_M04_O05 /... /20060813_M04_O06 /... /20060815_M04_O07 /... /20060817_M04_O08 /... /20060820_M04_O09 /... /20060823_M04_O10 /... /20060828_M05_O01 /... /... /20060913_M05_O14 /... /... Geometry Directory Not used for SOIR Software Directory Not used for SOIR Calibration Directory Not used for SOIR Label Directory There is no label directory. All PDS detached label files describing data or document files in a volume are in the corresponding data directory. Document Directory DOCINFO.TXT EAICD.DOC EAICD.TXT EAICD.PDF EAICD.LBL FLIGHT_USER_MANUAL.TXT FLIGHT_USER_MANUAL.LBL INSTRUMENT_CALIBRATION_PAPER.DOC INSTRUMENT_CALIBRATION_PAPER.LBL TMTC.DOC TMTC.LBL INSTRUMENT_PAPER.DOC INSTRUMENT_PAPER.LBL INSTRUMENT_DESC.TXT INSTRUMENT_DESC.LBL INSTRUMENT_MODE_DESC.LBL INSTRUMENT_MODE_DESC.TXT OBSERVATION_TYPE_DESC.LBL OBSERVATION_TYPE_DESC.TXT SOIR_DATAFILE_DESC.LBL SOIR_DATAFILE_DESC.TXT SOIR_CALIBRATION_DESC.LBL SOIR_CALIBRATION_DESC.TXT VEX_ORIENTATION_DESC.LBL VEX_ORIENTATION_DESC.TXT VEX_POINTING_MODE_DESC.LBL VEX_POINTING_MODE_DESC.TXT VEX_SCIENCE_CASE_ID_DESC.LBL VEX_SCIENCE_CASE_ID_DESC.TXT SOIR_DATA_QUALITY_DESC.LBL SOIR_DATA_QUALITY_DESC.TXT SOIR_CALIBRATION_SOFTWARE.LBL SOIR_CALIBRATION_SOFTWARE.TXT VEX_ORIENTATION_DESC.TXT VEX_ORIENTATION_DESC.LBL VEX_POINTING_MODE_DESC.TXT VEX_POINTING_MODE_DESC.LBL VEX_SCIENCE_CASE_ID_DESC.TXT VEX_ SCIENCE_CASE_ID_DESC.LBL APPENDIX 2: Data Product Design This appendix contains example labels for each of the SOIR data product, both for PSA level 1B and level 2. Data product design - PSA level 1B Data file A SOIR data product file at PSA level 1B contains the data of one observation, i.e. the data gathered between a switch ON and a switch OFF of the instrument. This can be an occultation (standard case) but also a calibration or other technological measurement. It covers both the precooling and the effective observation phase. Each file is an ASCII table, containing 11 thematic columns C and 2581 basic columns c and a variable number of rows, equal to the number of seconds in the observation (precooling + effective observation). For a 10 minutes precooling + a 15 minutes observation period there will be 1500 seconds, hence 1500 rows in the file. Each row contains 28462 bytes. Hence, for a 1500 seconds observation the file size will be approximately 43 Mbytes (42.693.000 bytes) C1 time C2 phase C3 bin0 … C10 bin7 C11 housekeeping T1 … T4 I1 … I320 I1 … I320 H1 … H16 c1 c4 c5 c6 c325 c2246 c2565 c2566 c2581 Ci (i=1 to 11) are 11 columns * C1 = c1 … c4 : 4 x 23 bytes, type character * C2 = c5 : 2 bytes, type character * C3 to C10 = c6 … c2565 : 8 x 320 x 10 bytes, type ASCII_integer * C11 = c2566 … c2581 : 16 x 11 bytes, type ASCII_real The data table (OBJECT=SOIR_TABLE) is composed of a set of 11 COLUMN objects (TIME, PHASE, BIN_0, BIN_1, BIN_2, BIN_3, BIN_4, BIN_5, BIN_6, BIN_7, HOUSEKEEPING). Each column consists of a certain number of ITEMS (sub-columns of the main column). The sub-columns are separated by comma’s and each line is terminated by a combination. The object SOIR_TABLE is described in a detached label in the following way OBJECT = SOIR_TABLE COLUMNS = 2581 INTERCHANGE_FORMAT = ASCII ROW_BYTES = 28462 ROWS = 1191 /* column contents : time of measurement */ OBJECT = COLUMN NAME = TIME BYTES = 103 DATA_TYPE = CHARACTER START_BYTE = 2 ITEMS = 4 ITEM_OFFSET = 26 ITEM_BYTES = 23 END_OBJECT = COLUMN /* column contents : precooling or observation phase */ OBJECT = COLUMN NAME = PHASE BYTES = 2 DATA_TYPE = CHARACTER UNIT = “N/A” START_BYTE = 106 END_OBJECT = COLUMN /* following 8 columns are bins of observation */ /* column contents : first bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_0 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 110 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : second bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_1 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 3630 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : third bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_2 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 7150 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : fourth bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_3 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 10670 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : fifth bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_4 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 14190 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : sixth bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_5 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 17710 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : seventh bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_6 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 21230 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* column contents : eighth bin of the observation – nr of rows in bin depends on configuration in telecommand */ OBJECT = COLUMN NAME = BIN_7 BYTES = 3519 DATA_TYPE = ASCII_INTEGER START_BYTE = 24750 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* following 16 columns are housekeeping values */ /* FPAT 2 : temperature measurement on focal plane array in detector */ OBJECT = COLUMN NAME = "FPAT_2" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28270 UNIT = "N/A" END_OBJECT = COLUMN /* SOFC : temperature measurement at socket of AOTF */ OBJECT = COLUMN NAME = "SOFC" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28282 UNIT = DEGREE END_OBJECT = COLUMN /* BPL_1 : first temperature measurement at baseplate */ OBJECT = COLUMN NAME = "BPL_1" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28294 UNIT = DEGREE END_OBJECT = COLUMN /* BPL_2 : second temperature measurement at baseplate */ OBJECT = COLUMN NAME = "BPL_2" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28306 UNIT = DEGREE END_OBJECT = COLUMN /* AOTF_T : temperature measurement inside AOTF box */ OBJECT = COLUMN NAME = "AOTF_T" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28318 UNIT = DEGREE END_OBJECT = COLUMN /* RF_AMP : amplitude of RF signal that drives AOTF */ OBJECT = COLUMN NAME = "RF_AMP" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28330 UNIT = "N/A" END_OBJECT = COLUMN /* MOT_C : DAC value used for the control of the cooler motor */ OBJECT = COLUMN NAME = "MOT_CT" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28342 UNIT = "N/A" END_OBJECT = COLUMN /* +12_V : measurement of +12 V power supply */ OBJECT = COLUMN NAME = "+12_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28354 UNIT = VOLT END_OBJECT = COLUMN /* -12_V : measurement of -12 V power supply */ OBJECT = COLUMN NAME = "-12_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28366 UNIT = VOLT END_OBJECT = COLUMN /* +8.5_V : measurement of +8.5 V power supply */ OBJECT = COLUMN NAME = "+8.5_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28378 UNIT = VOLT END_OBJECT = COLUMN /* -8.5_V : measurement of -8.5 V power supply */ OBJECT = COLUMN NAME = "-8.5_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28390 UNIT = VOLT END_OBJECT = COLUMN /* +3.3_V : measurement of +3.3 V power supply */ OBJECT = COLUMN NAME = "+3.3_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28402 UNIT = VOLT END_OBJECT = COLUMN /* +2.5_V : measurement of +2.5 V power supply */ OBJECT = COLUMN NAME = "+2.5_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28414 UNIT = VOLT END_OBJECT = COLUMN /* +5_V : measurement of +5 V power supply */ OBJECT = COLUMN NAME = "+5_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28426 UNIT = VOLT END_OBJECT = COLUMN /* -5_V : measurement of -5 V power supply */ OBJECT = COLUMN NAME = "-5_V" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28438 UNIT = VOLT END_OBJECT = COLUMN /* FPAT : temperature measurement on focal plane array in detector used for closed loop feedback */ OBJECT = COLUMN NAME = "FPAT" BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 28450 UNIT = KELVIN END_OBJECT = COLUMN END_OBJECT = SOIR_TABLE Associated files At the PSA level 1B each data set contains, besides the main data table file, two associated table files for the telecommands of type 1 and type 2 issued during this observation. The table for TC1 contains 10 rows, the table for TC2 31 rows. Each row is 19 bytes long, hence a TC1 table file is 190 bytes long, a TC2 table file is 589 bytes long. C1 telecommand parameter name C2 telecommand parameter value * C1 = 1 x 8 bytes, type character * C2 = 1 x 8 bytes, type ASCII_integer The two files each contain a small table object, namely OBJECT=TC1_TABLE and OBJECT=TC2_TABLE, both consisting of two COLUMN objects (TC_NAMES and TC_VALUES). OBJECT = TC1_TABLE INTERCHANGE_FORMAT = ASCII ROWS = 10 ROW_BYTES = 19 COLUMNS = 2 OBJECT = COLUMN NAME = TC_NAMES DATA_TYPE = CHARACTER START_BYTE = 1 BYTES = 8 END_OBJECT = COLUMN OBJECT = COLUMN NAME = TC_VALUES DATA_TYPE = ASCII_INTEGER START_BYTE = 10 BYTES = 8 END_OBJECT = COLUMN END_OBJECT = TC1_TABLE and OBJECT = TC2_TABLE INTERCHANGE_FORMAT = ASCII ROWS = 31 ROW_BYTES = 19 COLUMNS = 2 OBJECT = COLUMN NAME = TC_NAMES DATA_TYPE = CHARACTER START_BYTE = 1 BYTES = 8 END_OBJECT = COLUMN OBJECT = COLUMN NAME = TC_VALUES DATA_TYPE = ASCII_INTEGER START_BYTE = 10 BYTES = 8 END_OBJECT = COLUMN END_OBJECT = TC2_TABLE Besides the object definition of the respective tables the label files contain headers that describe a number of supplementary parameters documenting the observation. Below an example. PDS_VERSION_ID = PDS3 /* DESIGN */ /* per observation 1 data file + 1 telecommand file type_1 + 1 telecommand file type_2 */ /* 3 label files to accompany the 3 data files */ /* FILE RELATED INFORMATION*/ PRODUCT_ID = "20060828_M05_O01_OBS.TAB" FILE_NAME = "20060828_M05_O01_OBS.TAB" ^SOIR_TABLE = "20060828_M05_O01_OBS.TAB" RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 33898242 FILE_RECORDS = 1 /* PRODUCER IDENTIFICATION */ PRODUCER_ID = VEX_SPICAV_SOIR PRODUCER_FULL_NAME = "BERTAUX/NEEFS" PRODUCER_INSTITUTION_NAME = "SERVICE D'AERONOMIE/BELGIAN INSTITUTE FOR SPACE AERONOMY" PRODUCT_CREATION_TIME = 2008-04-28T08:45:09 /* DATA DESCRIPTION AND IDENTIFICATION */ DATA_SET_ID = "VEX-Y/V-SPICAV-2-SOIR-V1.0" DATA_SET_NAME = "VENUS EXPRESS SKY/VENUS SPICAV 2 SOIR V1.0" RELEASE_ID = 0001 REVISION_ID = 0000 PRODUCT_TYPE = EDR PROCESSING_LEVEL_ID = 2 MISSION_NAME = "VENUS EXPRESS" MISSION_ID = VEX INSTRUMENT_HOST_NAME = "VENUS EXPRESS" INSTRUMENT_HOST_ID = VEX MISSION_PHASE_NAME = "PHASE 0" INSTRUMENT_NAME = "SPICAV SOLAR OCCULTATION IN THE INFRARED" INSTRUMENT_ID = SPICAV INSTRUMENT_TYPE = SPECTROMETER ^INSTRUMENT_DESC = "INSTRUMENT_DESC.TXT" /* TARGET IDENTIFICATION */ TARGET_TYPE = SUN TARGET_NAME = SUN RIGHT_ASCENSION = “N/A” DECLINATION = “N/A” /* SCIENCE OPERATIONS INFORMATION */ VEX:SCIENCE_CASE_ID = 6 VEX:SCIENCE_CASE_ID_DESC = "See document VEX_SCIENCE_CASE_ID_DESC.TXT in DOCUMENT directory" OBSERVATION_TYPE = AC001A ^OBSERVATION_TYPE_DESC = "OBSERVATION_TYPE_DESC.TXT" /* TIME RELATED INFORMATION */ START_TIME = 2006-08-28T02:37:33 STOP_TIME = 2006-08-28T02:57:26 SPACECRAFT_CLOCK_START_COUNT = "1/0047097453.57585" SPACECRAFT_CLOCK_STOP_COUNT = "1/0047098646.50066" /* ORBITAL INFORMATION */ ORBIT_NUMBER = 129 ORBITAL_ECCENTRICITY = “N/A” ORBITAL_INCLINATION = “N/A” ORBITAL_SEMIMAJOR_AXIS = “N/A” PERIAPSIS_ALTITUDE = “N/A” PERIAPSIS_ARGUMENT_ANGLE = “N/A” PERIAPSIS_TIME = “N/A” SPACECRAFT_ORIENTATION = “N/A” ^SPACECRAFT_ORIENTATION_DESC = "VEX_ORIENTATION_DESC.TXT" SPACECRAFT_POINTING_MODE = INERT SPACECRAFT_POINTING_MODE_DESC = "See document VEX_POINTING_MODE_DESC.TXT in DOCUMENT directory" /* GEOMETRICAL INFORMATION */ SPACECRAFT_ALTITUDE = “N/A” SPACECRAFT_SOLAR_DISTANCE = “N/A” SUB_SPACECRAFT_LATITUDE = “N/A” SUB_SPACECRAFT_LONGITUDE = “N/A” SLANT_DISTANCE = “N/A” VEX: OCCULTATION_ENTRY_TIME = 2006-08-28T02:05:50 VEX: OCCULTATION_EXIT_TIME = 2006-08-28T02:52:29 /* QUALITY IDENTIFICATION */ DATA_QUALITY_ID = 0001111 DATA_QUALITY_DESC = "See document SOIR_DATA_QUALITY_DESC.TXT in DOCUMENT directory" /* INSTRUMENT RELATED INFORMATION */ INSTRUMENT_MODE_ID = HOPPING ^INSTRUMENT_MODE_DESC = "INSTRUMENT_MODE_DESC.TXT" DETECTOR_ID = SOIR Data product design - PSA level 2 Data file A SOIR data product file at PSA level 2 contains the data of one order throughout a selected reduced part of the observation, containing the scientifically interesting part of the measurement, i.e. the zone around “the occultation”, the sunset or sunrise. Each file is an ASCII table, containing 7 thematic columns C and 1319 basic columns c and a variable number of rows, equal to the number of seconds selected as scientifically interesting occultation data. For a 1 minute occultation period there will be 60 rows in the file. Each row contains 12709 bytes. Hence, for a 60 seconds occultation the file size will be approximately 0.7 Mbytes (762540 bytes). C1 time C2 wavenumber bin 1 C3 wavenumber bin 2 C4 bin 1 C5 bin 2 C6 housekeeping C7 attitude W1 … W320 W1 … W320 I1 … I320 I1 … I320 H1 … H16 A1 … A22 c1 c2 c321 c322 c641 c642 c961 c962 c1291 c1292 c1307 c1308 c1319 C1 time C2 wavenumber C3 bin 1 C4 bin 2 C5 housekeeping C6 attitude W1 … W320 I1 … I320 I1 … I320 H1 … H16 A1 … A28 Table 6: PSA level 2 science data table – TAB-file format Ci (i=1 to 7) are 7 columns * C1 = c1 : 1 x 23 bytes, type character * C2 = c2 … c321 : 320 x 7 bytes, type ASCII_real * C3 = c322 … c641 : 320 x 7 bytes, type ASCII_real * C2 = c2 … c321 : 320 x 7 bytes, type ASCII_real * C43 = c642 … c961 : 320 x 10 bytes, type ASCII_real * C54 = c962 … c1291 : 320 x 10 bytes, type ASCII_real * C65 = c1292 … c1307 : 16 x 11 bytes, type ASCII_real * C76 = c1308 … c1319 : 22 x 14 bytes, type ASCII_real The data table (OBJECT=SOIR_TABLE) is composed of a set of 6 7 COLUMN objects (TIME, WAVENUMBER BIN 1, WAVENUMBER BIN 2, TRANSMITTANCE TOP SLITBIN 1, TRANSMITTANCE BOTTOM SLITBIN 2, HOUSEKEEPING, ATTITUDE). Each column consists of a certain number of ITEMS (sub-columns of the main column). The sub-columns are separated by comma’s and each line is terminated by a combination. The object SOIR_TABLE is described in a detached label in the following way OBJECT = SOIR_TABLE COLUMNS = 1313 INTERCHANGE_FORMAT = ASCII ROW_BYTES = 12619 ROWS = 112 /* column contents : time of measurement */ OBJECT = COLUMN NAME = TIME BYTES = 23 DATA_TYPE = CHARACTER START_BYTE = 2 END_OBJECT = COLUMN /* wavenumber corresponding to the spectrum in the top half of the slit */ OBJECT = COLUMN NAME = TOP WAVENUMBER BYTES = 2559 DATA_TYPE = ASCII_REAL START_BYTE = 27 UNIT = 1 PER CENTIMETER ITEMS = 320 ITEM_OFFSET = 8 ITEM_BYTES = 7 END_OBJECT = COLUMN /* wavenumber corresponding to the spectrum in the bottom half of the slit */ OBJECT = COLUMN NAME = BOTTOM WAVENUMBER BYTES = 2559 DATA_TYPE = ASCII_REAL START_BYTE = 2587 UNIT = 1 PER CENTIMETER ITEMS = 320 ITEM_OFFSET = 8 ITEM_BYTES = 7 END_OBJECT = COLUMN /* spectrum in the top half of the slit */ OBJECT = COLUMN NAME = TOP SLIT BYTES = 3519 DATA_TYPE = ASCII_REAL START_BYTE = 5147 ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* spectrum in the bottom half of the slit */ OBJECT = COLUMN NAME = BOTTOM SLIT BYTES = 3519 DATA_TYPE = ASCII_REAL START_BYTE = 8667 ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN /* following 16 columns are housekeeping values */ /* FPAT 2 : temperature measurement on focal plane array in detector */ OBJECT = COLUMN NAME = FPAT_2 BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12187 UNIT = "N/A" END_OBJECT = COLUMN /* SOFC : temperature measurement at socket of AOTF */ OBJECT = COLUMN NAME = SOFC BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12199 UNIT = DEGREE END_OBJECT = COLUMN /* BPL_1 : first temperature measurement at baseplate */ OBJECT = COLUMN NAME = BPL_1 BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12211 UNIT = DEGREE END_OBJECT = COLUMN /* BPL_2 : second temperature measurement at baseplate */ OBJECT = COLUMN NAME = BPL_2 BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12223 UNIT = DEGREE END_OBJECT = COLUMN /* AOTF_T : temperature measurement inside AOTF box */ OBJECT = COLUMN NAME = AOTF_T BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12235 UNIT = DEGREE END_OBJECT = COLUMN /* RF_AMP : amplitude of RF signal that drives AOTF */ OBJECT = COLUMN NAME = RF_AMP BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12247 UNIT = "N/A" END_OBJECT = COLUMN /* MOT_C : DAC value used for the control of the cooler motor */ OBJECT = COLUMN NAME = MOT_CT BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12259 UNIT = "N/A" END_OBJECT = COLUMN /* +12_V : measurement of +12 V power supply */ OBJECT = COLUMN NAME = +12_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12271 UNIT = VOLT END_OBJECT = COLUMN /* -12_V : measurement of -12 V power supply */ OBJECT = COLUMN NAME = -12_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12283 UNIT = VOLT END_OBJECT = COLUMN /* +8.5_V : measurement of +8.5 V power supply */ OBJECT = COLUMN NAME = +8.5_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12295 UNIT = VOLT END_OBJECT = COLUMN /* -8.5_V : measurement of -8.5 V power supply */ OBJECT = COLUMN NAME = -8.5_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12307 UNIT = VOLT END_OBJECT = COLUMN /* +3.3_V : measurement of +3.3 V power supply */ OBJECT = COLUMN NAME = +3.3_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12319 UNIT = VOLT END_OBJECT = COLUMN /* +2.5_V : measurement of +2.5 V power supply */ OBJECT = COLUMN NAME = +2.5_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12331 UNIT = VOLT END_OBJECT = COLUMN /* +5_V : measurement of +5 V power supply */ OBJECT = COLUMN NAME = +5_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12343 UNIT = VOLT END_OBJECT = COLUMN /* -5_V : measurement of -5 V power supply */ OBJECT = COLUMN NAME = -5_V BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12355 UNIT = VOLT END_OBJECT = COLUMN /* FPAT : temperature measurement on focal plane array in detector used for closed loop feedback */ OBJECT = COLUMN NAME = FPAT BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 12367 UNIT = KELVIN END_OBJECT = COLUMN /* following 22 geometry parameters */ /* TangH (GEO): Tangential Height of the Geometrical Line-of-sight of the Spacecraft to the sun */ OBJECT = COLUMN NAME = "TangH(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12379 UNIT = KM END_OBJECT = COLUMN /* TPointLong (GEO): Longitude of the Previous geometrical tangential point on the Venus surface */ OBJECT = COLUMN NAME = "TPointLong(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12394 UNIT = DEGREES END_OBJECT = COLUMN /* TPointLat (GEO): Latitude of the Previous geometrical tangential point on the Venus surface */ OBJECT = COLUMN NAME = "TPointLat(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12409 UNIT = DEGREES END_OBJECT = COLUMN /* Theta (GEO): see figure 10 below – use GEO values*/ Figure 10 Theta angle calculation OBJECT = COLUMN NAME = "Theta(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12424 UNIT = DEGREES END_OBJECT = COLUMN /* SubSatPointLong (GEO): Longitude of the closest point on the Venus surface to the Spacecraft */ OBJECT = COLUMN NAME = "SubSatPointLong(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12439 UNIT = DEGREES END_OBJECT = COLUMN /* SubSatPointLat (GEO): Latitude of the closest point on the Venus surface to the Spacecraft */ OBJECT = COLUMN NAME = "SubSatPointLat(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12454 UNIT = DEGREES END_OBJECT = COLUMN /* TangH (BORESIGHT): Tangential Height of the SOIR viewing direction */ OBJECT = COLUMN NAME = "TangH(BORESIGHT)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12469 UNIT = KM END_OBJECT = COLUMN /* TPointLong (BORESIGHT): Longitude of the Previous SOIR Bore sight tangential point on the Venus surface */ OBJECT = COLUMN NAME = "TPointLong(BORESIGHT)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12484 UNIT = DEGREES END_OBJECT = COLUMN /* TPointLat (BORESIGHT): Latitude of the Previous SOIR Bore sight tangential point on the Venus surface */ OBJECT = COLUMN NAME = "TPointLat(BORESIGHT)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12499 UNIT = DEGREES END_OBJECT = COLUMN /* Theta (BORESIGHT): see figure 10 above - use BORESIGHT values */ OBJECT = COLUMN NAME = "Theta(BORESIGHT)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12514 UNIT = DEGREES END_OBJECT = COLUMN /* Dist_VenusSurface_Vex : distance from S/C to surface of Venus - Venus radius = 6051.8km */ OBJECT = COLUMN NAME = "Dist_VenusSurface_Vex" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12529 UNIT = KM END_OBJECT = COLUMN /* Dist_VenusSurface_Sun : distance from Sun to Venus (center to center) */ OBJECT = COLUMN NAME = "Dist_VenusCenter_Sun" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12544 UNIT = KM END_OBJECT = COLUMN /* Angle_Slit_limb : angle between the SOIR slit direction and the limb, Calculation uses SOIR bore sight values. The angle has a (arbitrarily chosen) sign. */ OBJECT = COLUMN NAME = "Angle_Slit_Limb(BORESIGHT)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12559 UNIT = DEGREES END_OBJECT = COLUMN /* SlitHeight : length of the slit parallel to the Venus-surface-normal in the tangential point It is the full slit height (not half) */ OBJECT = COLUMN NAME = "SlitHeight" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12574 UNIT = UM END_OBJECT = COLUMN /* SlitH_Resolution : The resolution of the slit in the Venus atmosphere. Full height resolution (not half) */ OBJECT = COLUMN NAME = "SlitH_Resolution" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12589 UNIT = KM END_OBJECT = COLUMN /* TangH(UNDER) : Tangential Height of the bottom side of the sun(geometrical) */ OBJECT = COLUMN NAME = "TangH(UNDER)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12604 UNIT = KM END_OBJECT = COLUMN /* TangH(UPPER) : Tangential Height of the top side of the sun(geometrical) */ OBJECT = COLUMN NAME = "TangH(UPPER)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12619 UNIT = KM END_OBJECT = COLUMN /* TangH_ref(UNDER) : Tangential Height of the bottom side of the sun(geometrical) including atmospheric refraction */ OBJECT = COLUMN NAME = "TangH_Ref(UNDER)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12634 UNIT = KM END_OBJECT = COLUMN /* TangH_ref(UPPER) : Tangential Height of the top side of the sun(geometrical) including atmospheric refraction */ OBJECT = COLUMN NAME = "TangH_Ref(UPPER)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12649 UNIT = KM END_OBJECT = COLUMN /* TangH_ref(CENTER) : Tangential Height of the center of the sun(geometrical) including atmospheric refraction */ OBJECT = COLUMN NAME = "TangH_Ref(CENTER)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12664 UNIT = KM END_OBJECT = COLUMN /* LocalTrueSolarTime(GEO) : Local True Solar Time. This value provides a measure of the instantaneous apparent position of the sun at the point of interest. Local True Solar Time is defined as the angle between the extension of the vector from the Sun to the target body and the projection on the target body's orbital plane of a vector from the target body's planetocentric centre to the point of interest. This angle is measured in a counterclockwise direction when viewed from north of the ecliptic plane. */ OBJECT = COLUMN NAME = "LocalTrueSolarTime(GEO)" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12679 UNIT = DEGREES END_OBJECT = COLUMN /* LocalTrueSolarTime : this value provides a measure of the instantaneous apparent position of the sun at the point of interest. Local True Solar Time is defined as the angle between the extension of the vector from the Sun to the target body and the projection on the target body's orbital plane of a vector from the target body's planetocentric centre to the point of interest. This angle is measured in a counterclockwise direction when viewed from north of the ecliptic plane. For SOIR boresight. */ OBJECT = COLUMN NAME = "LocalTrueSolarTime" BYTES = 14 DATA_TYPE = ASCII_REAL START_BYTE = 12694 UNIT = DEGREES END_OBJECT = COLUMN END_OBJECT = SOIR_TABLE END OBJECT = SOIR_TABLE COLUMNS = 1002 INTERCHANGE_FORMAT = ASCII ROW_BYTES = 10155 ROWS = 50 OBJECT = COLUMN NAME = TIME BYTES = 23 DATA_TYPE = CHARACTER START_BYTE = 2 END_OBJECT = COLUMN OBJECT = COLUMN NAME = WAVENUMBER BYTES = 7 DATA_TYPE = ASCII_REAL START_BYTE = 27 UNIT = 1 PER CENTIMETER ITEMS = 320 END_OBJECT = COLUMN OBJECT = COLUMN NAME = TOP SLIT BYTES = 10 DATA_TYPE = ASCII_REAL START_BYTE = 2587 ITEMS = 320 END_OBJECT = COLUMN OBJECT = COLUMN NAME = BOTTOM SLIT BYTES = 10 DATA_TYPE = ASCII_REAL START_BYTE = 6107 ITEMS = 320 END_OBJECT = COLUMN OBJECT = COLUMN NAME = HOUSEKEEPING BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 9627 ITEMS = 16 NAME_SET = {FPAT_2, SOFC, BPL_1, BPL_2, AOTF_T, RF_AMP, MOT_CT, +12_V, -12_V, +8.5_V, -8.5_V, +3.3_V, +2.5_V, +5_V, -5_V, FPAT} UNIT_SET = {N/A, °C, °C, °C, °C, N/A, N/A, V, V, V, V, V, V, V, V, °K} END_OBJECT = COLUMN OBJECT = COLUMN NAME = ATTITUDE BYTES = 11 DATA_TYPE = ASCII_REAL START_BYTE = 9819 ITEMS = 28 NAME_SET = {LDIST_NO_REF, RDIST_NO_REF, DIST_NO_REF, LDIST_10, RDIST_10, DIST_10, LDIST_REF, RDIST_REF, DIST_REF, LDIST_10_REF, RDIST_10_REF, DIST_10_REF, DIST_VENUS_VEX, ANGLE_SLIT_LIMB, H_SLIT, H_RESOLUTION, RA_PLANET, DEC_PLANET, POINT_OFFSET_RA, POINT_OFFSET_DEC, BORE_RA, BORE_DEC, X_RA, X_DEC, BORE_RA_NO_CORR, BORE_DEC_NO_CORR, X_RA_NO_CORR, X_DEC_NO_CORR} UNIT_SET = {KM, KM, KM, KM, KM, KM, KM, KM, KM, KM, KM, KM, KM, DEGREES, MICRON, KM, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES, DEGREES} END_OBJECT = COLUMN END_OBJECT = SOIR_TABLE Associated files The additional data table contains the regression coefficient file of the full sun spectrum for this occultation. It has 641 columns with 7043 bytes per row. C1 bin number C2 ‘a’ coefficient of regression C3 ‘b’ coefficient of regression a1 … a320 b1 … b320 c2 … c321 c322 … c641 * C1 = c1 : 1 x 2 bytes, type ASCII_integer * C2 = c2 … c321 : 320 x 11 bytes, type ASCII_real * C3 = c322 … c641 : 320 x 11 bytes, type ASCII_real The columns of this table are described here after: OBJECT = REF_TABLE INTERCHANGE_FORMAT = ASCII ROWS = 2 ROW_BYTES = 7043 COLUMNS = 641 OBJECT = COLUMN NAME = BIN_IX START_BYTE = 1 BYTES = 1 DATA_TYPE = ASCII_INTEGER UNIT = “N/A” FORMAT = I1 END_OBJECT = COLUMN OBJECT = COLUMN NAME = LIN_REGR_A_COEFF BYTES = 3519 DATA_TYPE = ASCII_REAL START_BYTE = 3 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN OBJECT = COLUMN NAME = LIN_REGR_B_COEFF BYTES = 3519 DATA_TYPE = ASCII_REAL START_BYTE = 3523 UNIT = “N/A” ITEMS = 320 ITEM_OFFSET = 11 ITEM_BYTES = 10 END_OBJECT = COLUMN END_OBJECT = REF_TABLE END At the PSA level 2 each data set contains, besides the main data table file, two associated table files for the telecommands of type 2 and for the treatment (TRT) the data underwent before arrival at PSA level 2. The table for TC2 contains 31 rows. Each row is 19 bytes long, hence a TC2 table file is 589 bytes long. C1 telecommand parameter name C2 telecommand parameter value * C1 = 1 x 8 bytes, type character * C2 = 1 x 8 bytes, type ASCII_integer The file contains a small table object, namely OBJECT=TC2_TABLE, consisting of two COLUMN objects (TC_NAMES and TC_VALUES). OBJECT = TC2_TABLE INTERCHANGE_FORMAT = ASCII ROWS = 31 ROW_BYTES = 19 COLUMNS = 2 OBJECT = COLUMN NAME = TC_NAMES DATA_TYPE = CHARACTER START_BYTE = 1 BYTES = 8 END_OBJECT = COLUMN OBJECT = COLUMN NAME = TC_VALUES DATA_TYPE = ASCII_INTEGER START_BYTE = 10 BYTES = 8 END_OBJECT = COLUMN END_OBJECT = TC2_TABLE The table for TRT contains 6 rows. Each row is 83 bytes long, hence a TRT table file is 498 bytes long. C1 treatment action name C2 treatment action value * C1 = 1 x 40 bytes, type character * C2 = 1 x 25 bytes, type character The file contains a small table object, namely OBJECT=TR_TABLE, consisting of two COLUMN objects (TR_NAMES and TR_VALUES). OBJECT = TR_TABLE INTERCHANGE_FORMAT = ASCII ROWS = 6 ROW_BYTES = 83 COLUMNS = 2 OBJECT = COLUMN NAME = TR_NAMES DATA_TYPE = CHARACTER START_BYTE = 1 BYTES = 40 END_OBJECT = COLUMN OBJECT = COLUMN NAME = TR_VALUES DATA_TYPE = CHARACTER START_BYTE = 42 BYTES = 40 END_OBJECT = COLUMN END_OBJECT = TR_TABLE Besides the object definition of the respective tables the label files contain headers that describe a number of supplementary parameters documenting the observation. PDS_VERSION_ID = PDS3 /* DESIGN*/ /* per order 1 data file */ /* per observation 4 orders (= 4 data files) + 1 telecommand file + 1 treatment file + 4 reference spectrum file */ /* 10 label files to accompany the 10 data files */ /* FILE RELATED INFORMATION*/ PRODUCT_ID = "20061128_M08_O05_169.TAB" FILE_NAME = "20061128_M08_O05_169.TAB" ^SOIR_TABLE = "20061128_M08_O05_169.TAB" RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 507750 FILE_RECORDS = 1 /* PRODUCER IDENTIFICATION */ PRODUCER_ID = VEX_SPICAV_SOIR PRODUCER_FULL_NAME = "BERTAUX/NEEFS" PRODUCER_INSTITUTION_NAME = "SERVICE D'AERONOMIE/BELGIAN INSTITUTE FOR SPACE AERONOMY" PRODUCT_CREATION_TIME = 2006-11-29T13:00:48 /* DATA DESCRIPTION AND IDENTIFICATION */ DATA_SET_ID = "VEX-Y/V-SPICAV-3-SOIR-V1.0" DATA_SET_NAME = "VENUS EXPRESS SKY/VENUS SPICAV 3 SOIR V1.0" RELEASE_ID = 0001 REVISION_ID = 0000 PRODUCT_TYPE = RDR PROCESSING_LEVEL_ID = 3 MISSION_NAME = "VENUS EXPRESS" MISSION_ID = VEX INSTRUMENT_HOST_NAME = "VENUS EXPRESS" INSTRUMENT_HOST_ID = VEX MISSION_PHASE_NAME = "PHASE 4" INSTRUMENT_NAME = "SPICAV SOLAR OCCULTATION IN THE INFRARED" INSTRUMENT_ID = SPICAV INSTRUMENT_TYPE = SPECTROMETER ^INSTRUMENT_DESC = "INSTRUMENT_DESC.TXT" /* TARGET IDENTIFICATION */ TARGET_TYPE = SUN TARGET_NAME = SUN RIGHT_ASCENSION = “N/A” DECLINATION = “N/A” /* SCIENCE OPERATIONS INFORMATION */ VEX:SCIENCE_CASE_ID = 6 VEX:SCIENCE_CASE_ID_DESC = "See document VEX_SCIENCE_CASE_ID_DESC.TXT in DOCUMENT directory" OBSERVATION_TYPE = AC001A ^OBSERVATION_TYPE_DESC = "OBSERVATION_TYPE_DESC.TXT" /* TIME RELATED INFORMATION */ START_TIME = 2006-11-28T07:22:09 STOP_TIME = 2006-11-28T07:22:58 SPACECRAFT_CLOCK_START_COUNT = "1/0055063326.02280" SPACECRAFT_CLOCK_STOP_COUNT = "1/0055063375.02279" /* ORBITAL INFORMATION */ ORBIT_NUMBER = 221 ORBITAL_ECCENTRICITY = “N/A” ORBITAL_INCLINATION = “N/A” ORBITAL_SEMIMAJOR_AXIS = “N/A” PERIAPSIS_ALTITUDE = “N/A” PERIAPSIS_ARGUMENT_ANGLE = “N/A” PERIAPSIS_TIME = “N/A” SPACECRAFT_ORIENTATION = “N/A” ^SPACECRAFT_ORIENTATION_DESC = "VEX_ORIENTATION_DESC.TXT" SPACECRAFT_POINTING_MODE = INERT SPACECRAFT_POINTING_MODE_DESC = "See document VEX_POINTING_MODE_DESC.TXT in DOCUMENT directory" /* GEOMETRICAL INFORMATION */ SPACECRAFT_ALTITUDE = “N/A” SPACECRAFT_SOLAR_DISTANCE = “N/A” SUB_SPACECRAFT_LATITUDE = “N/A” SUB_SPACECRAFT_LONGITUDE = “N/A” SLANT_DISTANCE = “N/A” VEX: OCCULTATION_ENTRY_TIME (PENS) = 2006-11-28T06:53:55 VEX: OCCULTATION_EXIT_TIME (PENE) = 2006-11-28T07:22:22 /* QUALITY IDENTIFICATION */ DATA_QUALITY_ID = 1111111 DATA_QUALITY_DESC = "See document SOIR_DATA_QUALITY_DESC.TXT in DOCUMENT directory" /* INSTRUMENT RELATED INFORMATION */ INSTRUMENT_MODE_ID = HOPPING ^INSTRUMENT_MODE_DESC = "INSTRUMENT_MODE_DESC.TXT" DETECTOR_ID = SOIR APPENDIX 3: Label keywords descriptions PDS version information PDS_VERSION_ID: version number of the PDS standards document that is valid when a data product label is created. For labels adhering to the PDS Standards Reference, Version 3.6, the appropriate value is [PDS3]. File related information PRODUCT_ID: unique identifier assigned to a data product. Data file name is used Example PSA level 1B ["20060812_M04_O05_OBS.TAB"] Example PSA level 2 ["20060809_M04_O03_120.TAB"] FILE_NAME: name of the data file. E.g. [“20060809_M04_O03_OBS.TAB”]for PSA level 1B, [“20060526_M01_O01_165.TAB”] for PSA level 2. SOIR_TABLE: pointer to the table file containing the SPICAV data and described in the label file Example ["20060809_M04_O03_120.TAB"] RECORD_TYPE: record format of a file. For the SOIR ASCII data files the RECORD_TYPE is [FIXED_LENGTH]. RECORD_BYTES: number of bytes in a record = “number of rows in the record” times “row length”. For PSA level 1B observation files the number of rows equals the number of seconds in the observation (order of magnitude 1500), the row length is 28.462 bytes. For PSA level 2 observation files the number of rows equals the number of interesting observations (seconds) in the occultation (order of magnitude 60), the row length is 10.119 bytes. FILE_RECORDS: Number of records in a file. Always [1] for SOIR. Producer identification PRODUCER_ID: identity of the producer of this dataset [VEX_SPICAV_SOIR] PRODUCER_FULL_NAME: full name of the person responsible for the production of a data [“BERTAUX/NEEFS”] PRODUCER_INSTITUTION_NAME: institution associated with the production of a data set ["SERVICE D’AERONOMIE/BELGIAN INSTITUTE FOR SPACE AERONOMY"] PRODUCT_CREATION_TIME: time of creation of this data file on the ground (in UTC). Example for SOIR [2006-10-23T10:06:03] Data description and identification DATA_SET_ID: unique alphanumeric identifier of this dataset. For SOIR PSA level 1B [“VEX-Y/V-SPI-2-SOIR-V1.0“]. For SOIR PSA level 2 [“VEX-Y/V-SPI-3-SOIR-V1.0“]. The DATA_SET_ID is an abbreviation of the DATA_SET_NAME. DATA_SET_NAME: full name given to a data set or a data product. The data_set_name typically identifies the instrument that acquired the data, the target of that instrument, and the processing level of the data. For SOIR PSA level 1B “VENUS EXPRESS SKY/VENUS SPICAV 3 SOIR V1.0“]. For SOIR PSA level 1B [“VENUS EXPRESS SKY/VENUS SPICAV 3 SOIR V1.0“] RELEASE_ID: number of the release of this data set. E.g. 0001 REVISION_ID: number of the revision of this data set. E.g. 0000 PRODUCT_TYPE: type or category of a data product within a data set [EDR for PSA level 1B, RDR for PSA level 2] PROCESSING_LEVEL_ID: CODMAC level [2 for PSA level 1B, 3 for PSA level 2] MISSION_NAME: Name of the mission including the SPICAV instrument [“VENUS EXPRESS”] MISSION_ID: [VEX] INSTRUMENT_HOST_NAME: name of the host spacecraft for the SPICAV instrument [“VENUS EXPRESS”] INSTRUMENT_HOST_ID: abbreviated name of the host spacecraft [VEX] MISSION_PHASE_NAME: mission subphases during which the data were collected [“CRUISE”, “VOI”, “PHASE 0”, “PHASE 1”, …] INSTRUMENT_NAME: name of the instrument ["SPICAV SOLAR OCCULTATION IN THE INFRARED"] INSTRUMENT_ID: acronym which identifies the instrument [SPICAV-SOIR] INSTRUMENT_TYPE: type of the instrument [SPECTROMETER] INSTRUMENT_DESCRIPTOR: pointer to the instrument description text file [“INSTRUMENT_DESC.TXT”] Target identification TARGET_TYPE: observed target [SUN] TARGET_NAME: the name of the target observed in the data [SUN] RIGHT_ASCENSION: not used for SOIR DECLINATION: not used for SOIR Science operations information VEX: SCIENCE_CASE_ID: case number as used during operations planning. Solar occultations using SOIR [6] VEX: SCIENCE_CASE_ID_DESC: science case description text file [“see document SCIENCE_CASE_DESC.TXT in DOCUMENT directory”] OBSERVATION_TYPE: observation type number as used during science definition. For SOIR [AC001A] OBSERVATION_TYPE_DESCRIPTOR: pointer to the observation type description text file [“OBSERVATION_TYPE_DESC.TXT”] Time related information START_TIME: the time of data acquisition of the first record (in UTC) e.g. [2006-08-09T01:30:53] STOP_TIME: the time of data acquisition of the last record (in UTC) e.g. [2006-08-09T01:31:42] SPACECRAFT_CLOCK_START_COUNT: the value of the spacecraft clock at the beginning of data acquisition of the first record e.g. ["1/0045451851.49184"] SPACECRAFT_CLOCK_STOP_COUNT: the time on the spacecraft clock at the end of data acquisition of the last record e.g. ["1/0045451900.49183"] Orbital information ORBIT_NUMBER: spacecraft orbit during which this data were collected. Valid values are [“N/A”] during the CRUISE phase or the value of the orbit (e.g.[“103”]) during the VENUS phase. ORBITAL_ECCENTRICITY: not used for SOIR ORBITAL_INCLINATION: not used for SOIR ORBITAL_SEMIMAJOR_AXIS: not used for SOIR PERIAPSIS_ALTITUDE: not used for SOIR PERIAPSIS_ARGUMENT_ANGLE: not used for SOIR PERIAPSIS_TIME: not used for SOIR SPACECRAFT_ORIENTATION: orientation vector of the spacecraft. The definition of the vector and the standard values are given via the SPACECRAFT_ORIENTATION_DESC pointer SPACECRAFT_ORIENTATION_DESC: pointer to a file containing information about the spacecraft orientation ["VEX_ORIENTATION_DESC.TXT"] SPACECRAFT_POINTING_MODE: pointing mode of the spacecraft. The definition of the modes and the standard values are given via the SPACECRAFT_POINTING_MODE_DESC pointer [INERT] SPACECRAFT_POINTING_MODE_DESC: definition file of the different pointing modes of the spacecraft ["see document VEX_POINTING_MODE_DESC.TXT in DOCUMENT directory"] Geometrical information SPACECRAFT_ALTITUDE: not used for SOIR SPACECRAFT_SOLAR_DISTANCE: not used for SOIR SUB_SPACECRAFT_LATITUDE: not used for SOIR SUB_SPACECRAFT_LONGITUDE: not used for SOIR SLANT_DISTANCE: not used for SOIR VEX: OCCULTATION_ENTRY_TIME (PENS): time of penumbra start during sunset observation. Example [2006-08-09T01:31:10] VEX: OCCULTATION_EXIT_TIME (PENE): time of penumbra end during sunrise observation. Example [2006-08-09T01:57:23] Quality identification DATA_QUALITY_ID: binary code describing in 7 bits the quality of the data. Example [1110101] DATA_QUALITY_DESC: description file of the data quality of the SOIR instrument ["see document SOIR_DATA_QUALITY_DESC.TXT in DOCUMENT directory"] Instrument related information INSTRUMENT_MODE_ID: observation mode of the SOIR instrument (taken from telemetry). Examples [HOPPING], [PARAMETER_STEPPING], [WINDOW_STEPPING] INSTRUMENT_MODE_DESC: pointer to the instrument mode description file ["INSTRUMENT_MODE_DESC.TXT"] DETECTOR_ID: name of the instrument [SOIR] ?? ?? ?? ?? VENUS-EXPRESS VEX-BIRA-AR-02 SOIR issue date: 21/1/08 issue number 004 Page 1 of 67 Archive Interface Control Document E. Neefs / BIRA-IASB