Output Formats Part I Bryan Butler NRAO. 2006-Oct-31EVLA Correlator f2f2 Overview 2 types of data: –Monitor data - of interest to engineers and system.

Slides:

Advertisements

Similar presentations

Test Builder & Test Executor Sonja Vrcic Socorro, December 12, 2007.

Advertisements

14-Jun-2004EVLA Software Design Review Transition Plan Bill Sahr 1 EVLA Hybrid Array & Transition Plan.

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

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.

The Prototype Correlator Sonja Vrcic Socorro, 5. December, 2006.

C. ChandlerEVLA Advisory Committee Meeting September 6-7, Scientific Commissioning Plan Claire Chandler.

WIDAR Prototype Testing User Interface Software Kevin Ryan NRAO-DRAO Face-to-Face Meeting April 3, 2006.

ALMA Software B.E. Glendenning (NRAO). 2 ALMA “High Frequency VLA” in Chile Presently a European/North American Project –Japan is almost certainly joining.

Mark McKinnon EVLA Advisory Committee Meeting May 8-9, Project Overview Mark McKinnon Project Manager.

Correlator Growth Path EVLA Advisory Committee Meeting, March 19-20, 2009 Michael P. Rupen Project Scientist for WIDAR.

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.

Pre-OTS Testing in Penticton Sonja Vrcic Socorro, December 11, 2007.

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.

Sean M. Dougherty Dominion Radio Astrophysical Observatory Herzberg Institute of Astrophysics National Research Council Canada The WIDAR Correlator.

Long Term Transition Plan Gareth Hunt EVLA M&C PDR 2002 May 15.

R MoeserCorrelator f2f Meeting1 MCAF (Metadata Capture and Formatting) Rich Moeser.

WIDAR Real-Time Data Display D. Del Rizzo EVLA Correlator Software f2f April 3-6, 2006.

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.

EVLA Monitor & Control Transition System Software

P.NapierEVLA Advisory Comm, 14 Dec 2004 Project Overview Peter Napier, EVLA Project Manager Status 2003 Committee Response.

14 June, 2004 EVLA Overall Design Subsystems II Tom Morgan 1 EVLA Overall Software Design Final Internal Review Subsystems II by Tom Morgan.

RupenEVLA Advisory Committee Meeting May 8-9, Scientific Oversight and Testing of Software Michael P. Rupen EVLA Project Scientist for Software.

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.

Station Board Testing EVLA Correlator S/W F2F 3-4 April 2006 D. Fort.

Configuration Mapper Sonja Vrcic Socorro,

M.P. RupenCorrelator Face-to-Face Meeting 31 Oct 2006 Output Formats Part II Michael P. Rupen.

RupenEVLA Advisory Committee Meeting May 8-9, Software Requirements Michael P. Rupen EVLA Project Scientist for Software rev. 3may06.

Correlator GUI Sonja Vrcic Socorro, April 3, 2006.

M. McKinnonEVLA Advisory Committee Meeting September 6-7, Project Overview Mark McKinnon Project Manager.

EVLA Software - Overview Bryan Butler NRAO. Bryan ButlerEVLA NSF Review 2006May History of EVLA Computing (1) EVLA computing consists of three parts:

Atacama Large Millimeter/submillimeter Array Expanded Very Large Array Robert C. Byrd Green Bank Telescope Very Long Baseline Array Emmanuel Momjian (NRAO)

Software Requirements for the Testing of Prototype Correlator Sonja Vrcic Socorro, December 11, 2007.

Bill SahrNSF Review May , EVLA Monitor & Control.

Master Correlator Control Computer (MCCC) Requirements & Status Sonja Vrcic Socorro, December 12, 2007.

SAGE meeting Socorro, May 22-23, 2007 WIDAR Correlator Overview Michael P. Rupen Project Scientist for WIDAR & Software.

Data Examination and Checking Programs--Requirements B. Carlson

Software Overview Sonja Vrcic

Bryan Butler EVLA Computing Division Head

EVLA Archive The EVLA Archive is the E2E Archive

Monitor and Control Software

EVLA Overall Software Design

Interactions with ALMA

EVLA Computing Software Overview.

EVLA Prototype Correlator (PTC)

VCI Overview Sonja Vrcic

PTC Setup at VLA B. Carlson

Software Requirements

Scientific Oversight and Testing of Software

VLA to EVLA Transition Plan

Bryan Butler (for Bill Sahr)

Software Requirements

EVLA Monitor & Control System

Gustaaf van Moorsel September 9, 2003

Software Requirements

Prototype Correlator Testing

Mark McKinnon EVLA Project Manager

EVLA Advisory Committee Meeting, March 19-20, 2009

EVLA M&C Components Observation Executor, Interim & Final Obs2script

Correlator Growth Path

EVLA Monitor & Control Bill Sahr NSF Review May , 2006

EVLA Construction Status

Presentation transcript:

Output Formats Part I Bryan Butler NRAO

2006-Oct-31EVLA Correlator f2f2 Overview 2 types of data: –Monitor data - of interest to engineers and system testers; stored in the “Monitor Database” –Science data - what’s interesting to astronomers, which comes in two flavors: What fits in the definition of the “Science Data Model”, e.g., correlation products What doesn’t, e.g., “radar mode” output (all of this comes from the Station Boards or Phasing Boards)

2006-Oct-31EVLA Correlator f2f3 Science Data Overview 4 phases: –Modcomp; VLA correlator –Post-Modcomp; VLA correlator –Prototype WIDAR –Production WIDAR

2006-Oct-31EVLA Correlator f2f4 Modcomp; VLA correlator

2006-Oct-31EVLA Correlator f2f5 Post Modcomp; VLA correlator

2006-Oct-31EVLA Correlator f2f6 Prototype WIDAR Is this OK? This is the final EBDF

2006-Oct-31EVLA Correlator f2f7 Production WIDAR

2006-Oct-31EVLA Correlator f2f8 Production WIDAR - Detailed

2006-Oct-31EVLA Correlator f2f9 Needed Software VisPipe (Modcomp retirement) IDCAF (Modcomp retirement) CBE (ASCII output - PTB, PTC h/w) CMIB on SBs and PBs (PTC h/w or OTS?) IDCAF2 (PTC OTS) IAAT (PTC OTS) AIPS (PTC OTS) CASA (either PTC OTS or Production WIDAR) CBE (EBDF output - PTC OTS) DCAF (Production WIDAR) AAT (Production WIDAR)

2006-Oct-31EVLA Correlator f2f10 Needed Software, Timeline PTB tests - now: –CBE (ASCII output) Modcomp retirement - June 2007: –VisPipe –IDCAF Prototype Correlator hardware tests - January 2008: –CMIBs on SBs and PBs for non-SDM data (and s/w to access it) Prototype Correlator OTS tests - April 2008 (?): –IDCAF2 or DCAF –IAAT (reads either UVFITS or SDM, depending on above) –AIPS –CASA (only if full DCAF used) –CBE (EBDF output) Production WIDAR - January 2009 (?): –DCAF (if not used for PTC) –CASA (if DCAF not used for PTC) –AAT (SDM access version)

2006-Oct-31EVLA Correlator f2f11 Questions Can we skip writing UVFITS and go right to production version for the prototype? What is the final form of the EVLA BDF and how does it differ from ALMA? What is the final form of the EVLA SDM, and how does it differ from ALMA? What is the format and destination for non-BDF and non-SDM data - Monitor Database; SB Database; PB Database (or can these all be the same?) and when do we need these? Does WIDAR have its own Monitor Database, and if so, are the records in it the same format as the other? Do the CMIBs and other processes communicate directly with the Monitor Database, or through the VCI (residing on the MCCC)? Do CMIBs and other processes communicate directly with DCAF, or through the VCI (residing on the MCCC)? For production WIDAR, do CPCC, PBs, and CBE/FF need a connection to DCAF? How much (if any) of CBE, FF, and DCAF software can be borrowed from ALMA?