1 / 4

Software Development Introduction

Software Development Introduction. 18-month Chronology Organization Key Issues. 18-month Chronology. Spring 2003: International AIPS++ Project dissolved 6/2003: Interferometry S/W Division formed, absorbing AIPS++. Project-oriented focus begins

Download Presentation

Software Development Introduction

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. Software Development Introduction 18-month Chronology Organization Key Issues EVLA Advisory Committee December 14-15, 2004

  2. 18-month Chronology • Spring 2003: International AIPS++ Project dissolved • 6/2003: Interferometry S/W Division formed, absorbing AIPS++. Project-oriented focus begins • 8/2003: EVLA Computing formed, including e2e part of Data Management • 11/2003: EVLA S/W Project Scientist named • 12/2003-6/2004: Overall high-level S/W design • FY04: EVLA begins funding 1/3 of AIPS++ • Summer 2004: Overall and S/W transition plans begin • Summer 2004: AIPS++ passes ALMA CDR2 • 10/2004: Begin developing EVLA deliverables in AIPS++ EVLA Advisory Committee December 14-15, 2004

  3. Organization • Interferometry S/W Division includes development common to several NRAO telescopes • Response to EVLA needs improved • e2e oversight committee addresses commonality among various projects • EVLA e2e contains 4 FTEs, most responsible for observatory-wide deliverables • NRAO plans search for observatory-wide software development coordinator EVLA Advisory Committee December 14-15, 2004

  4. Key Issues • EVLA is taking on more responsibility and costs of software development • VLA must be kept operational during EVLA development • EVLA presents novel post-processing problems, and we need a better model of how astronomers will reduce EVLA data • Desire for extensive e2e capabilities not matched by available funding • Maximize borrowing/re-use of ALMA developments EVLA Advisory Committee December 14-15, 2004

More Related