ESA Ground Segment - Krieger Web Services · Science Operations Centre ATEL Data Processing Centre...

ESA UNCLASSIFIED - For Official Use

ESA Ground Segment

Paul McNamara (for Uwe Lammers)Joint NLST/SST meetingBaltimore, August 2018


European Space Agency

e

Joint SST/NLST | 27-29/08/2018 | Slide

Science Ground Segment (SGS)

�2

The Science Ground Segment of LISA consists of:- Mission Operations Centre (MOC)- Science Operations Centre (SOC)- Consortium Data Processing Centre (DPC)- Data Computing Centres (DCC)

Relevant Documents:- Science Operations Assumptions Document (SOAD)

- End April- Science Management Plan (SMP)

- Phase B1- Science Implementation Requirements Document

(SIRD)- Science Implementation Plans (SIPs)

S/C

GroundStations

MOC

SOC

Uplink

Downlink

Events handling

ATEL

Users

DPC

Science Operations Ground Segment

Mission Operations Ground Segment

Table caption :

Event Notice

PreliminaryEventNotices

Ops request

Telecommands

Telecommands Telemetry

Telemetry

Raw & L0

L1L2

& L3

Data products

IOT L0

Ops requests

Calibrationfiles



e


Mission Operations Centre (MOC)

�3

The role of the MOC is to “fly” the satellites- They are responsible for all telecommands sent to the satellites, be it for spacecraft or instrument controlMOC are also responsible for collecting and consolidating the full telemetry streamConsolidated telemetry is made available to the SOC ~2 hours after the end of the ground station pass- We will work with the MOC to try to minimise this delay

- By 2034, the Mission Control System should be more advanced than it is today!

During the commissioning, calibration and early operations, the SOC and Instrument Operations Teams will be located at the MOC- Same as was done for LPF, which proved to be essential in

the success of the mission

MOC is located at ESOC in Darmstadt, Germany



e


Science Operations Centre (SOC)

�4

The Science Operations Centre’s role is to operate the science instrumentDuring nominal and extended operations, the SOC is the single point of contact between the Consortium/science community and LISA The role of the SOC is to ensure the optimal operation of the instrument, including any routine calibration activities- e.g. LPF science operations-like activitiesThe SOC is also responsible for the delivery of all data from the constellation to the DPC and eventually science community

The SOC is located at ESAC in Madrid, Spain



e


Science Operations Ground Segment elements

�5

MOC

Science Operations Centre

ATEL

Data Processing Centre

Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

UsersUser Support

Instruments Operations

TeamsArchive

DCC DCC

DCC DCC



e


LISA Science Operations Ground Segment - Uplink

�6

MOC


ATEL


Operational requests

Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

Users

Instruments & Calibration Ops requests

User Support


TeamsArchive

SOC unique point of contactwith MOC for uplink

DCC DCC

DCC DCC



e


SOGS : Downlink

�7

MOC


ATEL


Raw & Level 0 data

L1 data L2 & L3 data

Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

Users

Calibration files

User Support


Teams

L0 data

Archive

L1 data

L0 data


SOC unique point of contactwith MOC for downlink

DCC DCC

DCC DCC



e


LISA SOGS : Data distribution

�8

MOC


ATEL


Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

Users

Data products (L1, L2, L3)

User Support

Questions & answers


TeamsArchive

SOC responsible fordistribution of dataproducts

DCC DCC

DCC DCC



e


LISA SOGS : Transient Events

�9

MOC


ATEL


Event Notices

Preliminary Event Notices

Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

UsersUser Support


TeamsArchive

SOC responsible forsending Event Notices

DCC DCC

DCC DCC



e


LISA SOGS : Archive

�10

MOC


ATEL


Raw & Level 0 data


Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

UsersUser Support


Teams

L0 data

Archive

SOC Operational Archiveconnecting all Ground Segment actors

SOC Legacy Archivecontinuation of SOCOperational Archive

Data products (L1, L2, L3)

DCC DCC

DCC DCC



e


LISA SOGS : All interfaces

�11

MOC


ATEL


Event Notices

Preliminary Event Notices

Operational requests

Raw & Level 0 data


Transient Events

Consolidation

Science Planning

Team

Data Processing

Team

Users


Calibration files

User Support

Questions & answers


Teams

L0 data

Archive

L1 data

L0 data Data products (L1, L2, L3)

DCC DCC

DCC DCC



e


Data levels

�12

Currently we foresee the following levels of data:- Level 0: Raw data, in engineering format, from the satellite

- i.e. the data delivered from MOC to SOC- Level 1: Data has been “cleaned” and TDI algorithm has been implemented

- Data cleaning and TDI will be agreed and jointly developed with the DPC- Level 1 data will be available to the science community from the archive after the proprietary period

- Level 2: GW source parameter estimation with residuals- DPC produce Level 2 data- Level 2 data only makes sense in the case of separate source identification pipelines

- Does not make sense if global fit is employed by DPC- Level 3: GW source catalogue

- DPC produce Level 3 data



e


Mission Phases

�13

Study Phase

Development

LEOP + Cruise

Commissioning

Calibration and Performance Verification Phase

Science Phase (Nominal and Extended)

Post Ops

→Adoption

→Launch

→IOCR

→End of Operations

→End of Mission

Responsibility in ESA

SCI-F (ESTEC)

SCI-P (ESTEC)

SCI-O (ESAC)



e


During the Development Phase

�14

Principle of “smooth transition”- To use the same tools as during the operational phase (e.g. Archive, Data processing, payload monitoring tools)

Ground Segment Tests- System Operations Validation Tests (SOVTs) campaign involving all actors (ESOC, SOC, IOT, DPC and Project)- 13 SOVTs for LPF (with increasing complexity)

Building up of the IOT- The Instrument Operations Team will need to start preparing for operations before all the Payload HW is delivered (e.g. tools

and procedures for payload monitoring and calibration)



e


During the Commissioning Phase

�15

Instrument Teams at ESOC

Instrument Teams have direct interface with MOC for Uplink (via Project)

Manual commanding to the S/C

SOC is operational and provides Telemetry to Instrument Teams



e


During the Calib. & Performance Verification Phase

�16

Interfaces identical to the Nominal Science Phase

Instrument Teams and SOC at ESOC

Timeline driven operations

Calibration: to find the optimum setup for all satellite operations

Performance Verification: to use the observatory as during the Nominal Science Phase to confirm overall system is ready



e


During the Nominal Science Phase

�17

Instrument Teams and SOC relocated at home institutes and ESAC respectively, with regular meetings

In case of anomalies :- Instrument Teams support called as needed-Commissioning/CPV setup can be required

Transient Events : when generation of the “Preliminary Event Notices” is stable enough, it could be run in the SOC to decrease turn-around time

Data Re-processing-Regeneration of TDI’d data (L1)-This is expected to take place several times, requiring all data analysis to be re-run!



e


During the Post Operational Phase

�18

Generation of the ultimate payload calibration for final re-processing

Generation of the ultimate data products for Legacy Archive

ESA Ground Segment - Krieger Web Services · Science Operations Centre ATEL Data Processing Centre...

Documents

Transcript of ESA Ground Segment - Krieger Web Services · Science Operations Centre ATEL Data Processing Centre...