ROSETTA-RPC-MAG
To Planetary Science Archive Interface Control Document
EAICD
RO-IGEP-TR0009
Issue 3.3
18 February 2010
______________________________
Prepared by: Ingo Richter, RPC-MAG TM
__________________________ Approved by: PI
Change Log
Date
Sections Changed
Reasons for Change
7.3.2005
EAICD V1.5 release
26.9.2005
EAICD V1.7 release
PDS LABEL changes,
SOFTWARE deleted
4.10.2005
RPCMAG_SW.CAT changed to
RPCMAG_SOFTWARE.CAT
RPC Conventions
13.10.2005
Data Structure adapted to RPC conventions
RPC Conventions
26.10.2005
1.8, 2.4.3, 2.44, 3.11, 3.13, 3.14, 3.2.2, 3.42, 3.4.3.1,3.4.3.3, 4.3.1.6
Changes due to comments listed in RO-EST-LI-3331_1.0
18.01.2006
4.3.x
Geoindex information in DATA LBL files updated
28.09.2006
Sections mentioned in RO-EST-LI-3362
Comments on the Internal ESA Review
18.10.2006
TOC,1.5,1.9,2,22,3.1,4.2,4.3
Implementation of CLK,CLL data and Quality flags
20.4.2007
1.5.1, 1.5.2, 1.6, 1.8, 2.2.2, 2.2.6, 3.2.3, 3.42,
4.3.1.3,4.3.1.6
2.1, 2.2.3.1, 3.1.3, 3.4.3.2
4.3.1.9
4.3.2 ? 4.3.15
RID related changes, Editorial
Changes due to Improvement of Calibration S/W
Chapter added for description of GEOMETRY Information
Changes of *LBL files due to new ESA Requirements after DAWG meeting
6.8.2007
Additional changes according to RID 45
5.9.2007
2.2.2
Exact explanation of time stamps
28.10.2009
EAICD Acronym included in Acronym List,
List extended with RPCMAG_INST.CAT
Acronyms
26.1.2010
3.2
*LBL files updated according to S/W changes related to Archive review in October 2009
LEVEL_H description update due to LAP disturbance correction
18.2.2010
3.3
Logbook Items added
TABLE OF CONTENTS
1 INTRODUCTION 5
1.1 PURPOSE AND SCOPE 5
1.2 ARCHIVING AUTHORITIES 5
1.3 CONTENTS 5
1.4 INTENDED READERSHIP 5
1.5 SCIENTIFIC OBJECTIVES 6
1.5.1 Overview 6
1.5.2 The Cometary Magnetic Field - A historical perspective 6
1.5.3 The Cometary Magnetic field 7
1.6 APPLICABLE DOCUMENTS 7
1.7 RELATIONSHIPS TO OTHER INTERFACES 8
1.8 ACRONYMS AND ABBREVIATIONS 8
1.9 CONTACT NAMES AND ADDRESSES 10
2 OVERVIEW OF INSTRUMENT DESIGN, DATA HANDLING PROCESS AND PRODUCT GENERATION 10
2.1 DATA HANDLING PROCESS 12
2.1.1 Data Processing from DDS to PDS 12
2.1.2 Conversion of ADC-Counts to Physical Values 15
2.2 OVERVIEW OF DATA PRODUCTS 18
2.2.1 Instrument Calibrations 18
2.2.2 In-Flight Data Products 18
2.2.3 Software 22
2.2.4 Documentation 24
2.2.5 Derived and other Data Products 24
2.2.6 Ancillary Data Usage 24
3 ARCHIVE FORMAT AND CONTENT 26
3.1 FORMAT AND CONVENTIONS 26
3.1.1 Deliveries and Archive Volume Format 26
3.1.2 Data Set ID Formation 26
3.1.3 Data Directory Naming Convention 28
3.1.4 Filenaming Convention 30
3.2 STANDARDS USED IN DATA PRODUCT GENERATION 32
3.2.1 PDS Standards 32
3.2.2 Time Standards 32
3.2.3 Reference Systems 33
3.2.4 Other Applicable Standards 34
3.3 DATA VALIDATION 34
3.4 CONTENT 37
3.4.1 Volume Set 37
3.4.2 Data Set 37
3.4.3 Directories 39
4 DETAILED INTERFACE SPECIFICATIONS 42
4.1 STRUCTURE AND ORGANIZATION OVERVIEW 42
4.2 DATA SETS, DEFINITION AND CONTENT 44
4.3 DATA PRODUCT DESIGN 46
4.3.1 General OVERVIEW 46
4.3.2 Data Product ?EDITED Magnetic field data? Design 49
4.3.3 Data Product ?EDITED Housekeeping data? Design 52
4.3.4 Data Product ?CALIBRATED LEVEL_A Housekeeping data? Design 57
4.3.5 Data Product ?CALIBRATED LEVEL_A Magnetic Field data? Design 60
4.3.6 Data Product ?CALIBRATED LEVEL_B Magnetic Field data? Design 65
4.3.7 Data Product ?CALIBRATED LEVEL_C Magnetic Field data? Design 69
4.3.8 Data Product ?RESAMPLED LEVEL_K Magnetic Field data? Design 73
4.3.9 Data Product ?RESAMPLED LEVEL_L Magnetic Field data? Design 78
4.3.10 Data Product ?RESAMPLED LEVEL_E Magnetic Field data? Design 82
4.3.11 Data Product ?RESAMPLED LEVEL_F Magnetic Field data? Design 86
4.3.12 Data Product ?RESAMPLED LEVEL_G Magnetic Field data? Design 90
4.3.13 Data Product ?RESAMPLED LEVEL_H Magnetic Field data? Design 95
4.3.14 Data Product ?RESAMPLED LEVEL_I Magnetic Field data? Design 100
4.3.15 Data Product ?DERIVED LEVEL_J Magnetic Field data? Design 100
5 APPENDIX: AVAILABLE SOFTWARE TO READ PDS FILES 106
6 APPENDIX: EXAMPLE OF DIRECTORY LISTING OF DATA SET X 106
1 Introduction
1.1 Purpose and Scope
The purpose of this EAICD (Experimenter to (Science) Archive Interface Control Document) is two fold. First it provides users of the RPC-MAG 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 your instrument team and your 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 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 RPC-MAG instrument on ROSETTA from the s/c until the insertion into the PSA for ESA. 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 further on.
The design of the data set structure and the data product is given. Examples of these are given in the appendix.
1.4 Intended Readership
The staff of the archiving authority (Planetary Science Archive, ESA, RSSD, design team) and any potential user of the RPC-MAG data.
1.5 Scientific Objectives
1.5.1 Overview
The ROSETTA orbiter magnetometer is part of the ROSETTA Plasma Consortium set of scientific instruments. The purpose of the magnetometer is the measurement of the interplanetary magnetic field close to different targets visited by the ROSETTA spacecraft.
Special points of interest are:
* Measurements of the interplanetary magnetic field during the flybys at planet Mars & Earth, the asteroids and in the environment of comet p/Churyumov Gerasimenko.
* Study of the structure and dynamics of the cometary-solar wind interaction region.
* Study of the generation and evolution of the cometary magnetic Cavity.
* Study of cometary tail evolution and structure.
1.5.2 The Cometary Magnetic Field - A historical perspective
In 1951 the German Astronomer Ludwig Biermann used the fact that cometary tails are always pointing away from the Sun to postulate the solar wind.
It was Hannes Alfv�n who suggested in 1957 that cometary tails are due to the draping of the interplanetary magnetic field around the cometary nucleus.
To explain this draping effect C.S. Wu and R.C. Davidson in 1972 studied the pick-up of cometary ions and the associated mass loading of the solar wind.
Associated strong plasma wave turbulence due to this mass loading was first detected by B.T. Tsurutani and E.J. Smith in 1986.
The magnetic field draping itself was first measured by F. M. Neubauer and co-workers using magnetic field measurements made onboard the GIOTTO spacecraft.
1.5.3 The Cometary Magnetic field
1.6 Applicable Documents
Planetary Data System Data Preparation Workbook, February 1, 1995, Version 3.1, JPL, D-7669, Part1
Planetary Data System Standards Reference, August 1, 2003, Version 3.6, JPL, D-7669, Part 2
ROSETTA, Archive Generation, Validation and Transfer Plan, January 10, 2006, RO-EST-PL-5011
RPC-MAG Knowledge Management, Power-Point Presentation and Video (RO-3DSE-MAG)
RO-RPC-UM, Rosetta Plasma Consortium: User�s Manual
RO-IGM-TR-0002, Fluxgate Magnetometer Calibration for Rosetta: Report on the FM and FS Calibration
RO-IGM-TR-0003, Fluxgate Magnetometer Calibration for Rosetta: Analysis of the FM Calibration
RO-IWF-TR-0001, Calibration Report, Sample Rate and Frequency Response - Analysis of ROSETTA RPCMAG
RO-
IGEP-TR-0007, DDS2PDS User Manual
RO-IGEP-TR-0016, RPC Archiving Guidelines
RO-IGEP-TR-0028, RPCMAG Step by step Calibration Procedure
1.7 Relationships to Other Interfaces
This EAICD describes the overall RPC-MAG archiving details. If there will be changes in the DDS2PDS Sotftware, this EAICD and the DDS2PDS User manual, RO-IGM-TR0007, will be affected. Changes of the EAICD will not have any feedback to other documents,as the EAICD is changed at the end of the chain, taking into account any other document update made before
1.8 Acronyms and Abbreviations
ADC: Analog-Digital-Converter
AQP: Acquisition Period
ASIC: Application Specific Integrated Circuit
B-FIELD: Magnetic Field
CG: 67P/Churyumov-Gerasimenko
CO-I: Co-Investigator
CuL: Kupferlackdraht, Enamelled copper wire
DDS: Data Distribution System
DPU: Digital Processing Unit
DS-1: NASA's Deepspace 1 Mission
EAICD: Experimenter to Archive Interface Control Document
EID-B: Experiment Interface Document , Part B
EMC: Electromagnetic Compatibility
ESA: European Space Agency
ESTEC: European Space Research and Technology Centre
FGM: Fluxgate-Magnetometer
FM: Flight Model
FMECA: Failure Mode Effects and Criticality Analysis
FPGA: Field programmable Gate Array
FCP: Flight Control Procedure
FS: Flight Spare Model
HK: Housekeeping data (Supply voltages, Ref. Voltages, Temperatures)
H/W: Hardware
IABG: Industrieanlagenbetriebsgesellschaft
IB: Inboard Sensor
ID: Identifier
I/F: Interface
IGEP: Institut fuer Geophysik und extraterrestrische Physik, TU-Braunschweig IWF: Institut fuer Weltraumforschung,Graz
LCL: Latching Current Limiter
LEXAN: Polycarbonate resin thermoplastic
MACOR: Machinable glas ceramic
MAG: Magnetometer
MIP: RPC Mutual Impedance Probe
NASA: National Aeronautics and Space Administration
OB: Outboard Sensor
OPAMP: Operational Amplifier
PCB: Printed Circuit Board
PDS: Planetary Data System
PERMALLOY: Nickel Iron magnetic alloy
PI: Principal Investigator
PIU: RPC Power Interface Unit
PSA: Planetary Science Archive
PT1000: Platinum Thermistor with 1000 Ohm nominal resistance
RAW: Data in units of ADC counts in instrument coordinates
ROKSY: ROSETTA Knowledge Management System
ROMAP: ROSETTA Lander Magnetometer
RPC: ROSETTA Plasma Consortium
RPCMAG: ROSETTA Orbiter Magnetometer
RPC-MAG: ROSETTA Orbiter Magnetometer
RPC-0: RPC Main Electronics Box
SADM: Solar Array Drive Mechanism
S/C: Spacecraft
SID: Science Mode Identifier
S/W: Software
SEU: Single Event Upset
SEL: Single Event Latch-up
TC: Telecommand
TM: Telemetry
TM: Technical Manager
TS: Time series
UV: Ultraviolet
us: microsecond
Wrt.: with respect to
1.9 Contact Names and Addresses
PI: Prof. Dr. Karl-Heinz Glassmeier, IGEP, Mendelssohnstr. 3 , 38106 Braunschweig, +49 531 391 5215 , kh.glassmeier@tu-bs.de
TM: Dr. Ingo Richter, IGEP, Mendelssohnstr. 3 , 38106 Braunschweig, +49 531 391 5223 , i.richter@tu-bs.de
Responsible for the RAW2ASCII S/W, which converts Raw TM files to ASCII files:
Hans Eichelberger, Space Research Institute (IWF), Austrian Academy of Sciences, Schmiedlstr. 6, 8042 Graz, +43 316 4120 557, hue@oeaw.ac.at
2 Overview of Instrument Design, Data Handling Process and Product Generation
The ROSETTA orbiter magnetometer is part of the ROSETTA Plasma Consortium set of scientific instruments. The purpose of the magnetometer is the measurement of the interplanetary magnetic field close to different targets visited by the ROSETTA spacecraft.
To measure the magnetic field a system of two ultra light triaxial fluxgate magnetometers (about 36 g each) is used, with the outboard (OB) sensor mounted close to the tip of the about 1.5 m long spacecraft boom pointing away from the comet nucleus and with the inboard (IB) sensor on the same boom about 15 cm closer to the spacecraft body. Two magnetometer sensors are required to minimise the influence of the rather complex spacecraft field on the actual measurements, and for redundancy purposes.
In order to meet the scientific requirements as discussed above the spacecraft magnetic DC-field requirement is about 25 nT at the outboard MAG sensor. To achieve this goal a magnetic cleanliness programme was planned, conducted by the experimenter team, supported by the ROSETTA project.
To further eliminate spacecraft fields and zero-offsets the so called multi-magnetometer technique will be applied in conjunction with statistical in-flight techniques. To increase time resolution 6 A/D converters (one for each of the six sensor channels) will be used synchronously. The A/D converters have a resolution of 20 bits each. MAG will be operated with a high temporal resolution of about 20 vectors/sec outboard and inboard. Transmission of number of vectors/sec respectively burst mode memory operation will be adopted to available data rate by averaging of vector rate inside the PIU-DPU.
The Orbiter Magnetometer RPCMAG can be characterized by the following features:
* Fluxgate-Magnetometer with a resolution of +/- 31 pT
* Measurement Range ; +/- 16384 nT
* 2 Sensors OB/IB
* 20 Bit ADC
* Measuring B-Field in 3 components with a maximum vector rate of 20 Hz.
* The Flux-Gate Magnetometer RPC-MAG performance parameters are in full accordance with the EID-B design goals
* The Outboard/ Inboard sampling rate can be inverted by command either for higher Inboard time resolution or in case of outboard failure.
* The sensors are fully calibrated also versus a wide temperature range.
* The temperature at Outboard and Inboard sensor is monitored in MAG housekeeping data.
* The instrument delivers time series of the 3 dimensional magnetic field vector.
Block diagram of the RPCMAG Intrument
2.1 Data Handling Process
The RPC-MAG data are provided by IGEP using the DDS2PDS S/W package.
2.1.1 Data Processing from DDS to PDS
Details can be found in the DDS2PDS User Manual RO-IGEP-TR0007.
* The overall data processing can be done mainly by the IDL S/W package DDS2PDS. This consists of several routines for different purposes:
o Copying TM raw data from our ftp-server to the local analysis PC
o Converting /Decoding these binary data to ASCII data. This is done by calling the MATLAB S/W RAW2ASCII from the IDL program.
o Reading Attitude and Orbit file (*.ROS) from the ftp server
o Calling the OASWLIB S/W to generate desired attitude and orbit vectors
o Generating PDS Files from these ASCII raw data (Routine: GEN_CAL_DATA)
o Generating Plots
o Elimination of Reaction wheel influence
o Elimination of LAP Disturbance
o Considering Lander heater current disturbance
o Setting Quality flags to CALIBRATED, RESAMPLED , and DERIVED data
o Generating log files
* Binary TM data can be just read and converted to ASCII by RAW2ASCII
Program Details:
* developed in MATLAB under Windows by Hans Eichelberger, IWF, GRAZ
* this S/W acts as I/F between the binary raw data transmitted by the DDS/EGSE/IC-FTP server and the scientific usable data.
* The program converts binary raw data into ASCII data and adds the necessary time information (UTC) for the subsequent scientific analysis. Bad vectors are marked.
All written ASCII files get a header starting with #
* It reads
Magnetic field raw data in all modes (SID1 - SID6)
Temperature data (IB/OB)
HK data
* The program can be executed via a batch job to guarantee a more or less automatic data generation/conversion process.
* The converted ASCII data will be merged with auxiliary data and processed with GEN_CAL_DATA to obtain scientific usable data in PDS format.
* This IDL routine acts as I/F between the ASCII raw data converted by RAW2ASCII and the PDS System.
* GEN_CAL_DATA reads ( files can be read from a list for automatic data generation)
� ���� Magnetic field ASCII raw data:
RPCMAGyymmddThhmm_RAW_<sensor>_<MODE>.ASS
Auxiliary data - Attitude: ATyyyymmdd.ROS
Auxiliary data - Position: POSyymmdd.ROS
Housekeeping data: RPCMAGyymmddThhmm_RAW_HK.ASC
Calibration files: RPCMAG_GND_CALIB_FSDPU_FM<sensor>.TXT,
Boom alignment file: RPCMAG_SC_ALIGN.TXT
* Functions of GEN_CAL_DATA:
1) apply temperature dependent ground calibration results to get B-field in unit coordinates. 2) apply actual ?inflight? temperature model to get rid of temperature influence. This model
has to be created with assistance of the IDL S/W CALIB_ROS_TEMP_xxxx before.
2) turn B-field from instrument to s/c coordinates
3) apply attitude data to get B-field in EME2000 frame ( or a similar one)
4) apply filters, spike detectors,.... data processing routines to get ``scientific
usable magnetic field data�� in ASCII time series.
? GEN_CAL_DATA writes
PDS compliant calibrated data files and labels on different stages (*.tab, *.lbl).
* There exist some more routines to generate proper data:
* GEN_LEV_n_data to produce all Levels of calibarated, resampled and direved data.
* REACTION_WHEELS to plot spectra of the 4 reaction wheels
* BATCH_ADD_GEOINFO_TO_LBL to add all the relevant GEO-keywords and values to the lbl files
* BATCH_ADD_QUALITY to add quality flag placeholders to the TAB files and the quality flag description to the lbl files.
* BATCH_SET_QUALITY to write the right quality flags into the TAB file.after the quality has been assessed and been written to an overall quality index file.
* BATCH_FORMAT_LBL_FILES to generate lines of 80 chars length
* CREATE_LIST_RPCMAG_DATA_OVERVIEW and
* CREATE_PLOT_RPCMAG_DATA_OVERVIEW and
* QUALITY_CHECK to generate an up to date document which shows statistics about all processed data and overview plots including quality flag marked ranges of bad data
After generating all the dataset and checking them with PVV the data are copy (via SCP) to the Imperial college SFTP server. From here all RPC data will be sent (sftp?ed) to the PSA. This last
step is under responsibility of our overall RPC archive engineer.
2.1.2 Conversion of ADC-Counts to Physical Values
The measured values of the instrument are digitized by ADC-converters. The conversion from the raw ADC- counts to meaningful physical raw values (still uncalibrated) is different for magnetic field values and housekeeping values like e.g. instrument voltages. The following subsections shows detailed algorithms of the conversion from ADC counts to physical values:
* Science Data: Magnetic field values (range = +-15000nT , 20 Bit):
MAX_B = +15000 nT
MIN_B = -15000 nT
COUNTS = 220 = 1048576
NOMINAL_FACTOR = (MAX_B - MIN_B) / COUNTS
The binary values of the 20-bit ADC Output are in the range of 00000h : FFFFFh corresponding to decimal values of 0 :(COUNTS-1)
As the ADC is operated in bipolar mode the nominal relation between counts and magnetic field is as follows:
00000h <-> MIN_B
80000h <-> 0
FFFFFh <-> MAX_B
The conversion routine from binary TM data to ASCII Rawdata converts the binary values to signed integers in the following way
00000h -> -COUNTS/2
80000h -> 0
FFFFFh -> +COUNTS/2
These signed integers in the range from -COUNTS/2 to +COUNTS/2 are the EDITED RAW DATA.Unit is [counts]. To convert these into uncalibrated [engineering, enT] nanotesla values, the following algorithm is applied:
B= [ADCvalue + COUNTS/2] * NOMINAL_FACTOR + MIN_B [enT]
Also the Housekeeping Reference Voltage is monitored via a 20-bit ADC and converted in the same manor.
* Housekeeping Data: Magnetic field values (range = +-15000nT, 16 bit)
MAX_B = +15000 nT
MIN_B = -15000 nT
COUNTS = 2^16 = 65536
NOMINAL_FACTOR = (MAX_B - MIN_B) / COUNTS
The binary values of the 16 bit ADC Output are in the range of 0000h : FFFFh corresponding to decimal values of 0 :(COUNTS-1) . As the ADC is operated in bipolar mode the nominal relation between counts and magnetic field is as follows:
0000h <-> MIN_B
8000h <-> 0
FFFFh <-> MAX_B
The conversion routine from binary TM data to ASCII Rawdata converts the binary values to signed integers in the following way
0000h -> -COUNTS/2
8000h -> 0
FFFFh -> +COUNTS/2
These signed integers in the range from -COUNTS/2 to +COUNTS/2 are the EDITED RAW DATA.Unit is [counts].
To convert these into uncalibrated [engineering, enT] nanotesla values, the following algorithm is applied:
B= [ADCvalue + COUNTS/2] * NOMINAL_FACTOR + MIN_B [enT]
* Housekeeping Data: Voltages (range = +-5V, 16 bit)
MAX_V = +2.5 V
MIN_V = -2.5 V
COUNTS = 2^16 = 65536
NOMINAL_FACTOR = (MAX_V - MIN_V) / COUNTS
The binary values of the 16 bit ADC Output are in the range of 0000h : FFFFh corresponding to decimal values of 0 :(COUNTS-1). As the ADC is operated in bipolar mode the nominal relation between counts and magnetic field is as follows:
0000h <-> MIN_V
8000h <-> 0
FFFFh <-> MAX_V
The conversion routine from binary TM data to ASCII Rawdata converts the binary values to signed integers in the following way
0000h -> -COUNTS/2
8000h -> 0
FFFFh -> +COUNTS/2
These signed integers in the range from -COUNTS/2 to +COUNTS/2 are the EDITED RAW DATA.Unit is [counts].
To convert these into voltages, the following algorithm is applied:
U= [ADCvalue + COUNTS/2] * NOMINAL_FACTOR + MIN_V [V]
Also the nominal temperatures are computed from HK voltages in a similar way. Some voltage are monitored as 8bit values; the conversion, however, is done in the same way.
2.2 Overview of Data Products
RPCMAG will only deliver Flight data to the PSA. Data of the Ground calibration and the system tests cannot be converted to PDS compliant format and will be stored directly at IGEP. Relevant documentation will also be saved in the ROSETTA Knowledge Management System (ROKSY).
No software will be archived at the PSA.
2.2.1 Instrument Calibrations
The calibration for RPC-MAG has been performed completely. This means every electronics unit (DPU:FS,DPU:FM) has been calibrated connected with each sensor (Outboard sensor FS & FM, Inboard sensor FS & FM). Thus the results of all calibrations and cross calibrations will be archived.
Only the results are archived in PDS. These are
* Temperature dependent Sensitivity-Matrices
* Temperature dependent Alignment-Matrices
* Temperature dependent Offsets-Matrices
* Frequency behavior
During the calibration and integration of the instrument it turned out, that there were slight differences between the Flight model (FM) and Flight spare unit (FS) of the instruments. We choose the best one for the real flying units. These are:
? DPU: FS
? IB-Sensor: FM
? OB-Sensor: FM
So the original FM Digital Processing unit (DPU) operates with the Flight Spare (FS) sensors onboard ROSETTA.
2.2.2 In-Flight Data Products
Sensor temperatures of the MAG inboard and outboard sensors are delivered in the raw data files.
From the DDS we get raw data in instrument coordinates. These will be rotated into s/c-coordinates, the ground calibration parameters will be applied, and a temperature correction will be performed. The result of this procedure will be calibrated data.
On a higher level we will rotate these data in a convenient celestial body frame (e.g. EME2000, ECLIPJ2000, CSO, ..) and average these data to a convenient rate (e.g. 1s mean). A degapping and despiking filter can be applied.
The principal structure of the data products is the same for all mission phases. We will deliver ASCII tables containing at least 3 component magnetic field data and the related times in UTC and OBT. The raw data files will contain the sensor temperatures as well, as these are needed to calculate the real magnetic field.
The term ?Calibrated data? means that the results of the Ground calibration will be applied to the raw data. The spacecraft generated residual fields and the structures arising from the s/c noise are NOT removed in these data.
The elimination of these effects is under development and will lead to derived data products (TBD).
A major success in improving the data quality has been achieved by creating a Reaction Wheel frequency elimination algorithm. The rotation frequencies of ROSETTA?s 4 reaction wheels can be identified as disturbance spectral lines in the dynamic spectra of the MAG data. Therefore, a frequency elimination filter (dynamic sharp notch filter) had to be developed to get rid of the reaction wheel impact. The filter works satisfactory, especially for the burst data. A quite similar filter also purges the data from the LAP disturbances, which occured as constant frequency lines (mode dependent) in the dynamic spectrum.
During the Earth Swing by it turned out that the Lander heater currents disturb the RPCMAG data. The disturbance is in the order of a nanotesla.The elimination of this disturbance is done semi manually but the generation of the archive files can be done automatically using DDS2PDS.
All higher level data products (CALIBRATED, RESAMPLED, DERIVED) contain quality flags for each magnetic field vector.
During the analysis of the EAR1 data and the comparison of the measured data with the Earth Magnetic Field model data (POMME model from GFZ ,Potsdam) it turned out that the time stamp of the measured and filtered data has to be shifted slightly due to the filter algorithm used in the PIU software. If the time stamp is uncorrected, as it is for all the data products for the phases CVP, EAR1, and CR2 level V1.0, the time of the data is a little bit to early. This means that a certain dt (s. tables) has to be added to the time stamp to get the right times. This additional time offset is mode dependent and also dependent on the actual primary / secondary sensor.
For the data of the PRIMARY sensor, which is usually the OB sensor, the following table shows the times to be added to the time stamp of the vector to get the real physical event time:
SID
Mode Name
Packet Length [s]
Time to add to PRIMARY data timestamp [s]
SID1
Minimum
1024
223.7
SID2
Normal
32
8.2 1
SID3
Burst
16
0
SID4
Medium
32
1.35
SID5
Low
128
27.7
SID6
Test
16
0
For the SECONDARY vectors the situation is different as these vectors are not filtered but just picked out of the data stream. The following table applies for the time shift of the SECONDARY vectors.
SID
Mode Name
Packet Length [s]
Time to add to SECONDARY data timestamp [s]
SID1
Minimum
1024
1023.95
SID2
Normal
32
31.95
SID3
Burst
16
15.95
SID4
Medium
32
31.95
SID5
Low
128
127.95
For the later data products, starting with MARS or delivery level higher than V1.0 these corrections will be taken into account automatically by the Archive generation software. The correction is done only for the CALIBRATED, RESAMPLED and DERIVED science data, neither for EDITED data nor for HOUSEKEEPING data. Only the UTC time stamps are changed, the OBT is kept in the originally state.
Data products:
EDITED RAW DATA: Data in ADC Counts
* Housekeeping Data
UTC, OBT, T_OB, T_IB, STAGE_ID_A, STAGE_ID_B, FILTER_CFG, MAG_REF_VOLT,
MAG_NEG_VOLT, MAG_POS_VOLT, BX_OB, BY_OB,BZ_OB
* IB & OB Data
UTC, OBT, BX, BY, BZ, T, QUALITY
CALIBRATED DATA: DATA in Physical units, bad vectors removed, Quality flagged
LEVEL_A Data:
o Housekeeping Data
UTC, OBT, T_OB, T_IB, STAGE_ID_A, STAGE_ID_B, FILTER_CFG, MAG_REF_VOLT,
MAG_NEG_VOLT, MAG_POS_VOLT, BX_OB, BY_OB,BZ_OB
o IB & OB Data in Instrument coordinates
UTC, OBT, BX, BY, BZ, T, QUALITY
LEVEL_B Data:
o IB & OB Data in s/c coordinates
UTC, OBT, BX, BY, BZ, T, QUALITY
LEVEL_C Data:
o IB & OB Data in Celestial body coordinate system, e.g. ECLIPJ2000
UTC, OBT, POS_X, POS_Y,POS_Z, BX,BY,BZ, QUALITY
RESAMPLED DATA : DATA in Physical units, bad vectors removed, Quality flagged
LEVEL_K Data:
o IB & OB Data in s/c coordinates, Lander Heater influence eliminated
Source is corrected LEVEL_B data
UTC, OBT, BX, BY, BZ, T, QUALITY
LEVEL_L Data:
o IB & OB Data in Celestial body coordinate system, e.g. ECLIPJ2000
Source is corrected LEVEL_C data
UTC, OBT, POS_X, POS_Y,POS_Z, BX,BY,BZ, QUALITY
LEVEL_E Data:
o IB & OB Data in Instrument coordinates, derived from LEVEL_A data, data resampled to specified average interval,e.g. 1s, or 1 min
UTC, OBT, BX, BY, BZ,T, QUALITY
LEVEL_F Data:
o IB & OB Data in s/c - coordinates, derived from LEVEL_B or LEVEL_K data, data resampled to specified average interval, e.g. 1s, or 1 min
UTC, OBT, BX, BY, BZ, T, QUALITY
LEVEL_G Data:
o IB & OB Data in Celestial body coordinate system, e.g. ECLIPJ2000, derived from LEVEL_C or LEVEL_L data, data resampled to specified average interval, e.g. 1s, or 1 min
UTC, OBT, POS_X, POS_Y,POS_Z, BX,BY,BZ, QUALITY
LEVEL_H Data: Reaction Wheel Corrected Data
o IB & OB Data in Celestial body coordinate system, e.g. ECLIPJ2000, derived from LEVEL_C or LEVEL_L data, reaction wheel influence eliminated by filtering in frequency domain.
UTC, OBT, POS_X, POS_Y,POS_Z, BX,BY,BZ, QUALITY
LEVEL_I Data: Reaction Wheel Corrected Data, Averaged
o IB & OB Data in Celestial body coordinate system, e.g. ECLIPJ2000, derived from LEVEL_H data, reaction wheel influence eliminated by filtering in frequency domain, data resampled to specified average interval, e.g. 1s, or 1 min
UTC, OBT, POS_X, POS_Y, POS_Z, BX, BY, BZ, QUALITY
DERIVED DATA�(occasionally): DATA in Physical units, bad vectors removed
LEVEL_J Data: PCA processed data
o IB & OB Data derived from LEVEL_G, LEVEL_H or LEVEL_J data, a principal component analysis (PCA) has been applied, output is
One file for correlated data (_C), and
Two files (IB, OB) containing uncorrelated data (_U)
UTC, OBT, POS_X, POS_Y, POS_Z, BX,BY,BZ, QUALITY
Normally EDITED RAW DATA, CLA, CLB, CLC, CLF and CLG data will be produced, in case of heater problems additionally CLK and CLL data will be available. In case of Reaction wheel or LAP disturbance also CLH data will be generated.
The following figure shows an overview about the relation of all produced data types:
DATA PRODUCT OVERVIEW
2.2.3 Software
We do not intend to deliver any software.
2.2.3.1 Calibration Software
The ground calibration s/w is a complex package of different routines which has been used since many years for many missions (e.g. CLUSTER, DS-1, CASSINI, ? ) . The s/w is stored at the IGEP.
A single binary calibration file (*.CCD, Complete Calibration Data) produced by the calibration facility contains all information needed to perform a specific calibration task like offset determination or calculation of sensitivity and alignment. The calibration analysis s/w extracts the needed frames like applied magnetic field of the coil facility, measured fields of the FGM under test, and the actual temperatures. Then an appropriate sensor model will be applied to the data (e.g. linear model or models of higher order) to calculate the temperature dependent sensor parameters like offset, alignment and sensitivity. The frequency behavior will be investigated as well.
At the end of the process a report is written containing all results needed to use the magnetometer. All necessary parameters are written to the result files which are read by the DDS2PDS S/W.
DDS2PDS will apply the ground calibration results and additionally inflight calibration parameter to the data to generate proper archive data. In case of disturbance by ROSETTA?s reaction wheels special filters in the frequency domain can be applied to get rid of the reaction wheel frequencies in the magnetic field data. This can be done automatically if needed. This elimination requires the knowledge of the reaction wheel frequencies which have to be retrieved from the DDS prior to the analysis.
Also the Lander heater currents have an influence to the magnetic field data. This impact can be eliminated semi manually by comparing Lander HK data, ROMAP signatures and the RPCMAG data. The used s/w is not part of the DDS2PDS package.
It is a known fact that the magnetic field sensors are very temperature sensitive. This behaviour has been calibrated at the ground calibration down to ? 60�C. In flight, however, lower temperatures are seen. It turned out that the extrapolation of the ground calibration results (only the temperature dependent offset shift) did not lead to really convincing results. Therefore inflight data were taken to create a new temperature model of the offset behavior. For the early mission phases a common model, based on CVP & EAR1 data was used ? the so called model 002. During the Mars swing by it turned out that the usage of a model based on daily changes yields to even better results. Especially due to hysteretic effects (in terms of temperature influence) of the magnetic field sensor it showed up that a more sophisticated temperature model was needed
Therefore the CALIB_ROS_TEMP_XXXX and the GEN_CAL_DATA S/W (IDL) were improved/extended to handle this more complex task, leading to model 006. Also the method was changed. The model 002 was achieved by calculating a best fit 3rd order polynomial of the sensor temperatures to the magnetic field (one polynomial for each of the 6 sensor components).
For the calculation of the new model 006 a different approach based on the following items, has been chosen:
* The correlation of the OB magnetic field readings and the OB temperature has to be minimal.
* The correlation of the IB magnetic field readings and the IB temperature has to be minimal.
* The correlation of the IB magnetic field readings and the OB magnetic field readings has to be maximal.
* The influence of the temperature can be eliminated (minimized) by subtracting suitable polynomials P(T) from the magnetic field readings.
* The coefficients of these 6 polynomials are calculated from the optimization of the 9 above mentioned correlation coefficients.
Mathematically this is done by a POWELL minimization routine.
It showed up that the best result is achieved if this calculation is done day by day in order to really take the right temperature behavior into account. The former temperature model showed significantly worse results especially at lower temperatures and faster temperature changes. The calculated polynomials can be of 5th order, but the analysis yielded that linear ones with only very little quadratic and cubic contribution are the best ones. All the MARS data and future data will be calibrated using this new model.
2.2.3.2 Pipeline processing Software
The pipeline processing s/w is named DDS2PDS. A coarse overview has been given already in chapter 2.2.
DDS2PDS can be used with a command file in batch mode. Thus, data of many days can be processed automatically. The output of DDS2PDS are PDS files sorted by modes and times and calibration levels. Usually there will be one file per day and mode and level. CLH, CLK, and CLL file are generated only if disturbances occur and if they can be eliminated.
The format and the content of all PDS *:TAB files is stated in chapter 2.4.5.
2.2.3.3 Scientific analysis Software
The DDS2PDS software has also the capability to generate different kinds of plots. Thus time series can be plotted for every calibrated data level. Additionally spectra plots can be generated as well as plots of the differences of the OB & IB sensor.
Higher Level analysis software is currently under development.
2.2.4 Documentation
The features of the DDS2PDS s/w package will be described in the
DDS2PDS User Manual, RO-IGEP-TR0007.
This manual is part of the documentation package. The S/W itself, however, will not be delivered to the archive.
2.2.5 Derived and other Data Products
Actually it is not planned to deliver other derived data products than the described ones in section 2.4.5.
2.2.6 Ancillary Data Usage
For calculation of the magnetic field in a celestial reference coordinate system it is essential to have information about the attitude of the s/c and the position of the s/c. These data have to be available on the DDS.
Without these ancillary data (ATNR, ORER, ORHR,?) the generation of LEVEL_C (or higher level) data is not possible. The files can be retrieved from the AUXILIARY data section of the ROSETTA DDS. The format and content of these files is described in the ROSETTA DDID RO-ESC-IF-5003.
The Attitude information is extracted from the actual ATNR file. Currently this is ATNR_FDLRMA_DAP040302093352_0053.ROS. This ASCII file is provided by ESOC/TOS-GFI and contains ROSETTA?S state attitude quaternions. The actual attitude can be evaluated using the OASW S/W provided by ESOC.
The positions of the s/c are retrieved from the ORxx files. All positions are given here in the EME2000 frame. The coordinate systems centers, however, are different:
FILE
COORDINATE SYSTEM CENTER
ORHR
SUN
ORER, ORFR,ORGR
EARTH
ORMR
MARS
These ASCII file are provided by ESOC/TOS-GFI as well and contain ROSETTA?S state vectors (positions & velocities for given times). The position for a specific time can be evaluated using the OASW S/W provided by ESOC.
In the future we will also use SPICE kernels generated by the JPL NAIF group. The input to the ROSETTA trajectory and attitude kernels is provided by the ESOC Flight dynamic team.
3 Archive Format and Content
3.1 Format and Conventions
3.1.1 Deliveries and Archive Volume Format
PDS compliant data will be delivered to ESA on DATA SET Level. One Data Set corresponds to one Volume.
Data of different Processing Levels will be archived in different Data Sets.
The complete RPCMAG Data Set will be delivered to the Imperial College server. From here all RPC data will be delivered to ESA by the RPC Archive Manager.
3.1.2 Data Set ID Formation
Example: DATA_SET_ID = "RO-X-RPCMAG-3-CVP-RAW-V3.0"
The Data Set Id has the following structure
* RO: Rosetta Orbiter as instrument host
* <target_Id> :
* E: Earth,
* A: Asteroid
* M:Mars
* C:Comet
* X: Checkout
* CAL:Calibration
* SS:SOLAR WIND
* D: Dust
* RPCMAG: Magnetometer Instrument
* <data_Processing_level> : Codmac Level 1...8,N .
According to PDS Standard Reference, Chapter 6.5
* <Mission Phase abbreviation>:
* CVP: Commissioning
* EAR1,EAR2,EAR3 : Earth Swing-By
* CR1?CRn : Cruise Phases
* MARS
* AST1,AST2 : Asteroid Fly-by
* RVM1,RVM2 : Rendezvous Maneuvre
* NCD�: Near comet Drift
* FAT / CAT: Far / Close Approach Trajectory
* TGM : Transition to Global mapping
* GMP: Global mapping Phase
* COP : Close Observation Phase
* SSP : Lander delivery
* LOW / HIGH :Comet Activity low/ high
* MINC: Comet Activity moderate increase
* SINC: Comet Activity sharp increase
* PERI : Near Perihelion
* EXT: Extended Mission
Accumulated Phases:
* APPR : Approach FAT to COP
* ESCO : Escort LOW to PERI
* COM : Comet FAT to PERI
Designators according to RO-EST-PL-5011, Table 2
* Description: processing level?
* V3.0 version number
3.1.3 Data Directory Naming Convention
DATA_SET_ID
����DOCUMENT
� ����ARCHIVING
� ����CALIBRATION
� ����PROCESSING
� ����INSTRUMENT
�
����CALIB ; Results of GND & InFlight Calibration
����CATALOG
����DATA
����CALIBRATED ; calibrated magnetic field data
� � ; data in physical units
� ���2004
� ����MAR
� ���LEVEL_A ; instrument coordinates
� � ��HK ; Housekeeping data t, ...
� � ��IB ; Inboard sensor: t,B,T, QUAL
� � ��OB ; Outboard sensor: t,B,T, QUAL
� �
� ���LEVEL_B ; s/c coordinates
� � ��IB ; Inboard sensor: t,B,T, QUAL
� � ��OB ; Outboard sensor: t,B,T, QUAL
� �
� ���LEVEL_C ; B in celestial coords. & positions
� ��IB ; Inboard sensor: t,r,B, QUAL
� ��OB ; Outboard sensor: t,r,B, QUAL
�
�
����DERIVED ; higher level data products
� ���2004 ; year
� ���MAR ; month
� ���LEVEL_J ; Level
� �CORRELATED ; PCA correlated part
� �UNCORRELATED ; PCA uncorrellated part
� ��IB ; Inboard sensor: t,r,B, QUAL
� ��OB ; Outboard sensor: t,r,B, QUAL
�
�
����EDITED ; magnetic field raw data
� � ; in ADC counts
� ���2004
� ����MAR
� ��HK ; Housekeeping data
� ��IB ; Inboard sensor: t,B,T,Quality
� ��OB ; Outboard sensor: t,B,T,Quality
����RESAMPLED ; Averaged data products
���2004 ; year
���MAR ; month
���LEVEL_K ; Level, S/C. coords,Heater corr.
� ��IB ; Inboard sensor: t,B,QUAL
� ��OB ; Outboard sensor: t,B,QUAL
�
���LEVEL_L ; Level,celestial. Coords,Heater corr.
� ��IB ; Inboard sensor: t,B, QUAL
� ��OB ; Outboard sensor: t,B, QUAL
�
�
���LEVEL_E ; Level, Inst. coords
� ��IB ; Inboard sensor: t,B, QUAL
� ��OB ; Outboard sensor: t,B, QUAL
�
���LEVEL_F ; Level, s/c-coords
� ��IB ; Inboard sensor: t,B, QUAL
� ��OB ; Outboard sensor: t,B, QUAL
�
�
���LEVEL_G ; Level, Celestial coords
� ��IB ; Inboard sensor: t,r,B, QUAL
� ��OB ; Outboard sensor: t,r,B, QUAL
�
�
���LEVEL_H ; Level, RW- corrected
� ��IB ; Inboard sensor: t,B, QUAL
� ��OB ; Outboard sensor: t,B, QUAL
�
�
���LEVEL_I ; Level, RW- averaged
��IB ; Inboard sensor: t,B, QUAL
��OB ; Outboard sensor: t,B, QUAL
This directory shows the complete internal data structure, which gives an detailed overview of all processed data. When the data will be delivered to the PSA, the transmitted structure will be adapted in that way, that only the data of a single processing level (EDITED, CALIBRATED, RESAMPLED,?) will go into the designated data set. There are no empty folders . Data of different processing levels will go to different data sets.
For every activated mode there will be one single file for each day where data have been measured. This means that there can be data gaps in the file if e.g. there were some measurements in the morning and some others in the evening.
3.1.4 Filenaming Convention
Magnetic Field data filename convention for EDITED and CALIBRATED data:
<inst> <begin of observation>_<level>_<sensor>_<inst mode>.<ext>
RPCMAG yymmddThhmm RAW IB M1..M6 LBL
CLA OB TAB
CLB
CLC
Example: RPCMAG040528T1230_CLC_OB_M3.LBL
RPCMAG040528T1230_CLC_OB_M3.TAB
Magnetic Field data filename convention for RESAMPLED averaged data (CLE,CLF,CLG,CLI):
<inst> <begin of observation>_<level>_<sensor>_A<average>.<ext>
RPCMAG yymmdd CLE IB A60 LBL
CLF OB TAB
CLG
CLI
Example: RPCMAG040528_CLG_OB_A20.LBL
RPCMAG040528_CLG_OB_A20.TAB
Average denotes the time interval for one average period in seconds.
Magnetic Field data filename convention for RESAMPLED Heater or Reaction Wheel influenced data (CLK, CLL, CLH):
<inst> <begin of observation>_<level>_<sensor>_<inst mode>.<ext>
RPCMAG yymmddThhmm CLK IB M1..M6 LBL
CLL OB TAB
CLI
Example: RPCMAG040528T1230_CLK_OB_M3.LBL
RPCMAG040528T1230_CLK_OB_M3.TAB
Magnetic Field data filename convention for PCA corrected data:
Correlated data:
<inst> <begin of observation>_<level>_A<average>_C.<ext>
RPCMAG yymmdd CLJ A60 LBL
TAB
Example: RPCMAG040528_CLJ_A20_C.LBL
RPCMAG040528_CLJ_A20_C.TAB
Average denotes the time interval for one average period in seconds.
Uncorrelated data:
<inst> <begin of observation>_<level>_<sensor>_A<average>_U.<ext>
RPCMAG yymmdd CLJ IB A60 LBL
CLJ OB TAB
Example: RPCMAG040528_CLJ_OB_A20_U.LBL
RPCMAG040528_CLJ_OB_A20_U.TAB
RPCMAG040528_CLJ_IB_A20_U.LBL
RPCMAG040528_CLJ_IB_A20_U.TAB
Average denotes the time interval for one average period in seconds.
Housekeeping data Convention:
<inst> <begin of observation>_<datatype>.<ext>
RPCMAG yymmddThhmm _ HK LBL
TAB
Example: RPCMAG040528T1230_HK.LBL
RPCMAG040528T1230_HK.TAB
3.2 Standards Used in Data Product Generation
3.2.1 PDS Standards
MAG complies to PDS version 3, and we use version 3.6 of the PDS standard reference.
3.2.2 Time Standards
The Time Standard used for RPC-MAG obey the definitions stated in
Rosetta Time Handling, RO-EST-TN-3165, sect. 4.2
UTC Time Format :
Time(UTC) in LBL files: yyyy-mm-ddThh:mm:ss.sss
Time(UTC) in TAB files: yyyy-mm-ddThh:mm:ss.ssssss
ss.sss means: ?seconds . decimal fractional seconds?
OBT Time Format:
The PDS keywords
SPACECRAFT_CLOCK_START_COUNT and
SPACECRAFT_CLOCK_STOP_COUNT
refer to OBT.
The header of the experiment telemetry source packets contains the data acquisition start time in OBT as 32 bit of unit seconds followed by 16 bit of fractional seconds. OBT = 0 is at 2003-01-01-T00:00:00 UTC. The time resolution is 2^(-16) = 1.53E-5 seconds. The OBT is represented in the following format:
SPACECRAFT_CLOCK_START/STOP_COUNT = "<reset number>/<unit seconds>.<fractional seconds>"
The unit seconds and the fractional seconds are separated by the full stop character (?.?). Note that this is not a decimal point. The fractional seconds are expressed as multiples of 2^(-16) = 1.53E-5 seconds and count from 0 to 2^16 -1= 65535.
E.g. in SPACECRAFT_CLOCK_START_COUNT = "1/21983325.392" the 392 fractional seconds correspond to 392 * 2^(-16) = 0.00598 decimal seconds.
The spacecraft clock could be reset during the mission (although this is not planned). This would imply a change of the zero point. The zero point of the OBT will be indicated by pre-pending the reset number (integer starting at 1) and a slash to the unit seconds, i.e. "1/" means OBT = 0 at 2003-01-01T00:00:00 UTC.
Spacecraft Clock (OBT) in LBL files: ?r/nnnnnnnnnn.nnnnn?
Spacecraft Clock (OBT) in TAB files: nnnnnnnnnn.nnnnn
Here r means the reset number starting at 1. As the OBT is in the TAB files is supposed to be just an add-on information only the value of the clock without the reset number is stored. Probably nobody will use the OBT inside the TAB files as UTC is available for a comparison with other data.
3.2.3 Reference Systems
System Name
Definition
Instrument coordinates
RPC-MAG unit reference systems for the Inboard (IB) and Outboard (OB) sensor. Systems are defined relative to the S/C coordinate sytem using matrices for the stowed and deployed boom orientations.
Orientation: ref. to RPC USER MANUAL
S/C coordinates
Orientation: x: pointing from the LANDER to the s/c center, perpendicular to solar array axes; y:parallel to solar array axis; pointing to the left, when standing in front of the Lander, z: pointing up
EME2000
Earth Mean Equator inertial reference frame related to Equinox of Epoch J2000.
Orientation: X: Pointing from SUN to Vernal Equinoxe, Y: perpendicular to X in Earth Equatorial plane, Z: Perpendicular to Earth Equatorial plane, pointing up
ECLIPJ2000
Ecliptic Coordinates related to Equinox of Epoch J2000.
Orientation: X: Pointing from SUN to Vernal Equinoxe, Y: perpendicular to X in Ecliptic Plane, Z: Perpendicular to Ecliptic plane, pointing up
CSO
Comet Centric Solar Orbital System.
Orientation: X: Pointing from COMET to SUN,
Y: The inertially referenced velocity of the sun relative to the comet is the secondary vector: the Y axis is the component of this velocity vector orthogonal to the X axis.
Z: Perpendicular to X and Y, completing system to be right handed
GSE
GEO Centric Solar Ecliptic System.
Orientation: X: Pointing from EARTH to SUN, Y: perpendicular to X in Ecliptic plane, Z: Perpendicular to Ecliptic plane, pointing up
MSO
Mars Centric Solar Orbital System.
Orientation: X: Pointing from MARS to SUN, Y: perpendicular to X against planetary motion, Z: Perpendicular to X & Y, completing system to be right handed
3.2.4 Other Applicable Standards
N/A
3.3 Data Validation
For the validation of the data, data of the OB and IB sensor will be compared. They should show similar structures, originated in the solar wind. Due to the distortions of the s/c, however, there will be uncorrelated structures as well. The temperatures of both sensors should be nearly identical. A comparison of the MAG data with the data of the Lander magnetometer ROMAP will reveal precious information.
For a more quantitative assessment quality flags have been implemented to each magnetic field vector stored in TAB file. The quality flag is a string of 8 digits. The definition of this flag system is given in the following table
# FLAG-STRING FLAG DESCRIPTION
# 87654321
# ::::::::------ 1 IMPACT OF REACTION WHEELS
# ::::::: x = impact not assessed
# ::::::: 0 = no disturbance
# ::::::: 1 = disturbance eliminated during data analysis
# ::::::: 2 = disturbance elimination failed
# ::::::: 3 = data disturbed
# :::::::
# :::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
# :::::: x = impact not assessed
# :::::: 0 = no disturbance
# :::::: 1 = disturbance eliminated during data analysis
# :::::: 2 = disturbance elimination failed
# :::::: 3 = data disturbed
# ::::::
# ::::::-------- 3 BOOM DEPLOYMENT:
# ::::: 0 = boom deployed
# ::::: 1 = boom stowed
# ::::: 2 = boom deployment ongoing. Data only valid in instrument coordinates
# ::::: 3 = pyros fired for boom release
# :::::
# :::::--------- 4 OFFSET RELATED EFFECTS:
# :::: x = offset issues not assessed
# :::: 0 = no offset problems
# :::: 1 = offset behavior not clear
# :::: 2 = offset drifts, sensor not in thermal equilibrium thus temperature model N/A
# :::: 3 = offset drifts, reason unknown
# :::: 4 = offset jump detected, reason unknown
# ::::
# ::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
# ::: x = correlation not assessed
# ::: 0 = perfect correlation
# ::: 1 = good correlation
# ::: 2 = poor correlation
# ::: 3 = IB and OB show different long term behavior
# :::
# :::
# :::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
# :: x = no assessment
# :: 0 = no other problems detected
# :: 1 =
# :: 2 =
# :: 3 =
# :: 4 =
# :: 5 = data disturbed by AC signal originated in s/c
# :: 6 = data noisy due to power on failure
# :: 7 = data not calculatable due to thermistor failure
# :: 8 = sensor saturated due to huge external field
# :: 9 = sensor saturated, instrument power on sequence failed
# ::
# ::------------ 7 TBD
# : x = no assessment
# : -------------8 TBD
# x = no assessment
#
With this complex quality assessment system it is possible to quantify the quality of each single vector in a detailed way. It is flexible enough to be adapted to widely spread future needs.
At a first step the flags have to be determined and written to an overall time oriented index file. Each time a flag changes a new entry has to be generated. This step has to be done manually day by day. Once this index file has been generated the S/W BATCH_SET_QUALITY will read this file and pad each vector in every related TAB file with the right quality flag.
Flag evaluation Process:
Flag 1: Impact of Reaction wheels
This influence is checked by comparison of the dynamic frequency spectra of the magnetic field vectors and the spectra of the reaction wheels obtained from the DDS TM files. After calculation of the spectra the flags can easily be determined manually day by day ( Optical comparison of plots: do disturbing spectral lines exist or not)
Flag 2: Impact of Lander Heater Currents
These heater currents were up to now only disturbing during EAR1. The overall switch on/off times of this disturbance can be retrieved from Lander HK data.
Flag 3: Boom Deployment
The boom has been deployed on March 19, 2004. Exact times are known.
Flag 4, 5: Offset related Effects & Correlation between IB and OB Sensor
The offset is temperature dependent. Although a 3rd order model of the offset?s temperature dependence exists the offset can not be determined exactly at any time. Especially immediately after powering on the instrument (up to a few hours later) the thermal equilibrium is not reached and therefore the thermal model cannot be applied. This leads to arbitrary offset values.
The S/W QUALITY_CHECK performs an automatic analysis of the IB and OB sensor temperatures. It will mark the quality as bad if the magnitude of the 1st derivative of the difference of these temperatures exceeds a certain threshold.
Furthermore various kinds of magnetic field difference plots (IBi-Obi vs .Time, IBi vs.OBi) are generated to get an idea of the offset jumps. The flags will be set according to the inspection.
Flag 6: Other Impacts
Manual inspection of HK data and taking into account all known problems
Flag 7 TBD
Flag 8 TBD.
The Quality assessment is done by the data producer.
3.4 Content
3.4.1 Volume Set
According to Planetary Data System Standard Reference, Version 3.6, Chapter 19, Figure 19.1.
3.4.2 Data Set
Our naming convention for the DATA_SET_NAME will follow the same principles as the DATA_SET_ID in chapter 3.1.3.
DATA_SET_NAME=?ROSETTA-ORBITER <target_name> RPCMAG <level> <Mission phase abbreviation> <Description> <version number>?
<target_name> =
* 67P
* <asteroid short name>
* EARTH
* MARS
* CHECK
* CAL
* DUST
* SW
Target names according to RO-EST-PL-5011, table 4
<level> = Codmac Level 1...8,N . According to PDS Standard Reference, Chapter 6.5
<Mission Phase abbreviation> =
* CVP : Commissioning
* EAR1,EAR2,EAR3 : Earth Swing-By
* CR1?CRn : Cruise Phases
* MARS
* AST1,AST2 : Asteroid Fly-by
* RVM1,RVM2 : Rendezvous Maneuvre
* NCD�: Near comet Drift
* FAT / CAT: Far / Close Approach Trajectory
* TGM : Transition to Global mapping
* GMP: Global mapping Phase
* COP : Close Observation Phase
* SSP : Lander delivery
* LOW / HIGH :Comet Activity low/ high
* MINC: Comet Activity moderate increase
* SINC: Comet Activity sharp increase
* PERI : Near Perihelion
* EXT: Extended Mission
Accumulated Phases:
* APPR : Approach FAT to COP
* ESCO : Escort LOW to PERI
* COM : Comet FAT to PERI
Designators according to RO-EST-PL-5011, Table 2
<Description> = This contains the processing level in text form:
* EDITED
* CALIBRATED
* RESAMPLED
* DERIVED.
<Version Number>= Contains the Dataset version, e.g. V1.0
One data set will be used for each processing level. Multiple targets will be used for each data set and within each data set TARGET_NAME and TARGET_TYPE will be used to identify the current target (Thus they will not stay the same within one data set, but data set id will). The data set name fits in the full length thus 60 characters.
3.4.3 Directories
3.4.3.1 Root Directory
The root directory for the RPCMAG data is named with the DATA_SET_ID. It will only contain the
AAREADME.TXT, the VOLDESC.CAT and the PDSVOLUME.XML info file.
3.4.3.2 Calibration Directory
Contains the files:
CALINFO.TXT ; Info File
RPCMAG_SC_ALIGN.TXT ;Results of the sensor to S/C coordinates alignment
After the S/C integration an optical measurement of the sensor and boom orientation has been carried out by ASTRIUM people at ESTEC. Mirrors were attached to the sensors and the exact alignment wrt. Spacecraft has been determined. The resulting angles are listed in this file for a stowed an a deployed boom.
RPCMAG_GND_CALIB_FSDPU_FMIB.TXT ; GND Calibration results of FS DPU & FM IB sensor
RPCMAG_GND_CALIB_FSDPU_FMOB.TXT; GND Calibration results of FS DPU & FM OB sensor
These two files contain the results of the ground calibration for each SENSOR/DPU combination. All temperature dependent sensitivity, misalignment and offset coefficients (refer to RO-IGM-TR0003, Analysis of the FMG Calibration, Chapters 7 & 8 & 9) are listed here to be read by the data calibration software.
During flight it turned out that the temperature model had to be extended to lower temperatures. Therefore, a new model with additional coefficients has been created. These coefficients are stored in inflight calibration files.
RPCMAG_002_CALIB_IB.TXT ; Inflight Calibration results for the IB sensor
RPCMAG_002_CALIB_OB.TXT; Inflght Calibration results for the OB sensor
These files were used for the early mission phases CVP ?EAR1 ? CR2.
If there should be any need for future changes/improvements of these models/coefficients the file
Counter (currently 002) will be incremented and the new values are stored to new files. The calibration software has the feature to distinguish between the calibration file versions. E.g. for the MARS fly by there are inflight calibration file on daily based data:
RPCMAG_070223_006_CALIB_IB.TXT ; Inflight Calib. for the IB sensor, February 23, 2007
RPCMAG_070223_006_CALIB_OB.TXT; Inflight Calib. for the OB sensor, February 23, 2007
?.
RPCMAG_070227_006_CALIB_IB.TXT ; Inflight Calib. for the IB sensor, February 27, 2007
RPCMAG_070227_006_CALIB_OB.TXT; Inflight Calib. for the OB sensor, February 27, 2007
Temperature models will be created dependent on the data behavior and s/c operations. If there are lots of attitude changes during an observation, the sensor temperature will change accordingly and the usage of daily based calibration files will make sense. In stable phases, however, a single model for a long interval is sufficient.
In the case of using many calibration files for a single observation period, the different offsets between the models have to be adapted. This is done by the files
CLA_OFFSETS_IB.TXT ; Model Offset Correction file for the IB sensor
CLA_OFFSETS_OB.TXT ; Model Offset Correction file for the OB sensor
In these files the first and last magnetic field values of the regarded TAB file are stored. For every entry line there are 3 GND calibration based values and 3 inflight calibration based values per sensor (data are stored in Instrument coordinates). From the last value of the previous data file and the first value of the actual data file the original data jumps (GND calibration based) can be calculated. This jump height is used to set the jump height for the inflight calibration data to the same value to get rid of any artificial field jumps. The calculated offset correction (3 components per sensor) for the actual used model is written also to these files.
File format:
TIME Bx_GND By_GND Bz_GND Bx_IFL By_IFL Bz_IFL OFF_X OFF_Y OFF_Z T
Time in UTC, Magnetic field values in nanoTesla, Temperatures in Kelvin.
3.4.3.3 Catalog Directory
Contains the files:
FILENAME
DESCRIPTION
CATINFO.TXT
This file contains a list of all catalog files located in the CATALOG directory. A brief description of these files is given
DATASET.CAT
This files describes the MAGNETOMETER dataset in the actual mission phase
ROSETTA_INSTHOST.CAT
This file describes the ROSETTA s/c acting as instrument host for all the experiments. This file was provided by ESA.
ROSETTA_MISSION.CAT
This file describes the ROSETTA mission to Comet 67P/Churyumov-Gerasimenko. The file was provided by ESA.
RPCMAG_INST.CAT
This files contains a complete instrument description of the orbiter magnetometer RPC-MAG.
RPCMAG_PERS.CAT
In the file all people responsible for the RPC-MAG data archiving are listed. Contact information is added.
RPCMAG_REF.CAT
The file contains publication references of all publications mentioned in the CATALOG files. Addionally all references to ESA documents are listed here. These references were provided by ESA.
RPCMAG_SOFTWARE.CAT
The files is empty, as no S/W will be provided.
3.4.3.4 Index Directory
This directory contains the index files generated by the ESA S/W PVV.
Additionally the GEOINDEX.LBL and GEOINDEX.TAB files will be located here
3.4.3.5 Browse Directory and Browse Files
N/A
3.4.3.6 Geometry Directory
The needed geometry information will be taken from the ancillary files provided by RSOC via the DDS.
These files are not PDS compliant. RSOC is responsible for archiving them. Thus, there will not be any GEOMETRY directory.
3.4.3.7 Software Directory
It is not planned to deliver any software.
3.4.3.8 Document Directory
Directory Structure:
���DOCUMENT
����ARCHIVING
����CALIBRATION
����FLIGHT_REPORTS
Details about the content of this directory can be found in the DOCINFO.TXT file.
The ARCHIVING folder will contain this EAICD and the DDS2PDS Manual of the used IDL processing software (RO-IGEP-TR0007). The CALIBRATION directory contains the calibration protocols and analysis reports. Also a SETEP by STEP Calibration Procedure is added here.
The documents are saved in the original version as TeX or WORD or PDF files.
For a detailed instrument overview the Instrument Paper RPCMAG_INSTRUMENT is added as PDF version.
A good overview about all instrument operations and events occurring during flight is presented in the RPCMAG Logbook-file. This file is available in ASCII format. Most parts of this file are directly extracted from the DDS TC logging file and the DDS Events file.
3.4.3.9 Data Directory
Refer to 3.1.3
4 Detailed Interface Specifications
4.1 Structure and Organization Overview
The principle data directory strucure sorted by data types was presented in chapter 3.1.3.
The sortation with respect to the time is displayed in the following tree.
����DATA
����CALIBRATED ; calibrated magnetic field data
� � ; data in physical units
� ���2004
� � ����MAR
� � ����APR
� � ���� ..
� � ����DEC
. .
. .
� ���2014
� ����JAN
� ����FEB
� ���� ..
� ����DEC
�
����EDITED ; magnetic field raw data
� � ; in ADC counts
� ���2004
� � ����MAR
� � ����APR
� � ���� ..
� � ����DEC
. .
. .
� ���2014
� ����JAN
� ���� ..
� ����DEC
�
����RESAMPLED ; resampled magnetic field data
� � ; data in physical units
� ���2004
� � ����MAR
� � ����APR
� � ���-MAY
� � ���� ..
� � ����DEC
. .
. .
� ���2014
� ����JAN
� ����FEB
� ���� ..
� ����DEC
Each ?Month? directory contains the different Level and sensor directories as described in
Chapter 3.1.3. For the CALIBRATED data we have
�
���LEVEL_A ; instrument coordinates
� ��HK ; Housekeeping data t, ...
� ��IB ; Inboard sensor: t,B,T,QUAL
� ��OB ; Outboard sensor: t,B,T,QUAL
�
���LEVEL_B ; s/c coordinates
� ��IB ; Inboard sensor: t,B,T,QUAL
� ��OB ; Outboard sensor: t,B,T,QUAL
�
���LEVEL_C ; B in celestial coords. & positions
��IB ; Inboard sensor: t,r,B,QUAL
��OB ; Outboard sensor: t,r,B,QUAL
For the EDITED Data there are only the sensor and housekeeping subdirectories.
��HK ; Housekeeping data
��IB ; Inboard sensor: t,B,T
��OB ; Outboard sensor: t,B,T
For the RESAMPLED data there are LEVEL_N n={E;F;G;H;I} data, which represent s second averaged data merged from all available mode files of the given day.
�
���LEVEL_n
� ��IB ; Inboard sensor: t,(r),B,T,QUAL
� ��OB ; Outboard sensor: t,(r),B,T,QUAL
For the DERIVED data there are LEVEL_J data, which represent s second averaged data
which are the output of a PCA analysis.
���LEVEL_J ; Level
�CORRELATED ; PCA correlated part
�UNCORRELATED ; PCA uncorrellated part
��IB ; Inboard sensor: t,r,B,QUAL
��OB ; Outboard sensor: t,r,B,QUAL
4.2 Data Sets, Definition and Content
We distinguish between four levels: EDITED, CALIBRATED, RESAMPLED, and DERIVED data.
The EDITED data just contain the decommutated TM data in units of ADC counts. Quality flags assign the data quality.
All calibrated data contain data in physical units like Nanotesla and Kelvin?This means, that the results of the ground calibration or inflight calibration have been applied to the data.
The CALIBRATED directory is divided in various sublevels:
* LEVEL_A data are data in instrument coordinates including also sensor temperatures.
S/C generated noise and residual fields are not taken into account.
* LEVEL_B data are magnetic field data in s/c coordinates including temperatures as well.
S/C generated noise and residual field are not taken into account.
* LEVEL_C data are data in celestial coordinates. Nominal s/c position and attitude have been considered during the evaluation. s/c generated noise and residual fields are not taken into account. Data contain s/c positions as well.
The RESAMPLED data are derived from the CALIBRATED data by averaging to a specified average period, e.g. 1second or 1 minute or correcting specific disturbance sources by application of special filters. This leads to
* LEVEL_K data.
These are calibrated, Lander heater influence corrected data in s/c- coordinates. Input were Lander corrected LEVEL_B tables. The elimination of the heater influence has been done by a different s/w in a semi-manual way.
S/C generated noise and residual fields are not taken into account. Different modes are taken into account if necessary. Data are not averaged but resampled due to filter algorithm.
Data of this calibration level will only be produced, if a heater influence occurred.
* LEVEL_L data.
These are calibrated, Lander heater influence corrected data celestial coordinates. Input were Lander corrected LEVEL_C data. The elimination of the heater influence has been done by a different s/w in a semi-manual way.
S/C generated noise and residual fields are not taken into account. Different modes are taken into account if necessary. Data are not averaged but resampled due to filter algorithm.
Data of this calibration level will only be produced, if a heater influence occurred.
* LEVEL_E data.
These are calibrated data in instrument coordinates. Input were LEVEL_A data.
S/C generated noise and residual fields are not taken into account. Data averaged. Different modes are taken into account if necessary. Used for internal use only.
* LEVEL_F data.
These are calibrated data in s/c-coordinates. Input were LEVEL_B or LEVEL_K data.
S/C generated noise and residual fields are not taken into account. Data averaged. Different modes are taken into account if necessary.
* LEVEL_G data.
These are calibrated data in celestial coordinates. S/C position and attitude have been considered during the evaluation. S/C generated noise and residual fields are not taken into account. Data contain s/c positions as well. Data averaged. Different modes are taken into account if necessary.
Input were LEVEL_C or LEVEL_L data.
* LEVEL_H data.
These data are derived from LEVEL_C or LEVEL_L data. A filter algorithm has been applied to get rid of the noise produced by ROSETTA?s reaction wheels. Nominal S/C position and attitude have been considered during the evaluation. Residual fields are not taken into account. Data contain s/c positions as well. Data are not averaged but resampled due to filter algorithm in frequency domain.
* LEVEL_I data.
These are averaged LEVEL_H data in celestial coordinates. S/C position and attitude have been considered during the evaluation. Residual fields are not taken into account. Data contain s/c positions as well. Data are averaged. Different modes are taken into account if necessary.
The DERIVED data are derived from the CALIBRATED data. Currently there are only
* LEVEL_J data.
These data have been processed using a principal component analysis (PCA). As input LEVEL_G or LEVEL_I data can act.
As output two sets of files will be produced: correlated and uncorrelated data. The correlated data are the data which are supposed to represent the solar wind magnetic field. The uncorrelated (IB,OB) data represent the spacecraft noise.
Residual fields are not taken into account. Data averaged. The DC level of these magnetic field data is - per definition of a PCA ? set to zero.
LEVEL_J data are currently used for internal purpose only. Therefore delivery is still TBD.
All data are stored in *.TAB files. All timeseries contain UTC and OBT spacecraft clock as time stamps.
Data Sets will be created for each mission phase and delivered at convenient time afterwards. The data set will contain the data decribed in this document. It is not possible to state any exact data delivery date or data volume size as this is strongly dependent on the course of the mission.
4.3 Data Product Design
4.3.1 General OVERVIEW
We have three types of data:
* Housekeeping data (HK),
* Outboard sensor magnetic field data (OB) and
* Inboard sensor magnetic filed data (IB).
The format of the HK data is different to the OB and the IB data. The latter have, however, the same format inside a given level. Magnetic field data exist for every level, whereas HK data only exist for EDITED and CALIBRATED LEVEL_A data.
A complete set of EDITED Data consists of HK, OB & IB data.
A complete set of LEVEL_A Data consists of HK, OB & IB data.
Higher level data only contain OB & IB data.
RAW data will be delivered as EDITED DATA in one DATA_SET.
LEVEL_A, LEVEL_B and LEVEL_C data will be delivered as CALIBRATED DATA in one DATA_SET.
LEVEL_K, LEVEL_L, LEVEL_E, LEVEL_F, LEVEL_G, LEVEL_H and LEVEL_I data will be delivered as RESAMPLED DATA in one DATA_SET.
LEVEL_J data will be delivered as DERIVED DATA in one DATA_SET (still TBD).
To reduce the data volume the standard delivery includes only EDITED DATA, CLA, CLB, CLC, CLF and CLG data. CLK, CLL, and CLH data will be produced if disturbances occur. CLE and CLJ data are normally only used for internal purpose and are not part of the standard data sets.
4.3.1.1 File Characteristics Data Elements
The *.LBL file will be identified by the FILE_NAME
4.3.1.2 Data Object Pointers Identification Data Elements
The only pointer which is used is the pointer from the *.LBL file to the *.TAB file.
4.3.1.3 Instrument and Detector Descriptive Data Elements
* INSTRUMENT_MODE_ID = "SID<n>"
The instrument can operate in six modes SID1 ? SID6 (n=1..6). Meaning:
o SID1: Minimum Mode
o SID2: Normal Mode
o SID3: Burst Mode
o SID4: Medium Mode
o SID5: Low Mode
o SID6: Test Mode
Mode
Sample
Rate
Packet
Period
Packet
Length
Bit Rate
Vector Rate
Name
SID 1
1/32 Hz
1024 s
32 OB vec
1 IB vec
2 bits/s
0.0625 bits/s
0.03125 vec/s
0.000976 vec/s
Minimum Mode
SID 2
1 Hz
32 s
32 OB vec
1 IB vec
64 bits/s
2 bits/s
1 vec/s
0.03125 vec/s
Normal Mode
SID 3
20 Hz
16 s
320 OB vec
16 IB vec
1280 bits/s
64 bits/s
20 vec/s
1 vec/s
Burst Mode
SID 4
5 Hz
32 s
160 OB vec
1 IB vec
320 bits/s
2 bits/s
5 vec/s
0.03125 vec/s
Medium Mode
SID 5
� Hz
128 s
32 OB vec
1 IB vec
16 bits/s
0.5 bits/s
0.25 vec/s
0.007812 vec/s
Low Mode
SID 6
20 Hz
16 s
320 OB vec
1 IB vec
1280 bits/s
4 bits/s
20 vec/s
0.0625 vec/s
Test Mode
HK
1280 Hz
Internal
32 s
8 words
4 bits/s
House
Keeping
For every activated mode and calibration level there will be one single file for each day where data have been measured. This means that there can be data gaps in the file if e.g. there were some measurements in the morning and some others in the evening. Data for heater or reaction wheel corrected data will only be available if any disturbance occurred.
Mode SID6 is normally switched on only for a few minutes after powering the instrument. This is just a test mode and therefore, SID 6 data are not included in the datasets.
* INSTRUMENT_MODE_DESC = "<name> MODE: <p> PRIMARY & <s> SECONDARY VECTORS PER <q> SECONDS"
The mode description explains exactly how many <p> primary vectors (usually OB) and how many <s> secondary vectors (usually IB) are generated
Per <q> seconds and how this mode <name> is named.
* FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
The coefficients of the digital filter in the MAG flight software can be changed during flight. The Flight software ID will take these features into account.
* PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
The lower magnetometer boom has three positions: STOWED, moving during deployment, and DEPLOYED. For the launch it was stowed, and after the commissioning it will be deployed for the rest of the mission. The knowledge of the boom status is important for the right evaluation of the coordinate system.
4.3.1.4 Structure Definition of Instrument Parameter Objects
N/A
4.3.1.5 Data Object Definition
All data are stored in *.TAB files. Their structure is defined in the OBJECT Table definition within the *.LBL
Files. Each data definition block has as DESCRIPTION which explains the meaning of the assigned data column exactly.
4.3.1.6 Description of Instrument
The detailed description of the instrument is done in the RPCMAG knowledge management video and in a brief overview in the RPCMAG_INST.CAT file. The video ( RO_3DSE_MAG) is stored and administrated by ESA on the ROKSY server. It contains all available information about our instrument. Therefore, the access is limited to our instrument team.
Furthermore a detailed instrument description and first scientific results obtained during the first Earth Flyby in March 2005 can be found in our Instrument paper
RPC-MAG:The Fluxgate Magnetometer in the ROSETTA Plasma Consortium, Glassmeier, Richter, et al., Space Science Reviews,2006?
A copy of this paper is delivered in the DOCUMENT folder of each DATASET.
4.3.1.7 Parameters Index File Definition
N/A
4.3.1.8 Mission Specific Keyword
None
4.3.1.9 Geometry Information
ESA asked for GEOMETRY information in the *.LBL files. The RPCMAG team provides this in the
following way:
SC_SUN_POSITION_VECTOR = . . .
SC_TARGET_POSITION_VECTOR = . . .
SC_TARGET_VELOCITY_VECTOR = . . .
SPACECRAFT_ALTITUDE = . . .
SUB_SPACECRAFT_LATITUDE = . . .
SUB_SPACECRAFT_LONGITUDE = . . .
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
This means that the geometry items SC_SUN_POSITION_VECTOR, SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR provided in the label of the data product are related to the Ecliptic-
J2000 frame. The SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE, however, are related to the actual Planetocentric coordinate system. All the values are valid only for one particular time, the time given by the START_TIME value. All the distances are computed in Kilometers and all angles are given in degrees.
4.3.2 Data Product ?EDITED Magnetic field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 79
FILE_RECORDS = 85435
DATA_SET_ID = "RO-E-RPCMAG-2-EAR1-RAW-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 2 EAR1 RAW V3.0"
PRODUCT_ID = "RPCMAG050301T0014_RAW_OB_M2"
PRODUCT_CREATION_TIME = 2009-12-11T08:49:33
PRODUCT_TYPE = "EDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID2"
INSTRUMENT_MODE_DESC = "
NORMAL MODE: 32 PRIMARY & 1 SECONDARY VECTORS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-01T00:14:40.654
STOP_TIME = 2005-03-01T23:59:59.498
SPACECRAFT_CLOCK_START_COUNT = "1/68256861.20971"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68342380.09737"
START_JULIAN_DATE_VALUE = 2453430.5101927551
STOP_JULIAN_DATE_VALUE = 2453431.4999941904
SC_SUN_POSITION_VECTOR = ( 141029080.44, -49951700.29, 73686.10)
SC_TARGET_POSITION_VECTOR = ( 1358534.84, -322205.99, 73167.86)
SC_TARGET_VELOCITY_VECTOR = ( -3.85, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1391758.931
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
THE DATA QUALITY IS CODED FOR EACH VECTOR IN THE LAST COLUMN OF THE TABLE.
CODE: 0= GOOD DATA; 1= BAD DATA -- EACH SENSOR HAS ITS OWN QUALITY BIT --
BIT0:X, BIT1:Y,BIT2:Z, BIT3=0:OB, BIT3=1 IB"
PROCESSING_LEVEL_ID = 2
DESCRIPTION = "
THIS FILE CONTAINS MAGNETIC FIELD VECTOR RAW DATA OBTAINED BY THE OUTBOARD
MAGNETOMETER ABOARD THE ROSETTA S/C AND THE TEMPERATURE OF THE OUTBOARD
SENSOR. ALL VALUES ARE 20 BIT ADC COUNTS.
FIELD IS GIVEN IN INSTRUMENT COORDINATES"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050301T0014_RAW_OB_M2.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-SID2-RAW"
INTERCHANGE_FORMAT = ASCII
ROWS = 85435
COLUMNS = 7
ROW_BYTES = 79
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 44
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD X COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 52
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 60
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 68
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "RAW TEMPERATURE OF RPCMAG OB SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 76
BYTES = 2
DESCRIPTION = "REFER TO DATA_QUALITY_DESC. VALUE REPRESENTS A FLAG"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.3 Data Product ?EDITED Housekeeping data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 106
FILE_RECORDS = 2697
DATA_SET_ID = "RO-E-RPCMAG-2-EAR1-RAW-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 2 EAR1 RAW V3.0"
PRODUCT_ID = "RPCMAG050301T0002_RAW_HK"
PRODUCT_CREATION_TIME = 2009-12-11T08:49:24
PRODUCT_TYPE = "EDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "HK"
INSTRUMENT_MODE_DESC = "HOUSEKEEPING MODE: 8 WORDS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-01T00:02:05.359
STOP_TIME = 2005-03-01T23:59:57.375
SPACECRAFT_CLOCK_START_COUNT = "1/68256106.02522"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68342378.02522"
START_JULIAN_DATE_VALUE = 2453430.5014509149
STOP_JULIAN_DATE_VALUE = 2453431.4999696184
SC_SUN_POSITION_VECTOR = ( 141024080.54, -49973623.87, 73852.35)
SC_TARGET_POSITION_VECTOR = ( 1361441.35, -322852.72, 73333.05)
SC_TARGET_VELOCITY_VECTOR = ( -3.85, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1394740.801
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "N/A"
PROCESSING_LEVEL_ID = 2
DESCRIPTION = "
THIS FILE CONTAINS HOUSEKEEPING RAW DATA OBTAINED BY THE FLUXGATE
MAGNETOMETER ABOARD THE ROSETTA S/C. ALL VALUES ARE 20 BIT ADC COUNTS."
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050301T0002_RAW_HK.TAB"
OBJECT = TABLE
NAME = "RPCMAG-HK-RAW"
INTERCHANGE_FORMAT = ASCII
ROWS = 2697
COLUMNS = 13
ROW_BYTES = 106
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 44
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
TEMPERATURE OF THE RPCMAG OUTBOARD SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_IB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 52
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
TEMPERATURE OF THE RPCMAG INBOARD SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "STAGE_A_ID"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 60
BYTES = 1
DESCRIPTION = "FILTER TYPE IDENTIFICATION FLAG A"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "STAGE_B_ID"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 62
BYTES = 1
DESCRIPTION = "FILTER TYPE IDENTIFICATION FLAG B"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "FILTER_CFG"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 64
BYTES = 1
DESCRIPTION = "FILTER CONFIGURATION FLAG"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "MAG_REF_VOLTAGE"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 66
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETOMETER REFERENCE VOLTAGE: 2.5 V.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "MAG_NEG_VOLTAGE"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 74
BYTES = 3
UNIT = "N/A"
DESCRIPTION = "
MAGNETOMETER NEGATIVE SUPPLY VOLTAGE:-5V.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "MAG_POS_VOLTAGE"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 78
BYTES = 3
UNIT = "N/A"
DESCRIPTION = "
MAGNETOMETER POSITIVE SUPPLY VOLTAGE:+5V.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 82
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD X COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB-SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 90
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD Y COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB-SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 98
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD Z COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB-SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.4
Data Product ?CALIBRATED LEVEL_A Housekeeping data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 106
FILE_RECORDS = 2697
DATA_SET_ID = "RO-E-RPCMAG-2-EAR1-RAW-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 2 EAR1 RAW V3.0"
PRODUCT_ID = "RPCMAG050301T0002_RAW_HK"
PRODUCT_CREATION_TIME = 2009-12-11T08:49:24
PRODUCT_TYPE = "EDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "HK"
INSTRUMENT_MODE_DESC = "HOUSEKEEPING MODE: 8 WORDS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-01T00:02:05.359
STOP_TIME = 2005-03-01T23:59:57.375
SPACECRAFT_CLOCK_START_COUNT = "1/68256106.02522"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68342378.02522"
START_JULIAN_DATE_VALUE = 2453430.5014509149
STOP_JULIAN_DATE_VALUE = 2453431.4999696184
SC_SUN_POSITION_VECTOR = ( 141024080.54, -49973623.87, 73852.35)
SC_TARGET_POSITION_VECTOR = ( 1361441.35, -322852.72, 73333.05)
SC_TARGET_VELOCITY_VECTOR = ( -3.85, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1394740.801
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "N/A"
PROCESSING_LEVEL_ID = 2
DESCRIPTION = "
THIS FILE CONTAINS HOUSEKEEPING RAW DATA OBTAINED BY THE FLUXGATE
MAGNETOMETER ABOARD THE ROSETTA S/C. ALL VALUES ARE 20 BIT ADC COUNTS."
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050301T0002_RAW_HK.TAB"
OBJECT = TABLE
NAME = "RPCMAG-HK-RAW"
INTERCHANGE_FORMAT = ASCII
ROWS = 2697
COLUMNS = 13
ROW_BYTES = 106
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 44
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
TEMPERATURE OF THE RPCMAG OUTBOARD SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_IB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 52
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
TEMPERATURE OF THE RPCMAG INBOARD SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "STAGE_A_ID"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 60
BYTES = 1
DESCRIPTION = "FILTER TYPE IDENTIFICATION FLAG A"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "STAGE_B_ID"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 62
BYTES = 1
DESCRIPTION = "FILTER TYPE IDENTIFICATION FLAG B"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "FILTER_CFG"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 64
BYTES = 1
DESCRIPTION = "FILTER CONFIGURATION FLAG"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "MAG_REF_VOLTAGE"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 66
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETOMETER REFERENCE VOLTAGE: 2.5 V.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "MAG_NEG_VOLTAGE"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 74
BYTES = 3
UNIT = "N/A"
DESCRIPTION = "
MAGNETOMETER NEGATIVE SUPPLY VOLTAGE:-5V.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "MAG_POS_VOLTAGE"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 78
BYTES = 3
UNIT = "N/A"
DESCRIPTION = "
MAGNETOMETER POSITIVE SUPPLY VOLTAGE:+5V.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 82
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD X COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB-SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 90
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD Y COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB-SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_INTEGER
START_BYTE = 98
BYTES = 7
UNIT = "N/A"
DESCRIPTION = "
MAGNETIC FIELD Z COMPONENT, UNCALIBRATED RAW DATA,
INSTRUMENT COORDINATES, OB-SENSOR.
VALUE IS GIVEN IN ADC_COUNTS"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.5 Data Product ?CALIBRATED LEVEL_A Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 86261
DATA_SET_ID = "RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 3 EAR1 CALIBRATED V3.0"
PRODUCT_ID = "RPCMAG050302T0000_CLA_OB_M2"
PRODUCT_CREATION_TIME = 2009-12-11T08:50:18
PRODUCT_TYPE = "RDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID2"
INSTRUMENT_MODE_DESC = "
NORMAL MODE: 32 PRIMARY & 1 SECONDARY VECTORS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-02T00:00:45.737
STOP_TIME = 2005-03-03T00:00:07.464
SPACECRAFT_CLOCK_START_COUNT = "1/68342418.12288"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68428779.58897"
START_JULIAN_DATE_VALUE = 2453431.5005293638
STOP_JULIAN_DATE_VALUE = 2453432.5000863895
SC_SUN_POSITION_VECTOR = ( 141573911.73, -47460624.75, 54794.95)
SC_TARGET_POSITION_VECTOR = ( 1028637.03, -248948.51, 54393.42)
SC_TARGET_VELOCITY_VECTOR = ( -3.87, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1053352.128
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 3
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C AND THE TEMPERATURE OF THE
OUTBOARD SENSOR. GROUND CALIBRATION RESULTS HAVE BEEN APPLIED TO THE RAW
DATA. FIELD IS GIVEN IN INSTRUMENT-COORDINATES"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
TIMESTAMPS (UTC) OF PRIMARY SENSOR VECTORS HAVE BEEN SHIFTED BY 8.20 s and
TIMESTAMPS (UTC) OF SECONDARY SENSOR VECTORS HAVE BEEN SHIFTED BY 31.95 s
IN ORDER TO CORRECT DIGITAL FILTER TRANSFER FUNCTION."
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050302T0000_CLA_OB_M2.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-SID2-CLA"
INTERCHANGE_FORMAT = ASCII
ROWS = 86261
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.6 Data Product ?CALIBRATED LEVEL_B Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 86261
DATA_SET_ID = "RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 3 EAR1 CALIBRATED V3.0"
PRODUCT_ID = "RPCMAG050302T0000_CLA_OB_M2"
PRODUCT_CREATION_TIME = 2009-12-11T08:50:18
PRODUCT_TYPE = "RDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID2"
INSTRUMENT_MODE_DESC = "
NORMAL MODE: 32 PRIMARY & 1 SECONDARY VECTORS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-02T00:00:45.737
STOP_TIME = 2005-03-03T00:00:07.464
SPACECRAFT_CLOCK_START_COUNT = "1/68342418.12288"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68428779.58897"
START_JULIAN_DATE_VALUE = 2453431.5005293638
STOP_JULIAN_DATE_VALUE = 2453432.5000863895
SC_SUN_POSITION_VECTOR = ( 141573911.73, -47460624.75, 54794.95)
SC_TARGET_POSITION_VECTOR = ( 1028637.03, -248948.51, 54393.42)
SC_TARGET_VELOCITY_VECTOR = ( -3.87, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1053352.128
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 3
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C AND THE TEMPERATURE OF THE
OUTBOARD SENSOR. GROUND CALIBRATION RESULTS HAVE BEEN APPLIED TO THE RAW
DATA. FIELD IS GIVEN IN INSTRUMENT-COORDINATES"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
TIMESTAMPS (UTC) OF PRIMARY SENSOR VECTORS HAVE BEEN SHIFTED BY 8.20 s and
TIMESTAMPS (UTC) OF SECONDARY SENSOR VECTORS HAVE BEEN SHIFTED BY 31.95 s
IN ORDER TO CORRECT DIGITAL FILTER TRANSFER FUNCTION."
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050302T0000_CLA_OB_M2.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-SID2-CLA"
INTERCHANGE_FORMAT = ASCII
ROWS = 86261
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.7 Data Product ?CALIBRATED LEVEL_C Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 86261
DATA_SET_ID = "RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 3 EAR1 CALIBRATED V3.0"
PRODUCT_ID = "RPCMAG050302T0000_CLA_OB_M2"
PRODUCT_CREATION_TIME = 2009-12-11T08:50:18
PRODUCT_TYPE = "RDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID2"
INSTRUMENT_MODE_DESC = "
NORMAL MODE: 32 PRIMARY & 1 SECONDARY VECTORS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-02T00:00:45.737
STOP_TIME = 2005-03-03T00:00:07.464
SPACECRAFT_CLOCK_START_COUNT = "1/68342418.12288"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68428779.58897"
START_JULIAN_DATE_VALUE = 2453431.5005293638
STOP_JULIAN_DATE_VALUE = 2453432.5000863895
SC_SUN_POSITION_VECTOR = ( 141573911.73, -47460624.75, 54794.95)
SC_TARGET_POSITION_VECTOR = ( 1028637.03, -248948.51, 54393.42)
SC_TARGET_VELOCITY_VECTOR = ( -3.87, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1053352.128
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 3
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C AND THE TEMPERATURE OF THE
OUTBOARD SENSOR. GROUND CALIBRATION RESULTS HAVE BEEN APPLIED TO THE RAW
DATA. FIELD IS GIVEN IN INSTRUMENT-COORDINATES"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
TIMESTAMPS (UTC) OF PRIMARY SENSOR VECTORS HAVE BEEN SHIFTED BY 8.20 s and
TIMESTAMPS (UTC) OF SECONDARY SENSOR VECTORS HAVE BEEN SHIFTED BY 31.95 s
IN ORDER TO CORRECT DIGITAL FILTER TRANSFER FUNCTION."
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050302T0000_CLA_OB_M2.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-SID2-CLA"
INTERCHANGE_FORMAT = ASCII
ROWS = 86261
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.8 Data Product ?RESAMPLED LEVEL_K Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 86261
DATA_SET_ID = "RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 3 EAR1 CALIBRATED V3.0"
PRODUCT_ID = "RPCMAG050302T0000_CLA_OB_M2"
PRODUCT_CREATION_TIME = 2009-12-11T08:50:18
PRODUCT_TYPE = "RDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID2"
INSTRUMENT_MODE_DESC = "
NORMAL MODE: 32 PRIMARY & 1 SECONDARY VECTORS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-02T00:00:45.737
STOP_TIME = 2005-03-03T00:00:07.464
SPACECRAFT_CLOCK_START_COUNT = "1/68342418.12288"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68428779.58897"
START_JULIAN_DATE_VALUE = 2453431.5005293638
STOP_JULIAN_DATE_VALUE = 2453432.5000863895
SC_SUN_POSITION_VECTOR = ( 141573911.73, -47460624.75, 54794.95)
SC_TARGET_POSITION_VECTOR = ( 1028637.03, -248948.51, 54393.42)
SC_TARGET_VELOCITY_VECTOR = ( -3.87, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1053352.128
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 3
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C AND THE TEMPERATURE OF THE
OUTBOARD SENSOR. GROUND CALIBRATION RESULTS HAVE BEEN APPLIED TO THE RAW
DATA. FIELD IS GIVEN IN INSTRUMENT-COORDINATES"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
TIMESTAMPS (UTC) OF PRIMARY SENSOR VECTORS HAVE BEEN SHIFTED BY 8.20 s and
TIMESTAMPS (UTC) OF SECONDARY SENSOR VECTORS HAVE BEEN SHIFTED BY 31.95 s
IN ORDER TO CORRECT DIGITAL FILTER TRANSFER FUNCTION."
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050302T0000_CLA_OB_M2.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-SID2-CLA"
INTERCHANGE_FORMAT = ASCII
ROWS = 86261
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.9 Data Product ?RESAMPLED LEVEL_L Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 86261
DATA_SET_ID = "RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 3 EAR1 CALIBRATED V3.0"
PRODUCT_ID = "RPCMAG050302T0000_CLA_OB_M2"
PRODUCT_CREATION_TIME = 2009-12-11T08:50:18
PRODUCT_TYPE = "RDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID2"
INSTRUMENT_MODE_DESC = "
NORMAL MODE: 32 PRIMARY & 1 SECONDARY VECTORS PER 32 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2005-03-02T00:00:45.737
STOP_TIME = 2005-03-03T00:00:07.464
SPACECRAFT_CLOCK_START_COUNT = "1/68342418.12288"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68428779.58897"
START_JULIAN_DATE_VALUE = 2453431.5005293638
STOP_JULIAN_DATE_VALUE = 2453432.5000863895
SC_SUN_POSITION_VECTOR = ( 141573911.73, -47460624.75, 54794.95)
SC_TARGET_POSITION_VECTOR = ( 1028637.03, -248948.51, 54393.42)
SC_TARGET_VELOCITY_VECTOR = ( -3.87, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1053352.128
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 3
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C AND THE TEMPERATURE OF THE
OUTBOARD SENSOR. GROUND CALIBRATION RESULTS HAVE BEEN APPLIED TO THE RAW
DATA. FIELD IS GIVEN IN INSTRUMENT-COORDINATES"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
TIMESTAMPS (UTC) OF PRIMARY SENSOR VECTORS HAVE BEEN SHIFTED BY 8.20 s and
TIMESTAMPS (UTC) OF SECONDARY SENSOR VECTORS HAVE BEEN SHIFTED BY 31.95 s
IN ORDER TO CORRECT DIGITAL FILTER TRANSFER FUNCTION."
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050302T0000_CLA_OB_M2.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-SID2-CLA"
INTERCHANGE_FORMAT = ASCII
ROWS = 86261
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, INSTRUMENT-COORDINATES, OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.10 Data Product ?RESAMPLED LEVEL_E Magnetic Field data? Design
This data product is usually not generated.
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 5
DATA_SET_ID = "RO-X-RPCMAG-4-CVP-RESAMPLED-VGND"
DATA_SET_NAME = "ROSETTA-ORBITER CHECK RPCMAG 4 CVP RESAMPLED VGND"
PRODUCT_ID = "RPCMAG040507_CLE_IB_A200"
PRODUCT_CREATION_TIME = 2009-12-11T12:38:08
PRODUCT_TYPE = "REFDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "COMMISSIONING"
OBSERVATION_TYPE = "COMMISSIONING"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "AVERAGED"
INSTRUMENT_MODE_DESC = "200 S AVERAGES"
TARGET_NAME = "CHECKOUT"
TARGET_TYPE = "N/A"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : INSTRUMENTCOORDS"
START_TIME = 2004-05-07T23:41:20.056
STOP_TIME = 2004-05-07T23:54:40.056
SPACECRAFT_CLOCK_START_COUNT = "1/42594065.17518"
SPACECRAFT_CLOCK_STOP_COUNT = "1/42594865.17518"
START_JULIAN_DATE_VALUE = 2453133.4870376857
STOP_JULIAN_DATE_VALUE = 2453133.4962969450
SC_SUN_POSITION_VECTOR = ( 73620228.85, 111357586.02, -927727.21)
SC_TARGET_POSITION_VECTOR = "N/A"
SC_TARGET_VELOCITY_VECTOR = "N/A"
SPACECRAFT_ALTITUDE = "N/A"
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"DE403-MASSES.TPC",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 4
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
INBOARD MAGNETOMETER ABOARD THE ROSETTA S/C. GROUND CALIBRATION RESULTS HAVE
BEEN APPLIED TO THE RAW DATA. FIELD IS ROTATED TO INSTRUMENTCOORDS
COORDINATES.DATA ARE AVERAGED TO 200 S MEANS."
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMIB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: NOT USED"
NOTE = "
DATA SOURCE FOR CLE DATA: LEVEL_A DATA"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG040507_CLE_IB_A200.TAB"
OBJECT = TABLE
NAME = "RPCMAG-IB-200S_AVERAGE-CLE"
INTERCHANGE_FORMAT = ASCII
ROWS = 5
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_IB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, S/C-COORDINATES, 200S_AVERAGE-IB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_IB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, S/C-COORDINATES, 200S_AVERAGE-IB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_IB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, S/C-COORDINATES, 200S_AVERAGE-IB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_IB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG IB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.11 Data Product ?RESAMPLED LEVEL_F Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 90
FILE_RECORDS = 86397
DATA_SET_ID = "RO-E-RPCMAG-4-EAR1-RESAMPLED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 4 EAR1 RESAMPLED V3.0"
PRODUCT_ID = "RPCMAG050305_CLF_OB_A1"
PRODUCT_CREATION_TIME = 2009-12-14T10:30:09
PRODUCT_TYPE = "REFDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "AVERAGED"
INSTRUMENT_MODE_DESC = "1 S AVERAGES"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : S/C-COORDS"
START_TIME = 2005-03-05T00:00:00.715
STOP_TIME = 2005-03-05T23:59:56.715
SPACECRAFT_CLOCK_START_COUNT = "1/68601581.03648"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68687977.03648"
START_JULIAN_DATE_VALUE = 2453434.5000082762
STOP_JULIAN_DATE_VALUE = 2453435.4999619797
SC_SUN_POSITION_VECTOR = ( 142935361.97, -39764663.90, 7610.90)
SC_TARGET_POSITION_VECTOR = ( -2744.86, 42722.39, 8208.04)
SC_TARGET_VELOCITY_VECTOR = ( 1.66, 5.38, 1.23)
SPACECRAFT_ALTITUDE = 37218.863
SUB_SPACECRAFT_LATITUDE = -34.082
SUB_SPACECRAFT_LONGITUDE = 111.667
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 4
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C. GROUND CALIBRATION RESULTS HAVE
BEEN APPLIED TO THE RAW DATA. FIELD IS ROTATED TO S/C-COORDS
COORDINATES.DATA ARE AVERAGED TO 1 S MEANS."
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
DATA SOURCE FOR CLF DATA: LEVEL_K DATA"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050305_CLF_OB_A1.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-1S_AVERAGE-CLF"
INTERCHANGE_FORMAT = ASCII
ROWS = 86397
COLUMNS = 7
ROW_BYTES = 90
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, S/C-COORDINATES, 1S_AVERAGE-OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 54
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, S/C-COORDINATES, 1S_AVERAGE-OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 64
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, S/C-COORDINATES, 1S_AVERAGE-OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "T_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 74
BYTES = 6
UNIT = "KELVIN"
UNIT_ID = "K"
DESCRIPTION = "TEMPERATURE OF RPCMAG OB SENSOR"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 81
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.12 Data Product ?RESAMPLED LEVEL_G Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 125
FILE_RECORDS = 86397
DATA_SET_ID = "RO-E-RPCMAG-4-EAR1-RESAMPLED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 4 EAR1 RESAMPLED V3.0"
PRODUCT_ID = "RPCMAG050305_CLG_OB_A1"
PRODUCT_CREATION_TIME = 2009-12-14T10:23:31
PRODUCT_TYPE = "REFDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "AVERAGED"
INSTRUMENT_MODE_DESC = "1 S AVERAGES"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : ECLIPJ2000"
COORDINATE_SYSTEM_CENTER_NAME = "EARTH"
START_TIME = 2005-03-05T00:00:00.715
STOP_TIME = 2005-03-05T23:59:56.715
SPACECRAFT_CLOCK_START_COUNT = "1/68601581.03648"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68687977.03648"
START_JULIAN_DATE_VALUE = 2453434.5000082762
STOP_JULIAN_DATE_VALUE = 2453435.4999619797
SC_SUN_POSITION_VECTOR = ( 142935361.97, -39764663.90, 7610.90)
SC_TARGET_POSITION_VECTOR = ( -2744.86, 42722.39, 8208.04)
SC_TARGET_VELOCITY_VECTOR = ( 1.66, 5.38, 1.23)
SPACECRAFT_ALTITUDE = 37218.863
SUB_SPACECRAFT_LATITUDE = -34.082
SUB_SPACECRAFT_LONGITUDE = 111.667
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 4
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C. GROUND CALIBRATION RESULTS HAVE
BEEN APPLIED TO THE RAW DATA. FIELD IS ROTATED TO ECLIPJ2000 COORDINATES.
THE S/C POSITION IS GIVEN IN ECLIPJ2000 COORDINATES AS WELL.
DATA ARE AVERAGED TO 1 S MEANS."
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
S/C ATTITUDE COMPUTED USING FILE ATNR_FDLRMA_DAP040302093352_00091.ROS"
NOTE = "
S/C POSITION COMPUTED USING FILE ORER_FDLRMA_DA______________00031.ROS"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_OB.TXT"
NOTE = "
DATA SOURCE FOR CLG DATA: LEVEL_L DATA"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050305_CLG_OB_A1.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-1S_AVERAGE-CLG"
INTERCHANGE_FORMAT = ASCII
ROWS = 86397
COLUMNS = 9
ROW_BYTES = 125
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_X"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, X COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_Y"
DATA_TYPE = ASCII_REAL
START_BYTE = 58
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, Y COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_Z"
DATA_TYPE = ASCII_REAL
START_BYTE = 72
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, Z COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 86
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, 1S_AVERAGE-OB SENSOR, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 96
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, 1S_AVERAGE-OB SENSOR, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 106
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
CORRECTED DATA, 1S_AVERAGE-OB SENSOR, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 116
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.13 Data Product ?RESAMPLED LEVEL_H Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 125
FILE_RECORDS = 916480
DATA_SET_ID = "RO-E-RPCMAG-4-EAR3-RESAMPLED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 4 EAR3 RESAMPLED V3.0"
PRODUCT_ID = "RPCMAG091113T0000_CLH_OB_M3"
PRODUCT_CREATION_TIME = 2010-01-20T15:26:23
PRODUCT_TYPE = "REFDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 3"
OBSERVATION_TYPE = "EARTH SWINGBY 3"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "SID3"
INSTRUMENT_MODE_DESC = "
BURST MODE: 320 PRIMARY & 16 SECONDARY VECTORS PER 16 SECONDS"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : ECLIPJ2000"
COORDINATE_SYSTEM_CENTER_NAME = "EARTH"
START_TIME = 2009-11-13T00:00:39.135
STOP_TIME = 2009-11-13T12:44:23.086
SPACECRAFT_CLOCK_START_COUNT = "1/216691199.45896"
SPACECRAFT_CLOCK_STOP_COUNT = "1/216737023.42418"
START_JULIAN_DATE_VALUE = 2455148.5004529520
STOP_JULIAN_DATE_VALUE = 2455149.0308227553
SC_SUN_POSITION_VECTOR = ( -94206137.70,-114480855.85, 137944.52)
SC_TARGET_POSITION_VECTOR = ( -225968.09, -80438.68, 133137.51)
SC_TARGET_VELOCITY_VECTOR = ( 7.67, 3.18, -4.67)
SPACECRAFT_ALTITUDE = 267955.259
SUB_SPACECRAFT_LATITUDE = -19.022
SUB_SPACECRAFT_LONGITUDE = 337.063
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V15_MAG.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"RSSD0001.TF",
"EARTH_000101_100131_091109.BPC",
"DE405.BSP",
"DSNSTNS.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
PROCESSING_LEVEL_ID = 4
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
OUTBOARD MAGNETOMETER ABOARD THE ROSETTA S/C. GROUND CALIBRATION RESULTS HAVE
BEEN APPLIED TO THE RAW DATA. FIELD IS ROTATED TO ECLIPJ2000 COORDINATES.
THE S/C POSITION IS GIVEN IN ECLIPJ2000 COORDINATES AS WELL.
LAP DISTURBANCE OCCURRING AT CONSTANT FREQUENCIES HAS BEEN ELIMINATED.
DYNAMIC REACTION WHEEL DISTURBANCE SIGNATURE ELIMINATED IN SPECTRUM."
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20100111"
NOTE = "
S/C ATTITUDE COMPUTED USING FILE ATNR_FDLRMA_DAP040302093352_00091.ROS"
NOTE = "
S/C POSITION COMPUTED USING FILE ORGR_FDLRMA_DA______________00091.ROS"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_FMOB.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_091113_006_CALIB_OB.TXT"
NOTE = "
REACTION WHEEL CORRECTIONS HAVE BEEN COMPUTED USING FILE:
D:\ROSETTA\DATA\REACTION_WHEELS\ASCII_DATA\SCHK7_2009-11-13.TXT"
NOTE = "
DATA SOURCE FOR CLH DATA: LEVEL_C DATA"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG091113T0000_CLH_OB_M3.TAB"
OBJECT = TABLE
NAME = "RPCMAG-OB-RW_CORR-CLH"
INTERCHANGE_FORMAT = ASCII
ROWS = 916480
COLUMNS = 9
ROW_BYTES = 125
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_X"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, X COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_Y"
DATA_TYPE = ASCII_REAL
START_BYTE = 58
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, Y COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_Z"
DATA_TYPE = ASCII_REAL
START_BYTE = 72
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, Z COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 86
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED, TEMPERATURE
AND REACTION WHEEL AND LAP DISTURBANCE CORRECTED DATA,
OB SENSOR, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 96
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED, TEMPERATURE
AND REACTION WHEEL AND LAP DISTURBANCE CORRECTED DATA,
OB SENSOR, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_OB"
DATA_TYPE = ASCII_REAL
START_BYTE = 106
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED, TEMPERATURE
AND REACTION WHEEL AND LAP DISTURBANCE CORRECTED DATA,
OB SENSOR, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 116
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
4.3.14 Data Product ?RESAMPLED LEVEL_I Magnetic Field data? Design
This data product is usually not generated. Format like LEVEL_L.
4.3.15 Data Product ?DERIVED LEVEL_J Magnetic Field data? Design
PDS_VERSION_ID = PDS3
LABEL_REVISION_NOTE = "V1.0"
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 125
FILE_RECORDS = 85459
DATA_SET_ID = "RO-E-RPCMAG-5-EAR1-DERIVED-V3.0"
DATA_SET_NAME = "ROSETTA-ORBITER EARTH RPCMAG 5 EAR1 DERIVED V3.0"
PRODUCT_ID = "RPCMAG050301_CLJ_A1_C"
PRODUCT_CREATION_TIME = 2009-12-14T10:33:11
PRODUCT_TYPE = "DDR"
MISSION_ID = "ROSETTA"
MISSION_NAME = "INTERNATIONAL ROSETTA MISSION"
MISSION_PHASE_NAME = "EARTH SWING-BY 1"
OBSERVATION_TYPE = "EARTH SWINGBY 1"
ORBIT_NUMBER = "N/A"
INSTRUMENT_HOST_ID = "RO"
INSTRUMENT_HOST_NAME = "ROSETTA-ORBITER"
INSTRUMENT_ID = "RPCMAG"
INSTRUMENT_NAME = "ROSETTA PLASMA CONSORTIUM - FLUXGATE MAGNETOMETER"
INSTRUMENT_TYPE = "MAGNETOMETER"
INSTRUMENT_MODE_ID = "AVERAGED"
INSTRUMENT_MODE_DESC = "1 S AVERAGES"
NOTE = "
MAGNETIC_COORDINATE_SYSTEM : ECLIPJ2000"
COORDINATE_SYSTEM_CENTER_NAME = "SUN"
TARGET_NAME = "EARTH"
TARGET_TYPE = "PLANET"
START_TIME = 2005-03-01T00:14:42.154
STOP_TIME = 2005-03-01T23:59:00.154
SPACECRAFT_CLOCK_START_COUNT = "1/68256862.70971"
SPACECRAFT_CLOCK_STOP_COUNT = "1/68342320.70971"
START_JULIAN_DATE_VALUE = 2453430.5102101164
STOP_JULIAN_DATE_VALUE = 2453431.4993073386
SC_SUN_POSITION_VECTOR = ( 141029090.37, -49951656.75, 73685.77)
SC_TARGET_POSITION_VECTOR = ( 1358529.07, -322204.71, 73167.53)
SC_TARGET_VELOCITY_VECTOR = ( -3.85, 0.86, -0.22)
SPACECRAFT_ALTITUDE = 1391753.009
SUB_SPACECRAFT_LATITUDE = "N/A"
SUB_SPACECRAFT_LONGITUDE = "N/A"
NOTE ="
The values of the keywords SC_SUN_POSITION_VECTOR,
SC_TARGET_POSITION_VECTOR and SC_TARGET_VELOCITY_VECTOR,
are related to the ECLIPJ2000 reference frame.
SUB_SPACECRAFT_LATITUDE and SUB_SPACECRAFT_LONGITUDE
are northern Latitude and eastern Longitude in the standard
planetocentric IAU_<TARGET_NAME> frame. All values are computed
for the time t= START_TIME.
Distances are given in <km> velocities in <km/s>, Angles in <deg>"
SPICE_FILE_NAME = {"ATNR_P040302093352_00091.BC",
"ROS_LBOOM_V0.BC",
"ROS_V14.TF",
"ROS_SA_2004_V0001.BC",
"ROS_SA_2005_V0001.BC",
"ROS_SA_2006_V0001.BC",
"ROS_SA_2007_V0001.BC",
"ROS_SA_2008_V0037.BC",
"ROS_SA_2009_V0048.BC",
"ROS_HGA_2008_V0018.BC",
"ROS_HGA_2009_V0045.BC",
"ROS_RPC_V15.TI",
"NAIF0009.TLS",
"PCK00008.TPC",
"DE403-MASSES.TPC",
"ROS_090309_STEP.TSC",
"ORER_______________00031.BSP",
"ORFR_______________00067.BSP",
"ORGR_______________00091.BSP",
"ORHR_______________00091.BSP",
"ORMR_______________00052.BSP",
"ORHO_______________00077.BSP",
"ROS_RPC_STRUCT_V1.BSP",
"ROS_STRUCT_V1.BSP",
"EARTH_TOPO_050714.TF",
"EARTHFIXEDIAU.TF",
"EARTHFIXEDITRF93.TF",
"EARTH_000101_060918_060627.BPC",
"DE405.BSP"}
PRODUCER_ID = "RPC_MAG_TEAM"
PRODUCER_FULL_NAME = "INGO RICHTER"
PRODUCER_INSTITUTION_NAME = "IGEP-TU-BRAUNSCHWEIG"
DATA_QUALITY_ID = "N/A"
DATA_QUALITY_DESC = "
ONLY 'GOOD' RAW DATA HAVE BEEN PROCESSED AND STORED"
DESCRIPTION = "
THIS FILE CONTAINS CALIBRATED MAGNETIC FIELD VECTOR DATA OBTAINED BY THE
MAGNETOMETER ABOARD THE ROSETTA S/C. GROUND CALIBRATION RESULTS HAVE BEEN
APPLIED TO THE RAW DATA. FIELD IS ROTATED TO ECLIPJ2000 COORDINATES. THE
S/C POSITION IS GIVEN IN ECLIPJ2000 COORDINATES AS WELL. DATA ARE AVERAGED
TO 1 S MEANS. A PCA HAS BEEN APPLIED. THIS DATA SET CONTAINS THE
CORRELATED DATA"
NOTE = "
LBL & TAB FILE HAVE BEEN GENERATED BY S/W: GEN_CAL_DATA, VERSION V20091209"
NOTE = "
S/C ATTITUDE COMPUTED USING FILE ATNR_FDLRMA_DAP040302093352_00091.ROS"
NOTE = "
S/C POSITION COMPUTED USING FILE ORHR_FDLRMA_DA______________00091.ROS"
NOTE = "
GROUND CALIBRATION FILE: RPCMAG_GND_CALIB_FSDPU_F.TXT"
NOTE = "
INFLIGHT CALIBRATION FILE: RPCMAG_002_CALIB_.TXT"
NOTE = "DATA SOURCE FOR PCA: LEVEL_G DATA"
NOTE = "
DATA SOURCE FOR LEVEL_G DATA were LEVEL_L DATA"
FLIGHT_SOFTWARE_VERSION_ID = "FIL:V1.0"
PLATFORM_OR_MOUNTING_DESC = "MAGNETOMETER_BOOM: DEPLOYED"
^TABLE = "RPCMAG050301_CLJ_A1_C.TAB"
OBJECT = TABLE
NAME = "RPCMAG-CORR_PCA_DATA-1S_AVERAGE-CLJ"
INTERCHANGE_FORMAT = ASCII
ROWS = 85459
COLUMNS = 9
ROW_BYTES = 125
OBJECT = COLUMN
NAME = "TIME_UTC"
DATA_TYPE = TIME
START_BYTE = 1
BYTES = 26
DESCRIPTION = "UTC TIME OF OBSERVATION: YYYY-MM-DDTHH:MM:SS.FFFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "TIME_OBT"
DATA_TYPE = ASCII_REAL
START_BYTE = 28
BYTES = 15
DESCRIPTION = "S/C CLOCK AT OBSERVATION TIME,SECONDS SINCE 00:00
AT 1.1.2003: SSSSSSSSS.FFFFF"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_X"
DATA_TYPE = ASCII_REAL
START_BYTE = 44
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, X COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_Y"
DATA_TYPE = ASCII_REAL
START_BYTE = 58
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, Y COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "POSITION_Z"
DATA_TYPE = ASCII_REAL
START_BYTE = 72
BYTES = 13
UNIT = "KILOMETER"
UNIT_ID = "km"
DESCRIPTION = "SPACECRAFT POSITION, Z COMPONENT, ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BX_CORRELATED"
DATA_TYPE = ASCII_REAL
START_BYTE = 86
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD X COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, 1S_AVERAGE- PCA, CORRELATED DATA,ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BY_CORRELATED"
DATA_TYPE = ASCII_REAL
START_BYTE = 96
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Y COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, 1S_AVERAGE- PCA, CORRELATED DATA,ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "BZ_CORRELATED"
DATA_TYPE = ASCII_REAL
START_BYTE = 106
BYTES = 9
UNIT = "NANOTESLA"
UNIT_ID = "nT"
DESCRIPTION = "MAGNETIC FIELD Z COMPONENT, CALIBRATED,
TEMPERATURE CORRECTED DATA, 1S_AVERAGE- PCA, CORRELATED DATA,ECLIPJ2000"
END_OBJECT = COLUMN
OBJECT = COLUMN
NAME = "QUALITY_FLAGS"
DATA_TYPE = CHARACTER
START_BYTE = 116
BYTES = 8
DESCRIPTION = "
These flags describe the quality of the magnetic field data.
The quality is coded in a 8 byte string. Each character can have
the following values:
VALUE: MEANING:
x property described by flag is still unknown
0 no disturbance, good quality
1..9 specific disturbance/problems, see below
Description of the specific flags:
FLAG-STRING FLAG DESCRIPTION
87654321
::::::::------ 1 IMPACT OF REACTION WHEELS
::::::: x = impact not assessed
::::::: 0 = no disturbance
::::::: 1 = disturbance eliminated during data analysis
::::::: 2 = disturbance elimination failed
::::::: 3 = data disturbed
:::::::
:::::::------- 2 IMPACT OF LANDER HEATER CURRENTS:
:::::: x = impact not assessed
:::::: 0 = no disturbance
:::::: 1 = disturbance eliminated during data analysis
:::::: 2 = disturbance elimination failed
:::::: 3 = data disturbed
::::::
::::::-------- 3 BOOM DEPLOYMENT:
::::: 0 = boom deployed
::::: 1 = boom stowed
::::: 2 = boom deployment ongoing. Data only valid in
::::: instrument coordinates
::::: 3 = pyros fired for boom release
:::::
:::::--------- 4 OFFSET RELATED EFFECTS:
:::: x = offset issues not assessed
:::: 0 = no offset problems
:::: 1 = offset behavior not clear
:::: 2 = offset drifts, sensor not in thermal
:::: equilibrium thus temperature model N/A
:::: 3 = offset drifts, reason unknown
:::: 4 = ofset jump detected, reason unknown
::::
::::---------- 5 CORRELATION BETWEEN IB AND OB SENSOR
::: x = correlation not assessed
::: 0 = perfect correlation
::: 1 = good correlation
::: 2 = poor correlation
::: 3 = IB and OB show different long term behavior
:::
:::
:::----------- 6 OTHER IMPACTS DECREASING THE QUALITY
:: x = no assessment
:: 0 = no other problems detected
:: 1 = TBD
:: 2 = TBD
:: 3 = TBD
:: 4 = TBD
:: 5 = data disturbed by AC signal originated in s/c
:: 6 = data noisy due to power on failure
:: 7 = data not calculatable due to thermistor failure
:: 8 = sensor saturated due to huge external field
:: 9 = sensor saturated, instrument power on sequence failed
::
::------------ 7 TBD
: x = no assessment
:
:------------- 8 TBD
: x = no assessment
:
"
END_OBJECT = COLUMN
END_OBJECT = TABLE
END
5 Appendix: Available Software to read PDS files
There is no special S/W available to read our PDS files.
6 Appendix: Example of Directory Listing of Data Set X
DATA_SET_ID
�
����DOCUMENT
� ����CALIBRATION
� ����FLIGHT_REPORTS
� ����ARCHIVING
����CALIB
����CATALOG
����INDEX
����DATA
����CALIBRATED
����2005
����MAR
����LEVEL_A
� ����OB
� ����IB
� ����HK
����LEVEL_B
� ����OB
� ����IB
����LEVEL_C
����OB
����IB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\AAREADME.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CATALOG
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DOCUMENT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\ERRATA.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\INDEX
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\VOLDESC.CAT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\CALINFO.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_002_CALIB_IB.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_002_CALIB_IB.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_002_CALIB_OB.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_002_CALIB_OB.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_GND_CALIB_FSDPU_FMIB.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_GND_CALIB_FSDPU_FMIB.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_GND_CALIB_FSDPU_FMOB.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_GND_CALIB_FSDPU_FMOB.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_SC_ALIGN.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CALIB\RPCMAG_SC_ALIGN.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CATALOG\CATINFO.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CATALOG\DATASET.CAT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CATALOG\RPCMAG_INST.CAT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CATALOG\RPCMAG_PERS.CAT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\CATALOG\RPCMAG_SOFTWARE.CAT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050301T0002_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050301T0002_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050302T0000_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050302T0000_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050303T0000_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050303T0000_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050304T0000_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050304T0000_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050305T0000_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050305T0000_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050306T0000_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050306T0000_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050307T0000_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050307T0000_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050329T0932_CLA_HK.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\HK\RPCMAG050329T0932_CLA_HK.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050301T0014_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050301T0014_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050302T0000_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050302T0000_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050303T0000_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050303T0000_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050304T0000_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050304T0000_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050305T0000_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050305T0000_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050306T0000_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050306T0000_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050307T0000_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050307T0000_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050329T0943_CLA_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\IB\RPCMAG050329T0943_CLA_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050301T0014_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050301T0014_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050302T0000_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050302T0000_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050303T0000_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050303T0000_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050304T0000_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050304T0000_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050305T0000_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050305T0000_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050306T0000_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050306T0000_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050307T0000_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050307T0000_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050329T0943_CLA_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_A\OB\RPCMAG050329T0943_CLA_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050301T0014_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050301T0014_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050302T0000_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050302T0000_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050303T0000_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050303T0000_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050304T0000_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050304T0000_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050305T0000_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050305T0000_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050306T0000_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050306T0000_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050307T0000_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050307T0000_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050329T0943_CLB_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\IB\RPCMAG050329T0943_CLB_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050301T0014_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050301T0014_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050302T0000_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050302T0000_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050303T0000_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050303T0000_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050304T0000_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050304T0000_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050305T0000_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050305T0000_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050306T0000_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050306T0000_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050307T0000_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050307T0000_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050329T0943_CLB_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_B\OB\RPCMAG050329T0943_CLB_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050301T0014_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050301T0014_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050302T0000_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050302T0000_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050303T0000_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050303T0000_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050304T0000_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050304T0000_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050305T0000_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050305T0000_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050306T0000_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050306T0000_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050307T0000_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050307T0000_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050329T0943_CLC_IB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\IB\RPCMAG050329T0943_CLC_IB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050301T0014_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050301T0014_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050302T0000_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050302T0000_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050303T0000_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050303T0000_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050304T0000_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050304T0000_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050305T0000_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050305T0000_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050306T0000_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050306T0000_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050307T0000_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050307T0000_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050329T0943_CLC_OB_M2.LBL
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DATA\CALIBRATED\2005\MAR\LEVEL_C\OB\RPCMAG050329T0943_CLC_OB_M2.TAB
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DOCUMENT\ARCHIVING
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DOCUMENT\CALIBRATION
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DOCUMENT\DOCINFO.TXT
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DOCUMENT\FLIGHT_REPORTS
RO-E-RPCMAG-3-EAR1-CALIBRATED-V3.0\DOCUMENT\LOGBOOK_20050301_20050330.ASC
1 The analysis of the Earth Fly-by data resulted in a time shift of 8.3s. The stated 8.2 s is a theoretical value derived from the digital filter design.
??
??
8
RPC-MAG EAICD
Document No.
Issue/Rev. No.
Date
Page
: RO-IGEP-TR0009
: 3.3
: 18 February 2010
: 5
8
ESOC European Space Operations Centre