European Space Agency

1
European Space Agency
Data Handling of the Rosetta and Mars Express
Projects from Spacecraft Packets to the
Scientific Archive
March 20, 2004
F. Delhaise1, J Zender2, C Arviset3 1-European
Space Agency (ESA), European Space Operations
Centre (ESOC), Germany 2- ESA,European Space
Research and Technology Centre,
Noordwijk,Netherlands 3- VILPSA, Satellite
Tracking Station, ESA, Madrid Spain

2
Contents

• Introduction
• ESA/ESOC Rosetta Mars Express Data Flow from
  S/C to Instrument Teams
• Data flow from Spacecraft to the MOC ,
• Processing of the Mission Data at the MOC,
• Data Flow from the MOC to Instrument Teams via
  the DDS
• ESA/RSSD Rosetta Mars Express Data Flow from
  Instrument Teams to Scientific Community
• The Planetary Missions Science Archive (PSA)
  Development and features
• Data Flow from the Instrument Teams to the entire
  Scientific Community through the PSA

3
Introduction
0
Scientific Community
Science Operations Centre
Mission Operations Centre
PSA
Instrument Team
DDS
1b, 2,3
Lander Science Operations Centre
Lander Control Centre
Level 0 Raw telemetry data as received at the
ground station Level 1a Level 1 data that has
been processed by the MCS and DDS Level 1b Data
in scientific useful format, e.g. as images or
spectra. This data is still uncalibrated Level 2
3 Level 1b with calibration and corrections
applied to yield to scientific units provided by
instrument teams for the whole scientific
community and general public
4
Overview Rosetta/MEX Downlink from S/C to
Instrument Teams
ESOC MOC
N C T R S
Relay LAN
Operational LAN
Deep Space Antenna (New Norcia)
TM
TM/AUX data
Requests
TM
DDS
MCS
Archive
Data
FDS
Firewall
Firewall
Components of the Downlink Part of the Data Flow
from S/C to Instrument Teams NCTRS Interface
software between ground station and the MCS MCS
(Archive system)It is based on the ESOC
SCOS-2000 infrastructure. It provides the
capability to process HK data in real-time for
spacecraft control purposes. FDS Flight
Dynamics System provides Orbital Attitude
Data DDS It allows remote access by the
Instrument Teams for the near-real-time and/or
offline inspection of mission data
5
Data flow from S/C to MOC

• Ground Station from Spacecraft to Earth
• Cleaned from transmission error,
• Time-stamped with Earth Reception Time
• NCTRS from Ground Station to the MOC
• generic infrastructure system,
• performs the ground-station interface with the
  MCS,
• Forward the telemetry to the MCS ensuring online
  completeconnection from ground station to the
  MOC (it offers many other connection services
  than online complete)

6
Data Processing at the MOC

• MCS Telemetry is processed in real time at the
  level required for S/C monitoring and commanding
  i.e.
• conversion from OBT to UTC for each telemetry
  frame packet
• Retrieve parameter values from telemetry packets
• Calibrate TM parameters to engineering values via
  pre-defined calibration curve
• Out of limit, status consistency check of
  parameters is computed
• FDS A lot of Auxiliary data is generated
• S/C orbital position and attitude
• Orbit events file (station visibility etc)
• Mission Planning files
• Provides TC history files
• Time Correlation Packets
• ? Entire mission data is archived for 10 years
  and available through the DDS

7
Reception of Data via the DDS

• Nominal way to distribute the raw data from ESOC
  to Instrument Teams
• Via the Automatic Push Mechanism
• Pre-configured at ESOC (with help of PIs)
• Permanent request
• Frequency Daily basis
• Data TM, TC and Aux Flight Dyn Files for the
  given period
• Error messages reported via Web Page - Log
  extraction
• Up to 6 re-tries
• Via CD-Roms (applicable only to Mars Express)
• Pre-configured at ESOC CDs all mission data
  per day (defined by OBT)
• Frequency daily basis
• Use the SFDU formatting self-contained,
  self-descriptive

8
Retrieval of Data via the DDS

• During critical mission phases and in contingency
  cases like
• commissioning
• Failure in automatic push mechanism (in Routine)
• Special data requests
• Send an ascii request in XML format via FTP
• Use a XML validation tool before sending the
  request
• One request per ADID (APID) or one request per
  SUPER-APID
• Data is returned via FTP to a pre-defined
  hostname as one single file
• Build your request via the WEB interface
• Data is returned via FTP or HTTP

9
Data flow from MOC to Instrument Teams via the DDS
OPS LAN
RELAY LAN
DDS Operator
AUTHORIZED USERS

• Requests
• Web interface
• XML file via ftp
• Standing order

MCS
DDS
Send requests

• Archive(TM, TC,AUX File

• GDDS

• Web Browser
• FTP
• RDM reader

Deliver data

• Delivery
• Web interface
• file via ftp
• CD-ROM

RDM Production
Firewall
10
Format of Returned TM Raw Data via DDS

• Time ascending order based on source pkts gen
  time (OBT converted to UTC SCET)
• with a fixed length DDS Header
• SCET OBT converted UTC using Time Calibration
• Packet length, G/S ID, VC ID (0 VC0, 1 VC1)
• SLE service (RT, RTFC, off-line)
• Time Quality
• Good OBT is valid
• Inaccurate OBT invalid gt SCETERTprop delay
  (VC0)
• Bad OBT invalid gt SCETERTprop delay (VC1)

DDS header
Complete experiment raw packets
11
Format of Returned TC Raw Data via DDS

• TC Raw Data
• Time ascending order based on uplink / execution
  time
• with a fixed length DDS Header
• uplink / execution time
• Flags CUVUplink, CAVAccepted,
  CEVExecutiongtbased on VC0
• Flags CAVAccepted, CEVExecution gt based on
  VC1 TM
• Packet length, CMD ID and Parent SEQ ID
• TC History Brief Print readable ascii file
• ASCII file with 1 header line
• TC History Full Print
• ASCII file with 1 header line
• contains parameters data associated to each CMD

Header
Encoded Command Data
12
Data Flow from Instrument Teams to the Scientific
Community

• through the Planetary Science Archive
• ESA has the need for a Common Archive for ALL
  Planetary Missions accessible from the scientific
  community and the general public
• PSA Working Group is founded in 2002 mission
  independent scientific people from all
  disciplines to define PSA requirements
• PSA Major objective to increase and ease the
  scientific return of the mission data

13
ESA PSA Requirements

• PSA Requirements
• All ESA Planetary Missions Data into a single
  archive accessible from a single interface
• Giotto, Mars Express, Smart-1, Rosetta, Huyghens,
  Venus Express,
• Reduce Cost,
• Single interface for of all engineering,
  housekeeping and scientific data for all the
  science community,
• Compliant with PDS standard for all ESAs
  planetary missions
• Development of the PSA Archive in 2002-2003 based
  on existing ISO and XMM-Newton scientific data
  archive architecture
• cost reduction,
• well proven architecture

14
ESA PSA Features

• online archive allowing data search and access
  via the public internet
• offers additional data services on top of the
  PDS-compliant data sets (search, notification
  data service, shopping basket)
• aimed to support several user groups
• standard users full access to all public data
• expert users access data which is restricted
  (proprietary period)
• General public interested in simple queries
  (easy-to-interpret)
• electronic data ingestion and validation from the
  experimenter teams

15
ESA PSA Features

• Major objective to increase and ease the
  scientific return of the mission data, is reached
  by
• Central organization and long-term preservation
  of all data
• Easy access and search functionality
• Single entry place for all ESAs planetary
  missions
• PDS compliance
• Interoperability to other planetary archives
  (the design of the PSA is made such that it is
  possible for other Archive systems (located
  anywhere in the world) to automatically retrieve
  product data from the PSA via a JAVA software
  interface )
• Automatic ingestion and validation support (under
  development

16
ESA Planetary Missions Science Archive MMI
Query Panel
Results Panel
17
Archive Process from Instrument teams to the
general public through PSA
Launch
Mission Phase Start
Main actors
Archive Phases
Experimenter Team PSA consultancy
Archive Design
Data Collection
Experimenter Team
Experimenter Team
Data Preparation
PSA Team experimenterand external scientists
PSA Validation
Scientific Community
PSA Accessibility
Archive Plan
1st Ingestion
2ndIngestion
EAICD
Peer Review
Archive Phase Definitions and Delivery Schedule.
Left column gives the archives phases the lines
to the right of each archive phase indiate the
time axis. Right colum gives the main actors of
each archive phase.
18
Conclusion

• Data flow and data integrity from the Rosetta
  and Mars Express S/C to the scientific community
  general public has been fully described
• DDS is used operationally since June 2003 for
  MEX and has been successfully validated for
  Rosetta
• The ESA PSA will contain all ESA Planetary
  Missions Data (incl. Mars Express, Rosetta). -
  PSA V1.0 to be release 1st quarter 2004