60 likes | 180 Views
MIRI software; implementation plan. Peter Roelfsema. 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
E N D
MIRI software; implementation plan Peter Roelfsema
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
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
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
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
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