EVLA Advisory Committee Meeting, March 19-20, 2009

Slides:



Advertisements
Similar presentations
National Radio Astronomy Observatory June 13/14, 2005 EVLA Phase II Proposal Review EVLA Phase II Computing Development Bryan Butler (EVLA System Engineer.
Advertisements

Software for Science Support Systems EVLA Advisory Committee Meeting, March 19-20, 2009 David M. Harland & Bryan Butler.
Bill SahrEVLA M&C Transition System Software CDR December 5-6, EVLA Monitor & Control Transition System Software Overview.
EVLA Computing Schedule, Staffing, Testing, Tracking.
C. ChandlerEVLA Advisory Committee Meeting September 6-7, Scientific Commissioning Plan Claire Chandler.
Portal and Proposal Submission Review of SSS Software Readiness for SRO, June 5, 2009 Bryan Butler EVLA Computing Division Head.
EVLA Computing Overview Gareth Hunt EVLA Advisory Committee 2002 June
EVLA Early Science: Shared Risk Observing EVLA Advisory Committee Meeting, March 19-20, 2009 Claire Chandler Deputy AD for Science, NM Ops.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
N. RadziwillEVLA NSF Mid-Project Report May 11-12, 2006 NRAO End to End (e2e) Operations Division Nicole M. Radziwill.
Correlator Growth Path EVLA Advisory Committee Meeting, March 19-20, 2009 Michael P. Rupen Project Scientist for WIDAR.
JVLA capabilities to be offered for semester 2013A Claire Chandler.
Bill SahrEVLA Advisory Committee Meeting May 8-9, EVLA Monitor & Control.
Bill Sahr EVLA M&C EVLA Advisory Committee Meeting December 14-15, EVLA Monitor & Control.
K. Y. LoEVLA Advisory Committee Meeting September 6-7, 2007 Charge to the Committee K. Y. Lo.
Software Status Sonja Vrcic Socorro,
Archive Access Tool Review of SSS Readiness for EVLA Shared Risk Observing, June 5, 2009 John Benson Scientist.
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.
R MoeserCorrelator f2f Meeting1 MCAF (Metadata Capture and Formatting) Rich Moeser.
2007Sep06 EAC Butler - Software Overview 1 Software Overview Bryan Butler.
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,
P.NapierEVLA Advisory Comm, 14 Dec 2004 Project Overview Peter Napier, EVLA Project Manager Status 2003 Committee Response.
Introduction to EVLA Software Bryan Butler. 2006Dec05/06EVLA M&C Transition Software CDR2 EVLA Computing (Terse) History The original EVLA Phase I proposal.
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing Organization/Development.
EVLA Computing Software Overview. Gustaaf van MoorselEVLA Advisory Committee Meeting May 8-9, Contents History Organization and staffing Staffing.
Observation Preparation Review of SSS Readiness for EVLA Shared Risk Observing, June 5, 2009 David M. Harland SSS Group Lead.
Output Formats Part I Bryan Butler NRAO Oct-31EVLA Correlator f2f2 Overview 2 types of data: –Monitor data - of interest to engineers and system.
M.P. RupenCorrelator Face-to-Face Meeting 31 Oct 2006 Output Formats Part II Michael P. Rupen.
Bryan ButlerEAC meeting 2003-Sep-091 Computing Issues: Scientific Requirements Bryan Butler EVLA Project Scientist for Software (starting 2003-Oct-01)
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.
Frazer OwenNSF EVLA Mid-Project Review May 11-12, Transition to EVLA
EVLA Software - Overview Bryan Butler NRAO. Bryan ButlerEVLA NSF Review 2006May History of EVLA Computing (1) EVLA computing consists of three parts:
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing End-to-end (E2e) software.
Software Requirements for the Testing of Prototype Correlator Sonja Vrcic Socorro, December 11, 2007.
Computing Introduction Gareth Hunt EVLA System PDR 2001 December 04.
P.NapierEVLA Advisory Committee, 10 June, EVLA ADVISORY COMMITTEE PROJECT OVERVIEW Scope Organization Schedule Budget, personnel.
Master Correlator Control Computer (MCCC) Requirements & Status Sonja Vrcic Socorro, December 12, 2007.
Metadata for the SKA - Niruj Mohan Ramanujam, NCRA.
SAGE meeting Socorro, May 22-23, 2007 WIDAR Correlator Overview Michael P. Rupen Project Scientist for WIDAR & Software.
Software Overview Sonja Vrcic
Interaction of SSS Software
Bryan Butler EVLA Computing Division Head
EVLA Availability - or - When Can I Use It?
Monitor and Control Software
EVLA Computing Software Overview.
VCI Overview Sonja Vrcic
Software Requirements
Shared Risk Observing Claire Chandler EVLA SSS Review, June 5, 2009
Scientific Oversight and Testing of Software
VLA to EVLA Transition Plan
Bryan Butler (for Bill Sahr)
EVLA Advisory Committee Meeting
Science Commissioning
Software Requirements
Gustaaf van Moorsel September 9, 2003
Software Requirements
Operations Software Bryan Butler.
Shared Risk Science with the EVLA
Mark McKinnon EVLA Project Manager
NRAO End to End Integrated Operations
Observatory Science Operations
Observatory Science Operations
Correlator Growth Path
EVLA Construction Status
EVLA Postprocessing Algorithms
Requirements Bryan Butler.
Presentation transcript:

EVLA Advisory Committee Meeting, March 19-20, 2009 Software Overview EVLA Advisory Committee Meeting, March 19-20, 2009 Bryan Butler EVLA Computing Division Head

Software Scope Software to control and monitor antennas and correlator; includes software for operators, engineers, staff scientists Software system to make access to instrument and data easy for astronomers Post-processing software to allow the instrument to reach its full potential

Requirements We have detailed requirements documents (all available on the web as computing memos) in the following areas: Real-time (M&C) E2E (SSS) Engineering Operations Post-processing Requirements have priority and timescale

Remaining Milestone Schedule A - WIDAR0 testing support B - full OSRO support (256 MHz); begin support of RSRO capability (2 GHz) C - begin support of full-bandwidth RSRO capability (8 GHz) D - begin support of narrow-band RSRO capability (recirculation) E - begin support of mixed-bandwidth RSRO capability (different widths/channels per subband) F - full OSRO support (2 GHz); begin support of correlator resource reallocation RSRO capability (trade subbands for channels) G - begin support of RSRO capability (special capabilities) H - full OSRO support (8 GHz)

Software Support for Milestone -- Example Software necessary for WIDAR0: Executor controls antennas and calculates and distributes delays to correlator system Antenna MIB software Test Builder and Test Executor used along with correlator board interfaces to store and retrieve board and correlator backend configurations Board CMIB software Monitor and possibly shut down the correlator boards (CPCC) Capture and write visibility data in BDF format (CBE) Capture metadata and write it in minimal SDM format (MCAF) Write metadata into streamlined and easily searchable database (SDM Cataloger) Access metadata for search and data retrieval (AAT) Convert from BDF & SDM to Measurement Set (sdmtoms) Data analysis - either use CASA directly or use it to write UVFITS then use AIPS

Software Support for Milestone -- Example II Beyond that, software necessary for initial OSRO (ignoring operations and engineering software): Proposals preparation and submission (PST) Observation setup (OPT) Ability to control and monitor WIDAR (Configuration Mapper, Alerts, Logging, communication with EVLA M&C) Increased CBE functionality (decimation in time and frequency, blanking, weighting, Van Vleck correction, etc.) realtime telescope corrections (reference pointing only real-time correction necessary, but off-line delay, focus, pointing determinations also supported) write more complete SDM (all data necessary for normal user data post-processing) Users able to reduce their data fully within CASA (but may still export UVFITS and use AIPS)

Current Staffing Staffing is sufficient to deliver core software for OSRO and RSRO observing

Planning and Tracking We have continued the quarterly planning/tracking mechanism for SSS Goals are determined roughly 2 weeks in advance of the beginning of the quarter Tracking of progress toward goals occurs at the end of the quarter A report is included in the quarterly project updates A similar planning and tracking mechanism will be adopted for the M&C group starting this quarter (one has been in place in the past for tracking, but the planning has been less formal - occurring usually during weekly group meetings).

Software Reuse Within EVLA computing, we reuse software from many places: General software community (JAXB, FACES, Hibernate, Eclipse, Tomcat, etc.) General astronomical software community (measures, timing, CALC, SLALIB, etc.) NRAO, notably ALMA: Particular implementation of CALC CASA AAT (which is based on the ALMA NGAS system) Models - Science Data; Binary Data; Project Data; Calibration Data Catalogs - spectral line; calibrators Enumerations We will continue to reuse software wherever beneficial - it is clear that leveraging the ALMA software effort is beneficial and wherever commonality exists (and project timescales allow) we will take advantage of the synergy between the telescopes