1 / 27

GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 5

Gamma-ray Large Area Space Telescope. GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 5 Software Architecture Steve Culp SLAC sculp@slac.stanford.edu 650-926-8987. Agenda. Requirements Mapped to Software Software Architecture

odin
Download Presentation

GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 5

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gamma-ray Large Area Space Telescope GLAST Large Area Telescope: Instrument Science Operations CenterCDR Section 5 Software Architecture Steve Culp SLAC sculp@slac.stanford.edu 650-926-8987

  2. Agenda • Requirements Mapped to Software • Software Architecture • Development and Testing Schedule • Staffing Level (ROM) • Demo

  3. Requirements Mapped to Software • Reviewed all ISOC level III requirements • Identified which required software • Identified existing tools which satisfied all or part of reqt • Identified where new development needed

  4. Requirements breakdown • Each requirement was identified as: • Procedural (non-software) 42 • Existing software (commercial or other well-established software -- i.e. implementation Done!) 277 • Under development by SAS(mostly done, refer to SAS for status) 39 • To be developed by others (I&T, FSW, ITOS) 21 • Remaining new development 88 total 467 • Some requirements map to multiple categories or SW tools, so total exceeds total number of level IIIs (379)

  5. 1. Procedural(no SW development)

  6. 2. Existing software

  7. 3. Under Development by SAS

  8. 4. To be developed by others

  9. 5. Remaining to be developed

  10. Software Architecture

  11. Primary Software Data Flows LAT ISOC Level 1&2 Sci Data Products, LAT Science Activity Timeline, LAT Instrument Commands, LAT Instrument Loads Level 1&2 Sci Data Products Level 0 Sci Data Receive & Archive Science Data Analysis Pipeline Archive & Send MOC GSSC Level 0 Data, Integrated Observ. Timeline, As-Flown Timeline, Flight Dynamics Products, Anomaly Reports, PDB updates, LAT/GBM Sci Alerts, LAT/GBM/SC Problem Alerts Level 0 Hkpg Data CHS monitoring & trending Integrated Observ. Timeline, As-Flown Timeline, Flight Dynamics Products LAT Science Activity Timeline, LAT Instrument Commands, LAT Instrument Loads Contingency: LAT Instrument Commands, LAT Instrument Loads Mission Planning GSSC Archive & Send MOC Science Plan Receive & Archive Tested OK Commands to Verify All data into ISOC, and products out LAT Test Bed Alerts, Logs, Process status, File status Anomaly Tracking & Notification System Database Web Access

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

  13. Report Generation and Use

  14. Command and TelemetryDefinition File Verification LAT ISOC Modify .dbx file(s) .dbx files MOC Project Database (master Cmd &Tlm definitions) OK (test passed with new .dbx file(s) ITOS CCSDS Commands LAT Testbed Replay Commands & Receive Telemetry telemetry Command log, error log and optional Text/Stripchart displays Test Suite of STOL Commands

  15. Nominal LAT Command Process

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

  17. Data Display and Analysis Support • Web access • Data products (logs, reports, level 0/1/2 data) • Electronic logbook provides log entry, log and report viewing, and file download • Password protection on privileged actions (e.g. log entry, data download) • Tools • Includes ROOT, HippoDraw, IDL, and JAS • Used in ISOC to generate reports accessible over web • Data download allows users to process data locally with tools installed on their machine

  18. Electronic Logbook • Running record of ISOC and its data products in and out • Program currently in use by I&T can meet ISOC requirements • All entries go in relational database • Web-accessible • Includes • Record of data products received and sent and links to each • User comments • Time tag on each entry • Suggested Metric for ISOC • Response times – e.g. from receipt of level 0 data to sending of level 1 & 2 products

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

  20. Software Development & Testing Schedule

  21. Testing • Four software releases • Each level 3 requirement will • be mapped to the release where first needed • have test procedures defined • Each release includes functionality required for subsequent GRTs • R3 (Dec 05) includes all requirements • R4 (Jul 06) includes enhancements based on user experience (e.g. during Mission Simulation) • Two weeks prior to each release • test that requirements newly included in that release are met • regression test previously included requirements

  22. Summary of ISOC Software Capabilitiesfor GRTs & ETEs

  23. ISOC Software Development Schedule Phase / Milestone Aug-04 Sep-04 Oct-04 Nov-04 Dec-04 Jan-05 Feb-05 Mar-05 Apr-05 May-05 Jun-05 Jul-05 Aug-05 Sep-05 Oct-05 Nov-05 Dec-05 Jan-06 Feb-06 Mar-06 Apr-06 May-06 Jun-06 Jul-06 Aug-06 Sep-06 Oct-06 Nov-06 Dec-06 Jan-07 Feb-07 Mar-07 ISOC CDR ITOS setup/configuration ISOC Verif. with Test Bed Diagnostic Tool Dev Mission Planning Dev DB/Web/E-logbook Dev Plotting/Trending Dev SW enhancements ISOC Demos ISOC Simulation Testing ISOC SW Releases 1 4 2 3 Ground Readiness Tests 3 4 7 2 6 5 End-to-End Tests 6 5 4 3 1 2 Environmental tests at NRL ISOC testing at NRL ISOC ready to take over LAT operation ISOC used to I/F with LAT (front-door only) Mission Simulations Launch SW Dev Slack Times

  24. Staffing Level (ROM) • Based on review of level 3 requirements • Average LOC per reqt is >10 and <100 • 80 LOC per reqt appears conservative (probably high) • Of 467 reqts, 88 remain to be developed and all need to be verified • 88 reqts x 80 LOC/reqt = ~7,000 LOC (ROM) • Estimate 2,000 LOC per programmer per year • 7,000 LOC to develop / 2,000 LOC/pgmr-yr = 3.5 programmer years • Release 4 is July 06 •  ~ 2 calendar years of development • But with slack time and more intensive 1st year of development, need 3 programmers + 1 tester

  25. Status • Architecture concept is solid • Ready to proceed • Refine and document software design • Implement it • Lots of testing and demos • I.e. lots of work to do…

  26. ITOS Demo

  27. ITOS Demo Play back simulated LAT housekeeping telemetry • In real-time --this simulates: • Real-time connection to MOC for S/C contact periods • ISOC test bed use for verifying command sequences and ITOS Command & Telemetry definition files • Fast replay --this simulates: • Rapid replay of LAT and S/C housekeeping data files received from MOC after download from SSR • Examine print file generated during playback • Configured to record parameters of interest • Available for download through e-logbook

More Related