GLAST Large Area Telescope

Transcription

1 Gammaray Large Area Space Telescope GLAST Large Area Telescope LAT Instrument Science Operations Center Rob Cameron Stanford Linear Accelerator Center

2 Outline Overview ISOC Organization Commanding, Health and Safety Flight Software Performance Verification and Optimization Science Products Science Analysis Tools Operations Scenarios Software Architecture and Tools Operations Facility Planning Development Schedule 2

3 LAT ISOC GLAST LAT Collaboration Meeting, 29 Sept 24 LAT ISOC s Role in the GLAST GDS Analysis Software 3

4 LAT ISOC Objectives The LAT ISOC is organized to: safely operate the instrument produce the LAT science data products Functions: Command generation; health and safety monitoring Maintain and modify FSW and Testbed LAT performance verification and optimization Process and archive Level 1 and Level 2 data Maintain and optimize the software pipeline that produces science data products These functions are organized as teams that share personnel 4

5 ISOC Reviews ISOC Peer Review: 2 March 24 ISOC CDR: 4 August 24 GLAST GSDR: 1819 August 24 CDR: very successful review 8 RFAs and 8 Recommendations received 6 RFA responses submitted for review, others in work All recommendations completed GSDR: very successful review No ISOCspecific RFAs Groundsystem RFAs will be applied to ISOC as needed 5

6 ISOC Organization ISOC Manager R Cameron Database Documentation Commanding, Health & Safety Flight Software Performance V&O Science Products Science Analysis Tools Timeline Planning Code Maintenance Calibration Level1 CRs, gammas, diagnostics Simulation/Recon Command Generation Code V&V Performance Trending Level 2 Transients, GRBs Science Tools Command V&V Testbed Maintenance Standard Source Monitoring Pipeline Operation Infrastructure Health & Safety IRF Generation Configuration Tracking 6

7 LAT ISOC Architecture R/T HK & Cmd Mission Operations Center HSK Level Data GLAST Science Support Center Command & Science Planning Data Processing Level 1 & Level 2 Commanding, Health & Safety Performance Verification Instrument Response Command validation Flight Software & Testbed Instrument Optimization Calibrations Science Analysis Software LAT ISOC Steering Committee Data Transfer Reports and Information Support Functions Through Deliverables Advisory and/or Revision Role LAT Science Analysis 7

8 Commanding, Health and Safety The Commanding, Health and Safety (CHS) team is responsible for: generation and validation of commands and command sequences, passing LAT commands to the GSSC, verifying these commands were executed, receiving Level data from the MOC, logging and archiving of all commands and Level data, monitoring data to ascertain and track the health and safety of the instrument, continuous knowledge of the configuration of the LAT. 8

9 CHS System ITOS used for command, health and safety functions HK data limit checking Telemetry and command definition file validation Command load verification and validation Other tools Level receipt and archiving HK trending Data transmission Mission planning and generation of file uploads Anomaly tracking and notification Relational database queries for trending and analysis Configuration management tools 9

10 CHS Team Instrument Physicist: Mission planning, telemetry review Software Engineer: Maintain CHS software, T&C database CM Instrument Operators: Command build, telemetry monitoring Weekday, daytime operations Operator shift coverage 5 am to 2 pm to cover MOC shift times on East Coast 9 am to 6 pm to cover ISOC internal coordination needs Oncall support Operators for realtime commanding or anomaly support Software engineer for emergency software support Team Lead and Instrument Physicist for anomalies 1

11 Flight Software The Flight Software (FSW) team is responsible for: Updating and validation of all flight software files Debug or problem fixes to the FSW Implementation, and validation on the instrument test bed of authorized upgrades to FSW Continuing maintenance of the instrument testbed to ensure it is available to validate code and command sequences as well as to investigate any anomalies seen on orbit 11

12 FSW and ISOC Interactions Before FSQ (in April 25) Coding the software that will operate the LAT Testing the software Configuration management Development of Test Bed After FSQ Continue code/test/cm cycle as part of the ISOC operations Maintenance of Test Bed Review commanding, HK, and performance on a frequent and regular basis 12

13 Performance Verification and Optimization The Performance Validation and Optimization (PVO) team is responsible for: instrument calibration from low level through to IRFs continuous monitoring of the LAT science performance, identification of instrument performance trends and resolution of performance anomalies generation of performance reports generation and initial validation of algorithms that improve onorbit performance of the LAT management of prelaunch test and calibration data configuration and maintenance of the LAT reference geometry and the LAT Monte Carlo Model The basic infrastructure for the PVO team is in place for LAT I&T activities and is the basis for the ISOC implementation 13

14 Science Products The Science Products Team is responsible for Generation, archiving and distribution of the Level 1 data Generation, archiving and distribution of specific Level 2 data needed for transient source detection and GRB parameter determination Configuration control of the pipeline and generated data sets The functions developed by the Science Analysis Software (SAS) subsystem of the LAT are leveraged by the Science Products team to provide deliverables for ISOC 14

15 Science Analysis Software The Science Analysis Software Team is responsible for Development and maintenance of the pipeline machinery Development and maintenance of the simulation, reconstruction and event classification software Development and maintenance of the calibration algorithms, including low level cal and Instrument Response Function generation Development and maintenance of the quicklook transient analysis tools Development and maintenance of the highlevel diagnostics derived from reconstruction and classification Development and maintenance of the highlevel analysis tools 15

16 LAT Operations Planning 16

17 LAT Operations Phases ISOC will be involved in all phases of LAT operation: LAT I&T PreFSW (EM) PostFSW (Flight unit level) TVAC test at NRL Observatory I&T Spectrum Launch and Early Orbit (L&EO) Phase LAT poweron and configuration Initial checkout First year Phase 1 Survey mode Second and subsequent years Phase 2 Pointed observations Survey mode 17

18 Initial TurnOn and Checkout (Phase ) Launch and Early Orbit (L&EO) phase currently scheduled for 6 days Turnon (powerup) procedure will not be executed automatically Humans required to check environmental conditions prior to significant steps Must establish correct LAT configuration at each step Functional checkout of DAQ, ACD, CAL and TKR Perform initial calibrations Support special requirements E.g. monitor phototube high voltages in ACD during turnon ISOC will have presence at MOC during L&EO, but data will also flow to west coast ISOC for processing 18

19 Science Operations (Phases 1 and 2) Data taking Continuous A few commands to initiate Calibration Weekly, biweekly and monthly A few commands to initiate Load changes to tables and FSW Infrequent A few commands and/or file uploads which may be large Load new tables and files Infrequent A few commands and/or file uploads which may be large Perform Diagnostics Infrequent A few commands and/or file uploads which may be large SAA management FSW turns down high voltage automatically based on SAA message from S/C 19

20 Science Planning Phase /1: ISOC maintains LAT science observation plan Organization of the scientific activities of the LAT collaboration outside of the ISOC is being defined Steering Committee, with Collaboration and Project Scientist representation, will oversee LAT operations planning and serve as the interface between science and operations Acceptance of updated algorithms for the LAT trigger or event filtering (onboard or ground) Definitions of conditions when the LAT will autonomously request a repointed observation Phase 2: GSSC generates Long Term Science Schedule GSSC assists in overall science schedule evaluation and will manage the guest investigator proposal process Coordinated with LAT collaboration Input to LAT Planning 2

21 LAT Timeline Contains all LAT commanding information to fulfill a oneweek period of the Operations Plan Commands for Absolute Time Sequence (ATS) File loads Table uploads Configuration changes FSW loads Command procedures Commands requested to be sent in realtime Generated by CHS team about 2 weeks before upload Coordinated with GSSC, MOC and GBM through weekly planning meetings Validated and verified on testbed 21

22 LAT Operations Planning Timeline Monday Tuesday Wednesday Thursday Friday Saturday Sunday July 3 31 August GSSC Sends Preliminary Activity Timeline to MOC MOC Requests TDRSS Contacts for the Week ISOC Generates Command Plan ISOC Sends Command Plan to GSSC Deadline for ISOC to Send Changes* to Week GSSC Sends Final Activity Timeline to MOC MOC Uploads ATS ATS Goes Active September 1 2 *Minor changes that don t affect observing schedule or TDRS contacts 22

23 Software Architecture and Tools 23

24 Primary Data Flows LAT ISOC MOC Level Data, LAT Alerts, Integrated Observ. Timeline, Spacecraft Timeline, AsFlown Timeline, Flight Dynamics Products, SC Incident Reports, PDB updates Anomaly Tracking & Notification System Receive & Archive GSSC Receive & Archive Prelim. Science Timeline, Long Term Science Schedule, Observ. Timeline Package Integrated Observ. Timeline, Spacecraft Timeline, AsFlown Timeline, Flight Dynamics Products Alerts, Logs, Process status, File status Level Sci Data Level Hkpg Data, LAT Alerts Commands to Verify Science Data Analysis Pipeline CHS monitoring & trending Mission Planning LAT Test Bed Tested OK Level 1&2 Sci Data Products LAT Timeline Database Archive & Send Archive & Send All data into ISOC, and products out Level 1&2 Sci Data Products, LAT Timeline GSSC Contingency: LAT Instrument Commands, LAT Instrument Loads, MOC LAT Incident Reports, LAT T&C Database Updates Web Access 24

25 Automatic Telemetry Processing Science Data Analysis Pipeline LAT ISOC MOC Level sci & hkpg telemetry, LAT Alerts GINO & FastCopy/DTS Receive & Archive Level science telemetry Subsystemlevel monitor Calibration Trending Apply Calibration Level 1 processing Reconstruction GCN Calib. DB Systemlevel Monitor Level 2 processing Transient Search/ GRB Refinement GINO & FastCopy/DTS Archive & Send Level 1 & 2 data products GSSC Realtime Level hkpg telemetry (during contacts), LAT Alerts Level hkpg telemetry, LAT Alerts ITOS Monitor hkpg parameters Text & Stripchart displays (optional) Alerts, Logs, Process status, File status FASAT Reports, Log entries, Data Products received and sent Monitor Data ITOS Monitor Trends Anomaly Tracking & Notification System Database STOL Config monitor scripts Beeper / message Beeper / message 25

26 Command Load Generation & Verification LAT ISOC (new) LAT Timeline Generate Command Load & Perform Constraint Checking GSSC Verified OK STOL commands ITOS Issue Commands & Receive Telemetry Command log, Error log and optional Text/Stripchart displays CCSDS Commands telemetry LAT Test Bed 26

27 ISOC Requirements Mapped to Software ISOC requirements tracing is complete Each ISOC Level 3 requirement was identified as: 1. Procedural (nonsoftware) Existing software (commercial or other wellestablished software i.e. implementation Done!) Under development by SAS (mostly done, refer to SAS for status) To be developed by others (I&T, FSW, ITOS) Remaining new development 88 total 467 Some requirements map to multiple categories or SW tools, so total exceeds total number of Level 3 requirements (379) 27

28 2. Existing software Name Description # Level 3 Reqts % of Reqts Source ITOS satellite C&T package % GSFC ATNS Anomaly Tracking and Notification System % FASAT (commercial) or RXTE SOF Process Mgr (RXTE) FastCopy secure file transfer % FastCopy (commercial) CVS file config mgmt tool 5 1.1% Open Source STK Satellite Tool Kit 4.9% commercial LATDocs LAT documentation management tool 4.9% existing SLAC LAT tool NTP synchronize computers 1.2% Open Source electronic mail 1.2% Open Source Total % 28

29 5. Remaining to be developed Tool Name Description # Level 3 Reqts % of Reqts Comments PLOTTOOL plotting 28 6.% combination of existing tools (e.g. ROOT, HippoDraw, JAS, IDL) & new dev TRENDTOOL trending % combination of IDL, DTAS (used by MOC), and/or TAPS (GSFC) PLANTOOL mission planning 6 1.3% generate timeline and commands for LAT operation CONSTRAINT TOOL check command sequences against constraints % DB database definition and implementation 1 2.1% partially done by SAS, I&T, FSW coordinating dev with SAS, I&T, FSW, SCS DBIN ingest ISOC data 7 1.5% WEBTOOL provide web access to data products 9 1.9% Total % 29

30 ISOC Network Architecture SLAC Internet LAT ISOC Web Server Firewall SCS CPU Farm SCS Storage Farm SAS/SP Workstations PVO Workstations FSW Workstations CHS Workstations Linux PC (HK Replay ITOS) Linux PC (Realtime connection ITOS) Gateway System (Oracle, GINO, FastCopy/DTS) Firewall Firewall Abilene Network MOC GSSC Solaris Workstation (VxWorks tools) LAT Test Bed 1553 LVDS SIIS (S/C Sim) Linux PC (Test Bed ITOS) LAT Test Bed Lab Anomaly Tracking & Notification System 3

31 ISOC Operations Facility Working with SLAC management and Facilities group to define nearterm ISOC operations facility. Coordinating ISOC space requirements with LAT project management. Nearterm ISOC facility: a new temporary building at SLAC Longterm ISOC facility: discussions are starting with SLAC and KIPAC management on possible ISOC facility in new Kavli building at SLAC. Also ISOC presence on Stanford campus. 31

32 Proposed ISOC Layout for 6 x36 x36 Building 11'" 59'6" 25'" Operations Center Viewing wiindow Glass doors or glass windows in doors Cipher locked Glass window in door Glass window in door No window (wall for projection screen) 14'6" 32

33 33 SW Dev Slack Times ISOC Development Schedule ISOC Development Schedule Launch Mission Simulations ISOC testing at NRL Environmental tests at NRL ISOC SW Releases ISOC Simulation Testing ISOC Demos ISOC Verif. with Test Bed Plotting/Trending Dev DB/Web/Elogbook Dev Mission Planning Dev Diagnostic Tool Dev EndtoEnd Tests Ground Readiness Tests ISOC CDR M a r 7 F e b 7 J a n 7 D e c 6 N o v 6 O c t 6 S e p 6 A u g 6 J u l 6 J u n 6 M a y 6 A p r 6 M a r 6 F e b 6 J a n 6 D e c 5 N o v 5 O c t 5 S e p 5 A u g 5 J u l 5 J u n 5 M a y 5 A p r 5 M a r 5 F e b 5 J a n 5 D e c 4 N o v 4 O c t 4 S e p 4 Phase / Milestone A u g ITOS setup/configuration ISOC ready to take over LAT operation ISOC used to I/F with LAT (frontdoor only) 4 GSDR

34 ISOC Software Release Schedule The ISOC software release schedule has been coordinated with GSFC Ground System plans: ISOC Software Release 1 (April 1, 25) Support Ground Readiness Test (GRT) 2 and 3 ISOC Software Release 2 (August 15, 25) Support GRT 4 and 5 ISOC Software Release 3 (December 15, 25) Support EndtoEnd 1, ETE 2, ETE 3, GRT 6, GRT 7, and Mission Sim ISOC Software Release 4 (July 25, 26) Support remaining ETE s 4, 5, and 6 34

35 Summary ISOC development activity is ramping up A well defined ISOC organization and development plan is in place, with software releases, GRTs and ETE tests as milestones Lots of coordination effort needed between various project elements internal and external to LAT, to bring together all the elements of the ISOC 35