170 likes | 589 Views
LPF Science Ground Segment. Paul McNamara LTP Data Analysis Meeting 19/20 February 2007. Summary. Introduction Operations Mission Timeline Ground Segment Overview Science Ops Ground Segment. Introduction . Missions within ESA have two “sides” Project (SCI-P) Science (SCI-S)
E N D
LPF Science Ground Segment Paul McNamara LTP Data Analysis Meeting 19/20 February 2007
Summary • Introduction • Operations Mission Timeline • Ground Segment Overview • Science Ops Ground Segment
Introduction • Missions within ESA have two “sides” • Project (SCI-P) • Science (SCI-S) • SCI-P manages the project up to, and through, on-orbit commissioning • SCI-S takes control of the mission after commissioning, i.e. when instrument enters Science Phase • LPF Science Operations will be run through the Science and Technology Operations Center (STOC) • This will be managed by the Mission Manager/Project Scientist • The STOC is part of RSSD within ESA, and located at ESAC, Spain • Mission Operations (s/c health and safety, ground stations etc) are managed by ESOC
Operations Mission Timeline T = L + 0 L + 16d L + 50d L + 66d L + 94d L + 184d L + 244d LTP Ops DRS Ops ??? Despin Orbit Corr IOOP SCIENCE OPERATIONS Transfer Phase Commiss- ioning LEOP Launch Separation Project STOC LEOP = Launch and Early Orbit Phase (apogee raising) IOOP = In-Orbit Operational Phase (Science Operations)
Ground Segment Overview • The LPF Ground Segment consists of 3 parts: • The Operational Ground Segment (OGS) • The Science Ground Segment (SGS) • The interface to the Satellite Prime Contractor (Astrium UK) • The major tasks of the OGS is to perform satellite (payload and s/c) operations ensuring safety of the mission. It comprises: • The Ground Stations • The Mission Operations Centre (MOC) at ESOC • The Operational Ground Segment details can be found in the Ground Segment Management Plan (S2-EST-PL-5101)
Interface with Prime (ASU) • The Prime Contractor will interface with LPF to: • Provide OGS, during Phase C/D, the required deliveries called for in the MIP • e.g. Satellite User Manual (SUM) • Support system validation and listen-in tests as required • Provide the SGS, during Phase C/D, with the required deliveries and specialist support concerning the DFACS • Provide Support during launch and satellite (s/c and payload) commissioning • Receive On-Board Software (OBSW) maintenance requests from MOC and/or STOC and provide MOC with end-to-end validated images/patches/ On-Board Control Procedures (OBCPs) to be uploaded to the satellite.
Science Ground Segment • The major task of the SGS is to plan the utilisation and related configuration of the technology instruments on-board LPF, and derive from the mission products the science and technology results. • The SGS consists: • The Science and Technology Operations Centre (STOC) • Establish and maintain the Experiment Master Plan (EMP) • Derive from the EMP the run procedures • Perform monitoring of the technology instruments and DFACS during all phases of the mission • Perform Quick-look data analysis of the ICE telemetry • Perform full data analysis to extract science and technology results • Update TC parameters • Instigate branching of EMP in event of unexpected result • Archive all available data for later availability (i.e. as reference for LISA) • The LTP Contributors
Science Operations Ground Segment Ground Stations LISA Pathfinder Mission Operations Centre (LPF MOC) -OBSM -OBCP Firewall Mission Operations Center / DDS/ MUST (ESOC) • - Mission planning • requests • Short and long term planning requests • -Updated • TC parameter Firewall • Raw HK and s/c TM • Processed HK TM • -Command timeline • -Auxiliary data • DRS specific TM • LTP raw data O/B S/W change requests STOC (Incl Archive) LPF Prime Contractor -Mission planning requests -Mission planning requests LTP Co-Is DRS Raw and engineering payload and s/c data Raw and engineering payload and s/c data Internet
Science Ground Segment • STOC, LTP Contributors and the DRS can have access to data directly from ESOC • Only authorised data is available to each user • i.e. DRS will not have access to all LTP data • However, plan is for all users to access data through STOC • STOC will provide data in Engineering values • STOC provides single point of contact between Science Community and the MOC • Data analysis tools will be run within the STOC • One set of tools will be treated as the Golden Standard • STOC tools will be under Configuration Control • LTP Contributors are at liberty (encouraged) to analyse the data, either with own tool set, or using a copy of the STOC tools. • Data analysis algorithms must be verified prior to launch
Science Ground Segment • Experimental Master Plan written by STOC with input from Science Team • Will be extended to include details of specific procedures (i.e. discharging of proof mass) • Industrial Procedures will be written by Astrium • The building blocks of the experimental runs • Run Procedures written by LTP Team and validated by STOC with LTP/LPF simulator • Satellite database compiled by Astrium UK • Telecommands will be generated and validated by ESOC • Run procedure will look something like D1[t1s,x1W, y1s], D2[t2s,x2W, y2s], T1[t3,23o], ……
Location of STOC • STOC is being developed in ESAC, Madrid • During s/c commissioning and nominal operations, STOC will relocate to ESOC, Darmstadt • Allows faster access to mission planners, Satellite Operations Manager (SOM), etc • Nominal operations being treated as a payload commissioning phase • After nominal ops (during station keeping), STOC relocates back to ESAC! • ALL further science operations (DRS and extended mission) will be run from ESAC
Science Ground Segment • Science Ground Segment described in more detail in the Science Operations Scenario Document (S2-EST-PL-5005), Science Implementation Plan (LPF-PL-ESAC-DT-001), and Science Ground Segment Design Description (LPF-ESAC-DT-002) • Science Operations Ground Segment to be fully setup by GS-DPDR (2nd Quarter 2007)
LTP Contributors Role • During development, the LTP Contributors (LTP-C) will be involved in defining the procedures for the hardware they have developed and built • The LPF Science Team will also be involved in the creation of the Experiment Master Plan • During operations, the LTP-C are required to support the commissioning of their hardware (as defined in the MLA) • The LTP-C will also be involved in the analysis and particularly the interpretation of the data