PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = "V1.1" RECORD_TYPE = STREAM OBJECT = TEXT NOTE = "Rosetta GIADA data during Comet Escort 4 phase" PUBLICATION_DATE = 2016-11-01 END_OBJECT = TEXT END Rosetta GIADA data during Comet Escort 4 phase 1. Introduction The Comet Escort 4 Phase covers the period of time from the 21 October 2015 until the 12 January 2016. It started after Rosetta successfully completed the Comet Escort 3 Phase. The present DataSet collects the GIADA data of ESC4 phase. The data were retrieved from DDS by means of the PI Workstation located at Instituto di Astrofisica e Planetologia Spaziali in Rome. We used the MaGx Converter v. 3.0 software on GIADA IWS to covert the DDS data. GIADA in flight software configuration is 2.3 plus three additional patches (one more patch is used to update the context file). The data set organisation conforms to the Planetary Data System (PDS) Standards, Version 3.8, Jet Propulsion Laboratory (JPL) document JPL D-7669, according to the structure agreed with ESA and described in RO_GIA_IAPSUPA_IF_012_I1 (reported in DOCUMENTation dir). A general description of GIADA instrument is in RO_GIA_IAPSUPA_IF_012_I1. See also RO_GIA_IAPSUPA_RP_121_1 reported in DOCUMENTation dir) for evaluations on GIADA behaviour during this mission phase. 2. File Formats See Sections 3 and 4 of RO_GIA_IAPSUPA_IF_012_I1 (reported in DOCUMENTation dir). 3. Data Set Contents The files on this volume are organized in a directory tree as described in RO_GIA_IAPSUPA_IF_012_I1 (reported in DOCUMENTation dir). We recall here that GIADA is formed by 3 detection devices: GDS (Grain Detection System), IS (Impact Sensor) and MBS (Micro Balance Sensors), guided and controlled by ME (Main Electronics). We recall that GIADA may operate in four different operative modes. These modes can be selected autonomously by the S/C control system, as well as by means of ground TCs. Different operational modes correspond to different active subsystems, so allowing to measure different quantities, as it follows: Mode Name Active subsystems (nominal) Measured quantities SAFE ME None NORMAL ME, GDS, IS, 5 MBSs Dust flux and fluence Grain Scattering properties Momentum of single grains Velocity of grains Mass of single grains FLUX ME, 5 MBSs Dust flux and fluence COVER ME, Cover or Frangibolt None In each Mode different sensors may also be switched ON/OFF separately by proper TC. While scientific data are acquired in NORMAL or FLUX Modes only, Housekeeping data are acquired in all Modes. We recall that GIADA is a "dust event driven" experiment, so that no scientific data are collected until arrival to the comet. Therefore, during Rosetta Cruise Phase no scientific event is recorded. Actually, some "scientific events" are recorded by GDS and IS, but they are not real dust events and must be neglected. In-flight calibration and housekeeping data are collected and reported in the data set. They are relevant to follow the behaviour and health status of the GIADA experiment and must be used in comparison with data obtained during on ground and other in-flight tests (see other relevant data sets). Under the DATA sub-directory, different sub-sub-directories are present of four main classes. First class: directories containing actual scientific data related to dust monitoring. They are labelled with the acronym of the GIADA sub-system. GDS+IS, GDS and IS directories contain "scientific data" related to "single grain detections" by: GDS_IS (when a grain is detected by GDS and IS in sequence: this is the "nominal" detection of a grain by GIADA); GDS (when a grain is detected by GDS, but the grain momentum is too small to activate the detection by the IS or it does not reach at all the IS); IS (when a grain is detected by the IS, but it was not able, e.g. too small, to activate the optical detection by GDS). If no grain is detected by the relevant sub-system the corresponding directory is not present in the data set. MBS directory contains the periodic reading of each of the five microbalances. Second class: directories containing data acquired for periodic calibration of sub-systems. They are labelled with the acronym of the GIADA sub-system followed by _CAL. Third class: directories containing housekeeping (HK) and instrument status data for instrument health control and verification of behaviour in function of issued commanding sequences. HK_DATA contains HK data acquired periodically, independently on scientific operation of GIADA. These data guarantee a control of GIADA. It also contains a record of GIADA status in terms of operative parameters that are set at the switch on and can be modified by Telecommand during operation. HK_SCI contains HK data recorded contextually to acquisition of "scientific events". These data are useful, for example, to check behaviour of scientific signals with operative conditions (e.g. temperature) and instrument status (e.g.: laser illumination) at the time of event detection. Fourth class: MBS_HEAT contains data acquired when MBS's are heated (this operation is not automatic and is triggered by a suitable Telecommand). This procedure can be activated to try to remove deposited (mainly volatile) material from the sensors in case they should become saturated. Practically, the run of this process is also useful to analyse (periodically) the behaviour of the frequency vs. temperature for each MBS. Under each sub-sub-directory just described, the data are organised in a further lower level according to the date of acquisition and to the kind of test performed on GIADA. Data reported in CALIB sub-dir are of two classes: ENG_CAL: contains data (for Main and Red Interface) for polynomial laws to convert digital numbers (ADC counts) into engineering data with units. Both these data formats are reported in the different data files. Further details about the data content are reported in the *INFO.TXT files present in each sub-dir. 4.Data Quality At each GIADA switch ON, a careful data analysis is performed to validate data quality with respect to previous on-ground and in-flight switch-on. This check is based on comparison of GIADA housekeeping data and analysis of operation conditions. The quality of GIADA data is identified based on this analysis. The approach is different for data sets at CODMAC 2 or 3 levels and for housekeeping or scientific data. For data at CODMAC 2 level, the data quality convention is as shown below: ID => DESC => Comment 1 => GOOD => All HK and SCI data in the TAB file are good 3 => BAD => A large amount of spurious data is present in the TAB N/A=> N/A => The file contains reference information/data which are not HK or SCI data 5.Errata and Disclaimer A cumulative list of anomalies and errors is maintained in the file ERRATA.TXT at the root directory of this volume, if needed. Although considerable care has gone into making this volume, errors are both possible and likely. Users of the data are advised to exercise the same caution as they would when dealing with any other unknown data set. Reports of errors or difficulties would be appreciated. Please contact one of the persons listed herein. 5. Whom to Contact for Information For questions concerning this data volume, data products, documentation and GIADA in general: Alessandra Rotundi Universita' "Parthenope" Via del Fosso del Cavaliere 100, 00133 Roma (Italy)" Electronic mail address: giada@uniparthenope.it, rotundi@uniparthenope.it Vincenzo Della Corte INAF - INST. DI ASTROFISICA E PLANETOLOGIA SPAZIALI" Via del Fosso del Cavaliere 100, 00133 Roma (Italy)" Electronic mail address: vincenzo.dellacorte@iaps.inaf.it