EVLA Monitor & Control EVLA Advisory Committee June 10 – 11, 2002.

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.
Confidential and Proprietary May 7, 2015 Real-Time Data Where You Can Use It.
Mark McKinnon EVLA Advisory Committee Meeting May 8-9, Budget, Schedule, Contingency Mark McKinnon Project Manager.
Introduction Characteristics of USB System Model What needs to be done Platform Issues Conceptual Issues Timeline USB Monitoring Final Presentation 10.
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.
James Robnett EVLA M&C Hardware PDR March EVLA Monitor and Control M&C Network.
C. ChandlerEVLA Advisory Committee Meeting September 6-7, Scientific Commissioning Plan Claire Chandler.
NetBurner MOD 5282 Network Development Kit MCF 5282 Integrated ColdFire 32 bit Microcontoller 2 DB-9 connectors for serial I/O supports: RS-232, RS-485,
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
WIDAR Prototype Testing User Interface Software Kevin Ryan NRAO-DRAO Face-to-Face Meeting April 3, 2006.
Author Wayne M. Koski EVLA Monitor & Control Software PDR May 14 & 15, EVLA Monitor and Control Module Interface Board (MIB) Design.
IPv6 Network Assessor 111 © 2005 Cisco Systems, Inc. All rights reserved. Susan Shareshian Solutions Manager, Cisco Systems, Inc.
EVLA Computing Overview Gareth Hunt EVLA Advisory Committee 2002 June
5-6 Dec, 2006EVLA M&C Critical Design ReviewRich Moeser 1 User Interfaces Rich Moeser.
Cisco S2 C4 Router Components. Configure a Router You can configure a router from –from the console terminal (a computer connected to the router –through.
Hichem Ben Frej 5-Dec-2006 EVLA M&C Transition Software CDR CMP: Control Monitor Processor 1 Hichem Ben Frej Kevin Ryan.
June 14, 2004EVLA Software Communications Infrastructure Kevin Ryan 1 EVLA Software Communications Infrastructure.
Mark McKinnon EVLA Advisory Committee Meeting May 8-9, Project Overview Mark McKinnon Project Manager.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
Overall Data Processing Architecture Review EVLA Monitor and Control Interfaces July , 2002EVLA Data Processing PDR Bill Sahr.
CRISP & SKA WP19 Status. Overview Staffing SKA Preconstruction phase Tiered Data Delivery Infrastructure Prototype deployment.
Correlator Growth Path EVLA Advisory Committee Meeting, March 19-20, 2009 Michael P. Rupen Project Scientist for WIDAR.
Rich MoeserEVLA System PDR December 4-5, EVLA System PDR Operations Requirements.
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.
ATF Control System and Interface to sub-systems Nobuhiro Terunuma, KEK 21/Nov/2007.
Software Status Sonja Vrcic Socorro,
Author Wayne M. Koski EVLA Monitor & Control Hardware PDR March 13, EVLA Monitor and Control Module Interface Board (MIB) Design.
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.
Peter NapierEVLA Correlator CoDR Nov 2, EVLA Correlator CoDR P. Napier Overall EVLA Project Plan.
Long Term Transition Plan Gareth Hunt EVLA M&C PDR 2002 May 15.
Online Software 8-July-98 Commissioning Working Group DØ Workshop S. Fuess Objective: Define for you, the customers of the Online system, the products.
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,
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.
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing Organization/Development.
EVLA Monitor & Control Software Antenna Monitor and Control Subsystem (AMCS) May 14-15, 2002 Kevin Ryan.
18-19 July, 2002Correlator Backend System OverviewTom Morgan 1 Correlator Backend System Overview Tom Morgan, NRAO.
Configuration Mapper Sonja Vrcic Socorro,
Mark McKinnon NSF Mid-Project Review May 11-12, Baseline Project Definition Mark McKinnon Project Manager.
EVLA Monitor & Control Software PDR E2E Interfaces: Observation Scheduling Complaints to: Boyd Waters John Benson, Barry Clark, Tim Cornwell, Rich Moeser,
ICALEPCS 2005 Geneva, Oct. 12 The ALMA Telescope Control SystemA. Farris The ALMA Telescope Control System Allen Farris Ralph Marson Jeff Kern National.
May07-02: Parking Meter Clint Hertz: Team Leader Austyn Trace: Communications Nick Hollander Christian Baldus.
Correlator GUI Sonja Vrcic Socorro, April 3, 2006.
EVLA Monitor & Control Software PDR Status. May 15, 2002EVLA Monitor & Control Software PDR Bill Sahr 2 Requirements, Schedule Requirements (High Level,
Software Requirements for the Testing of Prototype Correlator Sonja Vrcic Socorro, December 11, 2007.
Bill SahrNSF Review May , EVLA Monitor & Control.
Bill SahrEVLA Advisory Committee Meeting September 8-9, EVLA Monitor & Control.
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.
Overall Data Processing Architecture EVLA timeline and priorities.
Master Correlator Control Computer (MCCC) Requirements & Status Sonja Vrcic Socorro, December 12, 2007.
Software Overview Sonja Vrcic
THE PROCESS OF EMBEDDED SYSTEM DEVELOPMENT
EVLA Computing Software Overview.
Antenna Monitor & Control Subsystem Engineering Requirements
Budget, Schedule, Contingency
Bryan Butler (for Bill Sahr)
EVLA Monitor & Control System
Gustaaf van Moorsel September 9, 2003
Mark McKinnon EVLA Project Manager
Background Information P.Napier
EVLA M&C Components Observation Executor, Interim & Final Obs2script
EVLA Monitor & Control Bill Sahr NSF Review May , 2006
Task Manager & Profile Interface
Presentation transcript:

EVLA Monitor & Control EVLA Advisory Committee June 10 – 11, 2002

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 2 Status High level overall software architecture/plan –Deferred to address issue of antenna MIB systems software –To begin June, 2002 –To include examination of other codebases, especially the GBT Detailed, timelined development plan for test antenna –Short term plan developed –Full term plan to be developed during June/July, 2002 Detailed, timelined transition plan –Systems Engineer for Software was to develop this plan –Plan not completed –Socorro-resident Systems Engineer as of 6/17/2002

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 3 Status Requirements target completed Antenna monitor & control 03/22/ /04/2002 Correlator monitor & control 04/16/2002 Vacancy filled 04/14/2002. Working from Brent Carlson’s document of 01/23/2002. Correlator backend 03/18/ /10/2002 Operational Interface 03/22/ /04/2002 Observing Layer Vacancy not yet filled.

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 4 Budget As of 04/30/2002 –$385K allocated for FY2002 –$13.5K actually spent As of 06/2002, –$100K contract placed for Antenna MIB systems software (06/07/2002). –An additional $20K to be spent on Antenna MIB toolset software –Approximately $16K to be spent for systems to host Antenna MIB and Correlator MIB development environments. –Approximately $5K - $7K to be spent on daughter board for Antenna MIB development board –Approximately $12K to be spent on enhanced debugging capabilities for Antenna MIB software development

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 5 Recruitment Began with four open positions Correlator Backend covered by a new hire, Tom Morgan, 01/2002 Antenna Monitor & Control covered by contributed effort, Kevin Ryan. Need more manpower here. Correlator Monitor & Control covered by a lateral transfer, Bruce Rowen, 04/14/2002. Now have 3 vacant positions: –Replacement for Bruce Rowen (VLBA maintenance & upgrades + 50% EVLA contributed effort) –Person to work on Observing Layer –Object-Oriented/Distributed Systems As of 6/7/2002, about to make offers to 2 candidates –Bruce Rowen replacement –Observing Layer

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 6 Recruitment Four offers have been rejected –1, money –1, family issues –1, money & family issues –1, spousal employment –Plus one candidate declined to apply on basis of location We are getting the right people in the door, but our offers are not accepted. We have not yet made an offer that did not involve more than a $10K/yr cut in salary for the candidate. Advice & suggestions are welcome.

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 7 Conceptual Diagram Transparency: EVLA M&C System Strawman Diagram

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 8 Antenna Monitor & Control Heterogeneous array (Upto 4 different antenna types) Ethernet based communications Must serve a variety of users from a number of different physical locations Performance –100 microsecond command start latency –Pointing updates every 50 milliseconds –Frequency change within band – 1 sec –“Nodding” source switch rate – 1 per 10 sec –Hardware responsible for its own safety Processors in antenna must be RFI quiet

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 9 Antenna Monitor & Control, Antenna MIB Infineon TC11IB chip –1.5 Mbytes of on-chip RAM –12 MHZ, sinusoidal external clock –Almost all components of all needed peripheral interfaces are on- chip Systems software & development environment –Accelerated Technology Nucleus PLUS rtos & Nucleus networking software –Nucleus PLUS and networking components must be ported to the TC11IB chip –Nucleus MNT simulation environment for earlier development of applications software –Altium TASKING toolset for compilers, linker, locator, etc –OCDS level 1 and level 2 debugging

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 10 Antenna Monitor & Control, Antenna MIB, Systems Software Nucleus PLUS rtos 45.0 KB Nucleus NET network stack 87.0 KB Ethernet driver 5.5 KB KB Telnet server 35.0 KB Shell 35.0 KB KB Nucleus WebServ 35.0 KB KB

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 11 Correlator Monitor & Control Hardware 300+ Correlator Module Interface Boards (CMIBs) 1 Master Correlator Control Computer (MCCC) 1 Correlator Power Control Computer (CPCC) Copper based networking between MCCC & CMIBs Network switches/hubs to isolate traffic Software Virtual Correlator Interface CMCS Test Software

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 12 Correlator Monitor & Control Transparencies –Correlator network diagram –Correlator software layers –Correlator flow diagram

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 13 Operational Interface System, Requirements Overview Client Platforms –Commodity PCs/Windows/Linux (required), Sun/Solaris –Platform independent language (Java) Remote Observing Installation & Upgrades –Java Web Start Security Robustness –System will not crash because of network glitches, broken sockets, reboots of devices, etc Reliability (MTBF is TBD) Availability –99.5 % (48 hours per year) Maintainability Usability

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 14 Operational Interface System, User Access Operators Scientists Engineers/Technicians/Programmers General Public At the Antenna From the VLA AOC/NRAO Sites WWW Monitor/Control Monitor

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 15 Operational Interface System, Attributes, Issues Loosely Coupled & Highly Adaptive –Changes to the core M&C system should have no or minimal effect on client Requires highly encapsulated core M&C system Require minimization of interface dependencies Discovery based –Dynamic discovery of objects/services –Requires some form of registration & lookup –Could be very useful in the context of a real-time system with many processors that may experience resets & reboots One current focus is the issue of how the client software will communicate with the core M&C system –Java RMI, CORBA, XML-RPC, SOAP –Other observatories ?

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 16 Correlator Backend Correlator e2e BackendM & C

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 17 Correlator Backend, Overview

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 18 Correlator Backend, Major Functions InputDPOutput Correlator e2e Backend Control Backend Monitor HWSW M&C

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 19 EVLA M&C Network The EVLA M&C Network is large. –~ 57 nodes associated with each antenna: 50 physically located in each antenna + 7 per antenna nodes in the control building. A total of 1539 nodes for 27 antennas –~ 300 nodes for the correlator –“Several” crates in the control building Will need a short, formal requirements document, especially in the area of security. NRAO expenditures currently split across several different cost data sheets under several different WBS headings. Coordination, if not formal integration, is required. We have targeted June/July for this effort. Correlator M&C Network components in both the DRAO budget and the NRAO EVLA budget. Comments/discussion on the planned use of networks in the EVLA is invited.

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 20 EVLA M&C Network Transparency: Monitor & Control Network

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 21 Test Antenna Goal – Outfit test antenna with new M & C System Q Select AMCS MIB Chip done TC11IB development board in-house (late) done (05/17/2002) Select systems software for AMCS MIB done (05/21/2002) P.O. Req & License Agreement for systems software done (06/07/2002) Configure & purchase AMCS MIB development tools 06/21/2002 Delivery of simulation environment 06/21/2002 Daughter board for TC11IB development board 06/21/2002 Begin development of MIB software apps 07/01/2002 Prototype MIB board available 07/15/2002 Port of MIB systems software complete (12 wks) 08/30/2002

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 22 Test Antenna MIB systems software on development board 09/06/2002 MIB systems software onto prototype MIB board 09/13/2002 MIB software apps onto prototype MIB board 09/20/2002 Continued MIB software development thru 03/2002 Bench test & Integration of AMCS 01/ /2002 We will have approximately 6 months after installation of the MIB RTOS on the prototype MIB board for continuing software development but this development will be intermixed with bench testing.

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 23 Test Antenna, Software Tasks AMCS MIB –Systems Software & Toolset –Communication Functions –Control & Computation Functions –Engineer/Technician Interface Screens Test Antenna, Single Dish Phase –Command Line Interpreter –Timekeeping routines –Geometry routines –Antenna pointing model –Archive for pointing model parameters –Archive for monitor data –Operator Interface Screens

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 24 Test Antenna, Software Tasks Test Antenna, Interferometer Phase –Translator, Modcomp card input to new system commands –Lobe rotator & phase switching drivers –Fiber Optic IF system – test, monitor, control –Data flagging system

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 25 Transition Plan Array downtime must be minimized as much as possible during the transition phase. Simultaneous operation of EVLA & VLA antennas must be possible (the hybrid array). –Control & Monitor processor (CMP) OBSERVE/JOBSERVE script files must be usable on the hybrid array. Modcomp computers decommissioned as soon as possible Control of VLA Correlator by EVLA M&C system possible via the new VLA correlator controller Minimize throw-away hardware & software

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 26 Transition Plan

June 10-11, 2002 EVLA Monitor & Control EVLA Advisory Panel Bill Sahr 27 Questions/Issues Recruitment Antenna MIB: RFI, the chip, the systems software, etc Use of Ethernet in the EVLA Use of software from the GBT &/or other observatories Test antenna schedule/development plan