1 / 11

Gamma-ray Large Area Space Telescope

Gamma-ray Large Area Space Telescope. GLAST Large Area Telescope ISOC Peer Review 2.3 Verification and Validation Lori Bator ISOC Chief Engineer. Methods of Verification and Validation. I&T Operations Goal: Verify and validate SOG and LOF tools and functions Data Challenges

karly-howe
Download Presentation

Gamma-ray Large Area Space Telescope

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 ISOC Peer Review 2.3 Verification and Validation Lori Bator ISOC Chief Engineer

  2. Methods of Verification and Validation • I&T Operations • Goal: Verify and validate SOG and LOF tools and functions • Data Challenges • Goal: “End to end” test of science analysis software • ISOC Tests • Goal: Verify and validate ISOC capabilities • Ground Readiness Tests (GRTs) • Goal: Verify and validate system interfaces and data flows • End-to-End (ETE) tests • Goal: Verify and validate interface between ground system and observatory • Mission Simulations • Goal: Verify operation team readiness prior to launch

  3. Integration and Test • I&T exercises SOG and SAS functions and tools in increasing complexity • Provides a verification of ground operations software design • Provides a validation of command and telemetry database • Some command procedures will be validated, such as instrument turn on and any tests that will also be used in on-orbit checkout • Remaining ISOC command procedures will be validated on the test bed

  4. Data Challenges • Will be discussed by Richard Dubois in section 7.3

  5. ISOC Tests • ISOC design is verified through a demonstrate of software and hardware capabilities • Tests will provide a verification and validation of ground operations software • Later tests will include simulations on the test bed • Test will be scheduled to occur prior to ground system tests to ensure ISOC functionality beforehand • Tests will occur in conjunction with ISOC software releases • Goals of tests address the ISOC-related goals of the ground system tests

  6. Ground Readiness Tests • Purpose of tests is to validate the ground system interfaces data flows, performance, and major functionality of the GLAST ground system • ISOC supports the test as part of the ground system • ISOC will provide input to test objectives, script reviews, and product development • FOT is responsible for planning, documenting and coordinating the execution of the test • Tests utilize simulators and recorded data and may include the spacecraft and integrated observatory

  7. ISOC Function in GRTs • GRT #1 – 02/15/05 • Provide command and telemetry database input • GRT #2 – 04/15/05 • Receive Level 0 data from MOC • Receive RT HK data from MOC • Provide basic LAT planning and scheduling • GRT #4 – 09/01/05 • Receive Level 0 data from MOC • GRT #5 – 11/15/05 • Provide Level 1 and Level 2 products to GSSC • Provide more complex LAT planning and scheduling • Provide instrument file uploads to GSSC • Provide simulate science data • GRT #6 – 02/15/06 • Contingencies added • GRT #7 – 05/01/06 • Clean-up and regression testing

  8. End-to-End Tests • Validate interface between MOC workstations at GSFC and the GLAST Observatory • Later tests include operational scenarios • ISOC will support LAT testing through an Instrument Operations Team (IOT) • Determine instrument configuration and interfaces required to meet the objectives of the test • Approve all operational products to be used with the instruments including all loads, PROCs and the scripts to ensure the instrument is properly operated • Provide operational products as required to meet the test objectives • Provide an assessment of instrument performance to be included in the test report

  9. ISOC Function in ETEs • ETE #1 – 2/11/06 • Provide Level 1 data products to GSSC • Receive Level 0 files from MOC (post-test) • ETE #2 – 4/15/06 • Provide instrument commands and file loads • Support memory dumps of instrument • ETE #3 – 6/15/06 • Support basic observatory operations • ETE #4 – 8/25/06 • Instrument turn on • ETE #5 – 10/14/06 • Regression test and contingencies • ETE #6 – 2/1/07 • Final ETE at launch facility

  10. Mission Simulations • Formal operational simulations (rehearsals) at MOC to verify launch readiness of the operations personnel, products (e.g., procedures), and processes • Conducted by MOC • Include activities such as L&EO, day-in-the-life, and contingency rehearsals • Scheduled to occur from May 2006 through launch

  11. Conclusion • ISOC will be involved in many tests and simulations • First flow of data to/from ISOC is GRT#2 (April 2005) • Success of tests requires ISOC to be ready • ISOC tests need to be well defined • Draft of LAT ISOC Validation and Verification Plan(LAT-MD-2513-1) • Infrastructure needs to be in place • SAS is testing pipeline and software through DCs • SOG and LOF tools are tested through I&T • Software issue tracking tool

More Related