1 / 23

The TRACE Model for Operations

The TRACE Model for Operations. Ted Tarbell tarbell@lmsal.com. The TRACE Model for Operations. TRACE Initial Phases Transition to Long-Term Operational Phase Why TRACE Remote Operations Works Tools for TRACE Planners & Monitors Science Coordination with Remote Planners

kirsch
Download Presentation

The TRACE Model for Operations

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. The TRACE Model for Operations Ted Tarbell tarbell@lmsal.com

  2. The TRACE Model for Operations • TRACE Initial Phases • Transition to Long-Term Operational Phase • Why TRACE Remote Operations Works • Tools for TRACE Planners & Monitors • Science Coordination with Remote Planners • Report on Other Missions by Dr. Chuck Holmes (NASA HQ) T. D. Tarbell, LMSAL tarbell@lmsal.com

  3. TRACE Initial Phase (1) • Launch (2 April, 1998) to 1st eclipse season (November, 1998) • April: 3 weeks outgassing, 1 week engineering checkout • May - June: 6 weeks to finish “Initial 30-Day Plan,” coordinated with SOHO • June – November: 5 months of observing without SOHO, refining observing programs and procedures, and training weekly science planners • All Operations at GSFC Experiment Operations Facility • No instrument problems so engineering staff went home after ~1 week • 2 scientists, 1 assistant, 1 computer sysadmin resident at GSFC • All other weekly planners traveled to GSFC for 7-10 day visits • Science planning by telecons and lots of email • Daily telecons at first with LMSAL/SAO/MSU, then weekly • Simple coordinations with Yohkoh & ground based observatories

  4. TRACE Initial Phase (2) • All science observing programs were completely rewritten in this period • Better types of sequences were developed, both for science and for calibration • Most preflight sequences were never used again • Operations were difficult for the early planners • Only ~6 people had enough knowledge of the instrumdent to be a weekly planner, learning how to do it on the job • Much stress from daily deadlines and too many details to follow • When operations began to settle down shortly before eclipse season, we began to train new planners • Science Planning & Operations in this phase were done with approximately the same approach as that of the Solar-B MODA Outline

  5. Transition to Operational Phase • During 1st eclipse season, planning software installed at LMSAL • Mirroring of planning data, ftp transfers of timelines and quick look data completely successful • During 2nd year of observing, 2 scientists, 1-2 assistant planners, 1 computer sysadmin resident at GSFC • Occasional visits by other scientists to be weekly planner • Frequent JOP’s with SOHO scientists at GSFC and in France • After 2nd year, no resident scientists, 1 part-time planner, 1 part-time computer sysadmin • Most planning now done at LMSAL, SAO, MSU • Travel to GSFC is done by choice to interact with scientists there, not by necessity to do science planning & operations

  6. Why TRACE Remote Operation Works • Science planning is done by email & telecon, even daily target selection • Observing programs are always prepared in advance, and usually tested onboard before a JOP is run with other instruments • Planning data (SAA’s, station passes, etc.) and quick-look telemetry is mirrored to multiple remote sites (LMSAL, MSU, SAO) • Remote sites run same planning software as in GSFC EOF • Prepare observing tables & timelines, send to GSFC by secure sftp and ssh for uplink by the NASA satellite operators • No normal Real-Time operations except uplink of timeline and tables • People watch web displays of health & status at different places & times • One part-time science planner at GSFC always on-call

  7. TRACE Timeline Generator / Editor Header Editor Timeline Editor Current onboard Obs. Sequences

  8. TRACE Target Selector Main Widget Past location in blue, Future locations in green, Squares for TRACE & MDI HiRES FOV’s

  9. TRACE Simulator TRACE Simulator

  10. Web Health Monitoring

  11. Observation As-Run Summary

  12. TRACE Sequences & Frames

  13. TRACE Frame Generator / Editor main widget frame files CCD areas

  14. Science Coordination with Remote Planners • TRACE has run successful joint observations not only with SOHO at GSFC but also with: • SOHO “MEDOC Campaigns” with planners in Paris • Ground-based observatories in the Canary Islands, Sac Peak & Hawaii • Yohkoh and ground-based observatories in Japan • Campaigns must be scheduled well in advance • Observing programs must be written and run on simulator in advance • Usually tested onboard by a short run a few days in advance • All parties must understand & follow the timing constraints for target selection • All email must go to trace_planner (NOT to an individual person) because several people follow it in addition to the weekly planner

  15. SOHO Calendar

  16. Comments on Observing Table & Timeline Generation Tools • Need fast, local tools with intuitive GUI interfaces for use at ISAS • Need ability for remote scientists to make & test observing tables before coming to or sending them to ISAS, using nearly identical tools • Need developmental databases of observing tables and secure, “checked-in” database of observing tables approved for use in flight • Need simulator or compiler to validate observing tables before they are “checked in” • Access via the network for all of the developmental tools should be considered while designing the interfaces • Running locally using mirrored databases and/or running over the network, perhaps with reduced use of graphics to speed connectivity • Must guarantee adequate security, of course

More Related