WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) STScI Ground System Development Status: WFC3 Wayne Baggett 11/08/2001 Wayne Baggett, STScI 1 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball WFC3 Ground System Development Status (morning session, auditorium) Development is on schedule: Phases 1 and 2 are complete (Macro definitions, Initial aperture definitions, Full-frame UVIS ACCUM, darks and bias) Phase 3 in progress (Full-frame IR MULTIACCUM, darks are done, Lamp operations in work) Phase 4 is in detailed planning Proposals with these completed modes can be entered into the system and processed through to command loads (with some caveats)! 11/08/2001 Wayne Baggett, STScI 2 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball WFC3 STScI Phase Development Plan (morning session, auditorium) Phase 5 (7/1/02 – 12/31/02) Phase 1 (7/1/00 – 12/31/00) 1. Macro Definitions 3. Aperture Definitions 14. Contingency Rework (Need only if problems are found during Test Bench testing; will displace either UVIS Subarrays or CTE Monitoring if needed) 15.SMGT Preparations 4. Basic UVIS ACCUM Mode 16. SMOV Special Commanding 5. UVIS Dark and Bias Calibrations 17. UVIS Subarrays 2. Reconfigurations Phase 2 (1/1/01 – 6/30/01) Phase 3 (7/1/01 – 12/31/01) 18. CTE Monitoring Phase 6 (1/1/03 – 6/30/03) 6. Basic IR MULTIACCUM Mode 7. IR Dark Calibrations 19. UVIS Binning 8. UVIS & IR Tungsten and Deuterium Lamp Operations Phase 4 (1/1/02 – 6/30/02) 9. UVIS & IR ALIGN Mode 10. SAA Contour Definitions 20. UVIS Post-Flash Capability 21. Autoimage Insertion for UVIS Prism Operations Phase 7 (7/1/03 – 12/31/03) 22. IR Automatic Post-SAA Darks 11. UVIS & IR Spatial Patterns 12. IR Bright Earth Avoidance 13. IR Subarrays (this should be in SMGT if at all possible) 11/08/2001 Wayne Baggett, STScI 3 WFC3 FSW/GS Splinter Meeting STScI Front-End Testing Process 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) Each Subsystem (RPS2, TRANS, Commanding) does own Code and Unit Test Component testing conducted by independent test team “End to end” testing conducted by the Flight System Engineering Team (Commanding) via “Certification Proposal” Takes Certification Proposal through RPS2 TRANS SPSS Commanding 11/08/2001 Wayne Baggett, STScI 4 WFC3 FSW/GS Splinter Meeting STScI Front-End Testing Process (cont.) 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) System Testing (aka “SMS Testing”) done on Ops benches using the Certification Proposal: Tests newly-implemented capabilities and regression tests old capabilities; done at the end of each phase Process proposal through front end systems Generate command load(s) in PASS Load and execute command loads on Ops bench Collect telemetry and science data from execution Process science data through OPUS when possible 11/08/2001 Wayne Baggett, STScI 5 WFC3 FSW/GS Splinter Meeting Prerequisites for System Testing 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) What’s needed for System Testing to occur: STScI ground system development of capability completed FSW development of capability completed (C&UT) FSW timing measurements done, analyzed, and incorporated into ground system SW/Ops bench available 11/08/2001 Wayne Baggett, STScI 6 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) To mitigate risk to our development schedule, STScI requires System Testing to be performed at least three times prior to SMGT (assumed to be 1 May 2003): Early development of basic capabilities gets more testing Both ground system and FSW are continually improved Ample opportunity to react to problems before SMGT This requires at least one year between the FSW/Ops bench availability and SMGT! 11/08/2001 Wayne Baggett, STScI 7 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) Why System Testing can’t be done now: No recons in Commanding – get transitions done by January 2002 FSW incomplete and slipping – IR detector support not available until 3 May 2002 Ops bench is incomplete Note: SM3B may impact STScI’s availability for about two months 11/08/2001 Wayne Baggett, STScI 8 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) The Ball FSW slip of 17 October 2001 has put less than one year between the availability of FSW for System Testing and SMGT. Limits bench test opportunities and increases risk to the STScI ground system development Mitigated by the inclusion of a new task in Phase 5 to allow for rework – if needed this task will displace another task, impacting the capabilities available for SMGT and launch We need earlier FSW/Ops bench availability, or schedule relief 11/08/2001 Wayne Baggett, STScI 9 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) 11/08/2001 Wayne Baggett, STScI 10 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) Constraining dates (based on Ball schedule, 17 Oct 2001): 21 Jan 2002 – Bench with Mechanism simulator available 25 Feb 2002 – Mech Part 1 (Sofa, Shutter, Correctors) C&UT 26 Feb 2002 – Mech Part 3 (Lamps) C&UT 12 Apr 2002 – UVIS Detector C&UT 29 Apr 2002 – Mech Part 2 (CSM, FSM) C&UT 30 Apr 2002 – Service Functions C&UT 3 May 2002 – IR Detector C&UT 1 May 2003 – SMGT 11/08/2001 Wayne Baggett, STScI 11 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) 11/08/2001 Wayne Baggett, STScI 12 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) 11/08/2001 Wayne Baggett, STScI 13 WFC3 FSW/GS Splinter Meeting 3rd FSW/GS Splinter November 8, 2001 @ Ball (morning session, auditorium) 11/08/2001 Wayne Baggett, STScI 14
© Copyright 2026 Paperzz