Transcript EVLA Monitor & Control Bill Sahr EVLA Advisory Committee Meeting 1

EVLA Monitor & Control
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
1
EVLA M&C and e2e Software
EVLA M&C and e2e software
Observing Tool
Proposal Tool
PBs
Program blocks for
submission to
Scheduling Tool
Proposal generation
and submission
Scheduling Tool
Atmospheric Model
Sends scheduling
blocks (SBs) to M&C
system
SBs, including Control Scripts
Activation
event
Archive
EVLA M&C
Observing Layer
CALC
RTCAT output
- goes to the M&C system
- is archived
- is to be available to the Quick
Look Pipeline
- is to be available to the
Astronomer's What's Up Screen
MIB Devices
Cmnds
VCI
- Antenna gains
- Autophasing info
- pointing solutions
- focus determinations
Raw Antenna
Data
Monitor Data
Default Archive Image
Pipeline
CMIBs
WIDAR
Correlator
MCCC
Correlator
Back End
The EVLA SSR requires that the time-lag
between when data is collected by the realtime system or produced by the Quick-Look
Pipeline and when it is available to the "What's
Up" screen should be < 10 seconds.
Astronomer's
"What's Up"
Screen
Activation
event
Fast Data Store
Real-Time Calibrator
Analysis Tool
(RTCAT)
Shared
Memory
(?)
Formatter
Quick-Look Pipeline
(QLP)
Archive
Visibility Data
/users/bsahr/EVLA/architecture_design/overall_design/evla_m&c_e2e.vsd, 8/2003
The EVLA SSR requires that the time
between data collection by the real-time
system and its availability to the QLP be
< 30 seconds.
Requirements
We now have requirements produced by the NRAO user
community rather than Computer Division internally
generated documents.
•
•
•
•
•
EVLA e2e Science Software Requirements, April 15, 2003
EVLA Data Post-Processing Software Requirements, July 3, 2003
EVLA Array Operations Software Requirements, June 6, 2003
EVLA Engineering Software Requirements, August 8, 2003
EVLA Science Requirements for the Real-Time Software, to be started
9/2003
• Scientific Requirements for the EVLA Real-Time System, Sept, 2000
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
3
EVLA Antenna
EVLA M&C Software
LO
Antenna
Feed
Rcvr
Servo
IF System
Raw Antenna
Data
DTS
system parameters
database
(Oracle)
monitor data,
flagging, alarms
Monitor data
database
(Oracle)
Observing Layer
Archiver
control
scripts
(jython)
commands
PCN
r u x
v r t
Proxy
Server
real time
observation
queue
remote cmnds &
monitor data
configuration and
metadata
CALC
TCP/IP ?
CMIBs
VCI
MCCC
Prv
Cur
Nxt
Activation
event
Real-Time Calibrator
Analysis Tool
(RTCAT)
Ready
In
Progress
RTCAT output
- goes to the M&C system
- is archived
- to the Quick Look Pipeline
- to the Astronomer's What's Up
Screen
- Antenna gains
- Autophasing info
- pointing solutions
- focus determinations
/users/bsahr/EVLA/architecture_design/overall_design/evla_m&c_01.vsd 8/2003
WIDAR
Correlator
Correlator
Back End
Fast Data
Store
Shared
Memory
Formatter
Archive
Visibility Data
Correlator config,
metadata, ? via
CMIBS
CBE config &
metadata
monitor
data
Antenna MIBs
• MIB – Module Interface Board
– Refers to the TC11IB processor board that will be used
to control antenna subsystems
– 96 MHZ processor
– 1.5 Mbytes on-chip RAM
– 8 Mbytes Flash
– SPI bus
– GPIO (parallel I/O lines)
– Ethernet Interface
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
5
Antenna MIB Software
• Quality of the MIB software is seen as
crucial to the quality of the EVLA M&C
software
• The MIB software consists of:
– Systems software
– MIB framework software
– Module software
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
6
MIB Systems Software
• RTOS kernel
• Network stack
• Telnet server
– Automatically activates the shell
• Shell
– Shell provides memory display and memory modification
– Shell is being extended to provide module specific
commands & displays
• All of the systems software is up and running on MIB
hardware
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
7
MIB Framework Software
•
•
•
•
Common to all MIBs
Device definition, instantiation, and initialization
A data port, broadcasts monitor data
A service port
– Accepts time-tagged commands
– Information services
• C++, ASCII text, XML, Xpath (likely),
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
8
MIB Module Software
• HW module specific, chiefly written in C
• Responsible for
– Device Control
– Collection of monitor point values
– Warnings, errors, alarms
• L301 (12-20 GHZ synthesizer) module software has been
tested
• L302 (10.8-14.8 GHZ synthesizer) module software
currently under development
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
9
Device Browser
• Generic, discovery-based, remote client application
– Obtains a list of all devices connected to a MIB
– Obtains a list and description of all monitor and control points
associated with a device
•
•
•
•
•
Can display any/all monitor point values for a device
Can modify monitor point attributes
Can be used to command devices
Peek/Poke capabilities
Multiplatform, written in Java
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
10
ALMA/EVLA Cooperation
• At the low levels there is little commonality between the
AMLA & EVLA M&C systems. The differences are
driven by differences in the hardware.
• We hope sharing can occur at the higher levels of the two
systems.
• Ralph Marson of ALMA and I have agreed to begin
monthly meetings to explore the possibilities for sharing
designs and code at the higher levels of the two systems.
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
11
Questions/Issues
• Are we headed in the right direction ?
• Overall design ?
– Have we now positioned ourselves to produce a
high quality overall design?
Bill Sahr
EVLA Advisory Committee Meeting
September 8-9, 2003
12