1 / 6

MIRI software; implementation plan

This document outlines the implementation plan for the MIRI software, drawing from the experiences gained during the HIFI mission. It emphasizes the importance of thoughtful planning and scenario development in operations. The document covers the identification of assumptions, analysis of other missions like ISO and Spitzer, and the integration of user-friendly systems early in the development phase. It highlights key milestones and activities required for the successful support of MIRI science operations, including collaboration, resource allocation, and the establishment of a robust data analysis framework.

sylvia
Télécharger la présentation

MIRI software; implementation plan

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. MIRI software; implementation plan Peter Roelfsema

  2. Experience from (HIFI) DP • Do take the time to think before you start running • For Herschel we actually (largely) made what we envisioned when the Herschel operations scenario was established in 1999/2000 • Work out scenario’s; ‘ a day in the life of…’ • Identify all assumptions • i.e. explicit and implicit assumptions • Look carefully at other missions • ISO; pipeline initially different between IDT and SOC, later merged into common source code (all IDL) • Spitzer; pipeline in SSC is an entirely closed box • Herschel; integration fundamental in system design • ‘Smooth transition’ pays off • HIFI is already using the operational system since HIFI DM  early (2 years before launch) DP testing and fast ILT data reduction • Make the system user friendly as early as possible • Get early ‘helpdesk’ for Calibration scientists and developers MIRI science support meeting - Amersfoort 11/01/2007

  3. Steps to get MIRI SW implemented – ‘the plan’ • Get the top level view – scenario document • What are the aim/needs for the operations phase • What are the aims/needs for ground calibration • How are these related; smooth transition between phases? • What is the relationship between pipeline and interactive analysis • What is the timeline, major milestones • What is needed to support this view • Are there systems already supporting this  e.g. Hershel… or are we fixed/limited by JWST/STScI context? • What conversion/new implementation is needed • What/how much manpower is needed • How do we implement this MIRI science support meeting - Amersfoort 11/01/2007

  4. Status • Get the top level view • Significant work on establishing data analysis requirements • Initial identification of relevant work packages • Some initial guestimates of required effort needed …but not from scratch • Framework effort depends on whether we can re-use existing systems • …but no progress on top level scenario (since July 2006) • Largely due to unavailability of personnel MIRI science support meeting - Amersfoort 11/01/2007

  5. Next steps Priority of activities: • Establish top level scenario  april? (…march??) • Requires people; are we confident they are available? • PRR, RSH, BV, JB? • Investigate framework approach • Can go on in parallel • HCSS is a good candidate given available expertise • Fundamental question; are there ‘new’ processing problems? • New in the sense of requiring a novel data analysis framework design • Note: a framework could be anywhere between very expensive and essentially for free • Needs coordination within EC but also STScI MIRI science support meeting - Amersfoort 11/01/2007

  6. Next steps – cont. • Detailed implementation plan  may? • Further detailing of work packages • Timeline of development • Agreement on who does what • Requires partner commitments • Major questions: • What are important milestones • March EC meeting? • Who takes the lead for scenario document • Who does the coordination with EC/STScI MIRI science support meeting - Amersfoort 11/01/2007

More Related