Status of Computing at PDR B.E. Glendenning (NRAO), G. Raffi (ESO)

Slides:



Advertisements
Similar presentations
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Advertisements

National Radio Astronomy Observatory June 13/14, 2005 EVLA Phase II Proposal Review EVLA Phase II Computing Development Bryan Butler (EVLA System Engineer.
The decision box represents key management decisions and serve as the GATES which delineate phases. The decision can be to proceed, exit, or recycle. More.
Systems Analysis and Design 9th Edition
Fundamentals of Information Systems, Second Edition
Systems Engineering Management
Release & Deployment ITIL Version 3
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
October 2005ALMA Cost Review1 Atacama Large Millimeter Array Science IPT Review Bilateral Project Scientists: Al Wootten, (Lead) Tom Wilson, (Deputy) Ryohei.
Work Package 6: Performance Specification Ian McCrea.
C. ChandlerEVLA Advisory Committee Meeting September 6-7, Scientific Commissioning Plan Claire Chandler.
ANASAC, , Chicago Computing B.E. Glendenning (NRAO)
Hunt for Molecules, Paris, 2005-Sep-20 Software Development for ALMA Robert LUCAS IRAM Grenoble France.
ADASS XI Sept30-Oct3, 2001 The ALMA Common Software (ACS) as a basis for a distributed software development G.Raffi, G.Chiozzi (ESO), B.Glendenning (NRAO)
Common PDR Problems ACES Presentation T. Gregory Guzik March 6, 2003.
EVLA Computing Overview Gareth Hunt EVLA Advisory Committee 2002 June
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
ALMA Operations and the North American ALMA Science Center Al Wootten NRAO.
McMullinEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Data Post-processing: SSG (AIPS++/CASA) Development J. McMullin.
ICT Coordination and Planning Meeting #1 (17-19 April 2013) ALMA Dashboard 1.0 Giorgio Filippi The Atacama Large Millimeter/submillimeter Array.
The ALMA Software and Release Management Ruben Soto Software Operations Group & Release Manager Joint ALMA Observatory.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
ALMA Software B.E. Glendenning (NRAO). 2 ALMA “High Frequency VLA” in Chile Presently a European/North American Project –Japan is almost certainly joining.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
CRISP & SKA WP19 Status. Overview Staffing SKA Preconstruction phase Tiered Data Delivery Infrastructure Prototype deployment.
N. RadziwillEVLA NSF Mid-Project Report May 11-12, 2006 NRAO End to End (e2e) Operations Division Nicole M. Radziwill.
NRAO Users Committee Meeting May 20-21, National Radio Astronomy Observatory NRAO Users Committee Meeting – May 20-21, 2008 ALMA Operations Chris.
K. Y. LoEVLA Advisory Committee Meeting September 6-7, 2007 Charge to the Committee K. Y. Lo.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
EVLA Transition to Science Operations: An Overview EVLA Advisory Committee Meeting, March 19-20, 2009 Bob Dickman AD, NM Operations.
Gustaaf van MoorselEVLA Advisory Committee Meeting May 8-9, 2006 EVLA Computing Software Overview.
EVLA Software Bryan Butler. 2007May22EVLA SAGE Meeting2 Requirements and Goals of EVLA Software Maximize scientific throughput of the instrument At a.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
SSC SI Data Processing Pipeline Plans Tom Stephens USRA Information Systems Development Manager SSSC Meeting – Sept 29, 2009.
Response to ASAC Report of May 2004 Response to ASAC The Atacama Large Millimeter Array Tom Wilson and Al Wootten Science IPT.
ALMA Week, 2004 March 3-5, in Garmisch, Germany ALMA Operations Plan: Progress Report Darrel Emerson (NRAO) David Silva (ESO) JAO Operations Group
2007Sep06 EAC Butler - Software Overview 1 Software Overview Bryan Butler.
FASR Software Considerations Gordon Hurford SSL AUI – August 2007.
SAGE meeting Socorro, May 22-23, 2007 EVLA Science Operations: the Array Science Center Claire Chandler NRAO/Socorro.
P. NapierEVLA Advisory Committee Meeting September 8-9, EVLA Advisory Committee Project Overview P. Napier, Project Manager Management, Schedule,
December2002, Garching ALMA Computing IDR ALMA AIPS++ Audit Steven T. Myers (NRAO)
P.NapierEVLA Advisory Comm, 14 Dec 2004 Project Overview Peter Napier, EVLA Project Manager Status 2003 Committee Response.
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing Organization/Development.
Mark McKinnon NSF Mid-Project Review May 11-12, Baseline Project Definition Mark McKinnon Project Manager.
ESO, 17 April 2007ESAC meeting1 ALMA offline User Test 5 Silvia Leurini, ESO.
RupenEVLA Advisory Committee Meeting May 8-9, Software Requirements Michael P. Rupen EVLA Project Scientist for Software rev. 3may06.
N. RadziwillEVLA Advisory Committee Meeting May 8-9, 2006 NRAO End to End (e2e) Operations Division Nicole M. Radziwill.
UlvestadEVLA Advisory Committee Meeting September 6-7, Future EVLA Operations Jim Ulvestad.
Atacama Large Millimeter/ submillimeter Array - ALMA ASAC Charges For Oct 31 ASAC Report to ALMA Board Al Wootten JAO Interim Project Scientist.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Frazer OwenNSF EVLA Mid-Project Review May 11-12, Transition to EVLA
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing End-to-end (E2e) software.
Computing Introduction Gareth Hunt EVLA System PDR 2001 December 04.
Jim UlvestadEVLA Advisory Committee Meeting May 8-9, EVLA Operations Jim Ulvestad Array Science Center Concept Requirements Staffing and Cost Plans.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
TK2023 Object-Oriented Software Engineering
Software Reviews Ashima Wadhwa.
EVLA Computing Software Overview.
Lockheed Martin Canada’s SMB Mentoring Program
VLA to EVLA Transition Plan
Gustaaf van Moorsel September 9, 2003
Software Requirements
Mark McKinnon EVLA Project Manager
EVLA Advisory Committee Meeting, March 19-20, 2009
Observatory Science Operations
EVLA Operations Jim Ulvestad
Observatory Science Operations
Preliminary Project Execution Plan
Presentation transcript:

Status of Computing at PDR B.E. Glendenning (NRAO), G. Raffi (ESO)

ALMA Project ASAC 2-3 April 2003 Computing IPT2 Phase 2 Scope Scope: Observing preparation and support through archival access to automatically produced (pipeline) images

ALMA Project ASAC 2-3 April 2003 Computing IPT3 Management Planning Computing Plan (framework) and 15 subsystem agreements prepared –Computing Plan submitted to document approval process (comments from JAO to be accounted for) –Subsystem agreements approved by Computing IPT Management model: –Agreement “contracts” followed by subsystem scientists (scope) and software management (schedule, cost) –Initial PDR, yearly CDRs and release planning –Synchronized 6-month releases across all subsystems –SSR requirements mapped to releases for progress tracking

ALMA Project ASAC 2-3 April 2003 Computing IPT4 Management Planning (2) –Readiness reviews, acceptance tests, and delivery to interim operations in 2007 –“Data flow” items get a second development period during interim operations review requirements after first experience with operations Not subject to current agreements – institutional responsibility could shift PackageFeature nameShort descriptionSSR requirement Numbers To be completed at Release (R ) Status at Milestone T0 (N,P,C) ObsProjectCheckObsDatabaseCheck observation database for conflict 3.0R10R3.0N ObsProjectLocal saveSave/recover programs to/from local disk in human readable form 3.0-R11, 3.1R3, 3.1R12 R1.0N

ALMA Project ASAC 2-3 April 2003 Computing IPT5 AIPS++ Evaluation AIPS++ (along with the ESO Next Generation Archive System) is a major package proposed for use by ALMA –Both to ensure at least one data reduction package is available to users and in implementing ALMA systems (notably the Pipeline) AIPS++ is a very controversial package (long development period, has not yet received wide acceptance) ALMA Computing jointly with SSR committee, has arranged several evaluations (next presentation by R.Lucas) –Audit of capabilities based on documentation –AIPS++/IRAM tests to test suitability for millimeter data –Benchmarking tests NRAO/AIPS++ Consortium have set up a technical review

ALMA Project ASAC 2-3 April 2003 Computing IPT6 AIPS++ technical review Held at the National Radio Astronomy Observatory in Socorro on March 5-6, 2003 Review panel: Roger Brissenden (CfA), Hilton Lewis (Keck), Chair, Andrew Lumsdaine (U. Indiana), Dave McConnell (ATNF), Steve Scott (OVRO), David Silva (ESO), Doug Tody (NRAO) and Rick White (STSCI). Report submitted to NRAO Director and circulated to AIPS++ Executive Committee.

ALMA Project ASAC 2-3 April 2003 Computing IPT7 AIPS++ review summary - major recommendations (1/2) Note: All here given recommendations are a short summary of the full text Change the focus of AIPS++ – from a system aiming to be a general-purpose radio astronomy package to a system that is developed to meet the strategic goals of the Consortium. Modify the Development Process –The AIPS++ master schedule should be consistent with the major project schedules (e.g., GBT, ALMA, EVLA). Strengthen the Project Management and the Project Team Further Strengthen the Project Scientist Role

ALMA Project ASAC 2-3 April 2003 Computing IPT8 AIPS++ review summary - major recommendations (2/2) Short-Term Priorities (next 12 months) –Significant improvements in reliability and stability –Performance improvements approaching the performance of AIPS –Synthesis imaging capability covering many common use cases of the VLA –Reduced emphasis on graphical user interface Proceed With the Proposed Technology Changes –The Panel finds that the case for changing the technology to support future development of AIPS++ is compelling. The proposed architectural change to the framework has technical merit and a proof of concept should be pursued at this time, in parallel with current development. However, it is critically important that this not be allowed to distract the AIPS++ team from completing the current development.

ALMA Project ASAC 2-3 April 2003 Computing IPT9 Current AIPS++ Architecture

ALMA Project ASAC 2-3 April 2003 Computing IPT10 Proposed AIPS++ Architecture

ALMA Project ASAC 2-3 April 2003 Computing IPT11 ALMA Proof of Concept AIPS++ proposes to use ALMA Common Software (ACS) technology and interoperability designs (exact technical relation being defined) –CORBA, Python, Container/Component, Java –To be confirmed by AIPS++ Executive Committee. This should allow AIPS++ to interoperate much more readily with other software packages and (particularly) ALMA subsystems –In particular it becomes easier in principle for the Pipeline to adopt engines from other packages –provided some data model interoperability exists

ALMA Project ASAC 2-3 April 2003 Computing IPT12 Preliminary Design Review March 18-20, Tucson –Panel R. Doxsey (CHAIR) (STScI, Head HST Mission Office) P. Quinn (ESO, Head of Data Management and Operations Division) N. Radziwill (NRAO, Head of GBT Software Development) J. Richer (Cambridge, ALMA/UK Project Scientist, Science Advisory Committee) D. Sramek (NRAO, ALMA Systems Engineering IPT Lead) S. Wampler (NSO, Software Architect) A. Wootten (NRAO, ALMA/North America Project Scientist)

ALMA Project ASAC 2-3 April 2003 Computing IPT13 Hot Topics presented at PDR (1/2) Missing operational requirements Science committee is being set up to answer operational questions (Lucas and Schwarz are Computing representatives there) Conflict of priority at ATF If the issue of operators is solved, we do not see here a conflict in the long run, although in 2003 we have quite some pressure. Splitting of Archive and Pipeline operation between OSF and SOC Long term baseline concept (not for Interim Science) : –Archive will be in two copies: OSF and SOC. –Calibration and Quick look running at the OSF (due to their timing) while Science Pipeline will run at the SOC.

ALMA Project ASAC 2-3 April 2003 Computing IPT14 Hot Topics presented at PDR (2/2) Only OSF in 5 years plan Santiago (SOC) and RSCs commissioning is not included. Santiago Center (SOC) commissioned in 2008 possibly with a limited bandwidth (e.g. 10 Mb/s -> 100 Mb/s) to check operations model and reliability asap. Santiago link in 2007 Good to monitor OSF and gain experience with link. Could have limited bandwidth. RSC installation (once or twice?) Baseline plan: prototype system to run the array, delivering the final (pipeline and archive) systems as late in the construction period as possible: one in Chile and one to each RSC.

ALMA Project ASAC 2-3 April 2003 Computing IPT15 Possible issues Staffing (especially at NRAO) not yet at plan, although full recruitment now in progress Data rate increase sought by Science Software Requirements group, based on assumption that Base Correlator change will be approved. –Correlator enhancements need corresponding increase in data rates to be of most importance –Cost implications need to be determined

ALMA Project ASAC 2-3 April 2003 Computing IPT16 PDR Recommendations (1/2) Unofficial top-level results, based on exit debriefing by panel to IPT Management and M. Rafal –Official report and IPT response by mid-April Well prepared PDR; at or ahead of where similar projects have been at this stage The ALMA Project needs to develop an understanding of operations, and the Computing IPT needs to fold this in to their planning and priorities. This might result in reprioritization of SSR requirements ALMA project needs to define clearly the steps necessary for getting to, and implementing, Interim Operations and the consequent requirements for computing support

ALMA Project ASAC 2-3 April 2003 Computing IPT17 PDR Recommendations (2/2) The interaction with AIPS++ requires careful management. Operational (Pipeline) requirements on AIPS++ need further development. Testing effort seems satisfactory; management will need to follow-up to ensure subsystem unit tests are in fact carried out

ALMA Project ASAC 2-3 April 2003 Computing IPT18 Computing Goals for Support prototype antenna tests 2.Use AIPS++ for ALMA Computing work (Pipeline, Off-line, DRUI) while completing feasibility phase: - AIPS++ benchmarking - Support use of ACS in AIPS++ Proof of Concept  Review progress on AIPS++ in 1 year (CDR2) Produce 1st integrated ALMA software Release Waiting for ALMA Operations Plan (software aspects)