1. LAT ISOCDOE Status Review, 12 Oct 2004 1 GLAST Large Area Telescope LAT Instrument Science Operations Center Rob Cameron Stanford Linear Accelerator Center rac@slac.stanford.edu 650-926-2989 Gamma-ray Large Area Space Telescope

2. LAT ISOCDOE Status Review, 12 Oct 2004 2 Outline  Overview  ISOC Organization  ISOC Operations  Software Architecture  Operations Facility Planning  Development Schedule  Current Status

3. LAT ISOCDOE Status Review, 12 Oct 2004 3 LAT ISOC in the GLAST GDS Analysis Software

4. LAT ISOCDOE Status Review, 12 Oct 2004 4 LAT ISOC Objectives 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 flight software 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

5. LAT ISOCDOE Status Review, 12 Oct 2004 5 ISOC Reviews  ISOC Peer Review: 2 March 2004  ISOC CDR: 4 August 2004  GLAST GSDR: 18-19 August 2004  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 ISOC-specific RFAs –Ground-system RFAs will be applied to ISOC as needed

6. LAT ISOCDOE Status Review, 12 Oct 2004 6 CDR RFA Status SectionRFA TitleRequestorActioneeECD/Comments Sent to Originator for Review Submitted to Chairpersons Closed 1 ISOC Documentation Tree E. AndrewsL. Bator Response submitted 8/12/04 2 Requirements Traceability Tool E. Andrews B. Craig J. Martin Response submitted 8/27/04 9/07/04 3.1 Add ISOC Architecture Diagram E. AndrewsB. Craig Response submitted 8/16/04 3.4 ISOC Requirements & Testing (Overall) E. AndrewsJ. Martin Response submitted 9/14/04 4.2SAA Handling ApproachN. JohnsonL. Bator Response submitted 8/30/04 4.2 Launch Critical Support Plan M. Rackley J. Leibee S. Culp Awaiting GSFC input 4.2 Red/Yellow Limit Philosophy J. LeibeeL. Bator Awaiting SAI definitions 8 SAS Verification Approach M. RackleyJ. Martin Response submitted 9/14/04

7. LAT ISOCDOE Status Review, 12 Oct 2004 7 ISOC Organization ISOC Manager R Cameron Commanding, Health & Safety Timeline Planning Command Generation Command V&V Health & Safety Configuration Tracking Flight Software Code Maintenance Code V&V Testbed Maintenance Performance V&O Calibration Performance Trending Standard Source Monitoring IRF Generation Science Products Level1 CRs, gammas, diagnostics Level 2 Transients, GRBs Pipeline Operation Science Analysis Tools Simulation/Recon Science Tools Infrastructure DatabaseDocumentation

8. LAT ISOCDOE Status Review, 12 Oct 2004 8 Commanding, Health and Safety  The Commanding, Health and Safety (CHS) team is responsible for: –LAT mission planning support –generation and validation of LAT commands –passing LAT commands to the GSSC –verifying commands were correctly executed –receiving Level 0 data from the MOC –logging and archiving of all commands and Level 0 data –monitoring data to ascertain and track the health and safety of the instrument –continuous knowledge of the configuration of the LAT

9. LAT ISOCDOE Status Review, 12 Oct 2004 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  ITOS provides compatibility with MOC  Other tools –Level 0 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

10. LAT ISOCDOE Status Review, 12 Oct 2004 10 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  FSW team moves into ISOC after FSQ (April 2005) –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

11. LAT ISOCDOE Status Review, 12 Oct 2004 11 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 on-orbit performance of the LAT –management of pre-launch test and calibration data –configuration and maintenance of the LAT reference geometry and the LAT Monte Carlo Model  The basic structure for the PVO team is already in place for LAT I&T activities

12. LAT ISOCDOE Status Review, 12 Oct 2004 12 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  The functions (pipeline etc) used by the Science Products team are developed by the Science Analysis Software team

13. LAT ISOCDOE Status Review, 12 Oct 2004 13 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 high-level diagnostics derived from reconstruction and classification –Development and maintenance of the high-level analysis tools  ISOC will have responsibility for tools used to produce its deliverables

14. LAT ISOCDOE Status Review, 12 Oct 2004 14 ISOC Staffing Plan  ISOC staff will grow mostly by team transfer, plus some new hires

15. LAT ISOCDOE Status Review, 12 Oct 2004 15 ISOC Operations ISOC will be involved in all phases of LAT operation:  LAT I&T –Pre-FSW (EM) –Post-FSW (Flight unit level) –TVAC test at NRL  Observatory I&T at Spectrum Astro  Launch and Early Orbit (L&EO) – Phase 0 –LAT power-on and configuration –Initial checkout and calibration  First year – Phase 1 –Survey mode  Second and subsequent years – Phase 2 –Pointed observations –Survey mode

16. LAT ISOCDOE Status Review, 12 Oct 2004 16 Initial Turn-On and Checkout (Phase 0)  Launch and Early Orbit (L&EO) phase currently scheduled for 60 days  Instrument turn-on 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  Initial calibrations  ISOC will have staff at MOC during L&EO, but data will also flow to west coast ISOC for processing

17. LAT ISOCDOE Status Review, 12 Oct 2004 17 Science Operations (Phases 1 and 2)  Data taking –Continuous –Few commands needed  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

18. LAT ISOCDOE Status Review, 12 Oct 2004 18 Operations Coverage  Weekday, day-time operations –Mission planning, command building –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  Telemetry monitoring and science data processing –Continuous automatic processing  On-call support available 24/7 –Support for targets of opportunity, anomalies –Operators for real-time commanding or anomaly support –Software engineer for emergency software support –Computer technician for computer/network support –Team Lead and Instrument Physicist for anomalies

19. LAT ISOCDOE Status Review, 12 Oct 2004 19 LAT Mission Planning Timeline  Weekly mission planning cycle, with 3 week lead time

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

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

22. LAT ISOCDOE Status Review, 12 Oct 2004 22 Requirements Drive ISOC Design  ISOC requirementstracing is complete  Each ISOC Level 3 requirement was identified as: 1.Procedural (non-software) 42 2.Existing software277 3.Under development by SAS 39 4.To be developed by others (I&T, FSW, ITOS) 21 5.New development needed 88 Total467  Some requirements map to multiple categories or SW tools, so total exceeds total number of Level 3 requirements (379)  Top-down planning and scheduling of new software development is underway

23. LAT ISOCDOE Status Review, 12 Oct 2004 23 ISOC Operations Facility  Working with SLAC management and Facilities group to define near-term ISOC operations facility. Coordinating ISOC space requirements with LAT project management.  Near-term ISOC facility: a new temporary building at SLAC  Long-term ISOC facility: discussions are starting with SLAC and KIPAC management on ISOC facility in new Kavli building at SLAC, available 2006. Also ISOC presence on Stanford campus.

24. LAT ISOCDOE Status Review, 12 Oct 2004 24 Proposed ISOC Layout for 60΄x36΄ Building

25. LAT ISOCDOE Status Review, 12 Oct 2004 25 ISOC Trailer Location

26. LAT ISOCDOE Status Review, 12 Oct 2004 26 SW Dev Slack Times 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/E-logbook Dev Mission Planning Dev Diagnostic Tool Dev End-to-End Tests Ground Readiness Tests ISOC CDR Mar-07Mar-07 Feb-07Feb-07 Jan-07Jan-07 Dec-06Dec-06 Nov-06Nov-06 Oct-06Oct-06 Sep-06Sep-06 Aug-06Aug-06 Jul-06Jul-06 Jun-06Jun-06 May-06May-06 Apr-06Apr-06 Mar-06Mar-06 Feb-06Feb-06 Jan-06Jan-06 Dec-05Dec-05 Nov-05Nov-05 Oct-05Oct-05 Sep-05Sep-05 Aug-05Aug-05 Jul-05Jul-05 Jun-05Jun-05 May-05May-05 Apr-05Apr-05 Mar-05Mar-05 Feb-05Feb-05 Jan-05Jan-05 Dec-04Dec-04 Nov-04Nov-04 Oct-04Oct-04 Sep-04Sep-04Phase / Milestone Aug-04Aug-04 2 34 5 6 7 ITOS setup/configuration 12 3 4 5 6 1 3 2 ISOC ready to take over LAT operation ISOC used to I/F with LAT (front-door only) 4 GSDR

27. LAT ISOCDOE Status Review, 12 Oct 2004 27 Current Status  ISOC team structure and development plan is in place –System development underway –Software releases, GRTs and ETE tests as milestones  ISOC activity is ramping up –ISOC staffing plan is being refined –Recent hires in July, August –CHS software developer starting in November –Test engineer to be hired in 2004 –ISOC facility and infrastructure being developed  Lots of coordination effort needed between various project elements to bring together all the elements of the ISOC –e.g. inter-team meetings, ICDs