Transcript Document 7637228

Master Correlator Control Computer
(MCCC)
Requirements & Status
Sonja Vrcic
N ational R esearch Council
Canada
Conseil national de recherches
Canada
Socorro, December 12, 2007
Outline
• There is a bit of confusion when it comes to terms & acronyms, this
presentation provides definition for MCCC, VCI & Configuration Mapper.
• Requirements for the various stages of testing.
• Questions. Are there any issues ?
The diagrams used in this presentation are copied from the NRAO document:
“WIDAR Prototype Correlator, Schedules, Testbeds, Software” Version 3.0
Author: Bill Sahr
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
2
Definitions
•
•
•
•
•
•
Master Correlator Control Computer (MCCC) is of the shelf computer system
running software that provides a single point of access for monitoring &
controlling the correlator.
Virtual Correlator Interface (VCI) is an interface between the correlator and the
user.
In the EVLA system, the user is Observation Executor, but user can be any
software application able to generate and transmit VCI messages.
VCI is a protocol (a set of rules) that defines content and format of the messages
exchanged between the user and WIDAR correlator. VCI also includes (defines)
underlining transport protocol.
In the WIDAR correlator, software that implements VCI is running on the MCCC.
Configuration Mapper:
– Is a software package that implements part of VCI protocol relevant to configuration of
the correlator.
– It translates VCI configuration messages into configuration of the correlator
subsystems: Station Board, Baseline Boards, Switching Boards, Backend, etc.
– Configures correlator subsystems as required and maintains correlator status.
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
3
Timeline
The following two diagrams show configuration for:
1.
Critical on-the-sky testing needed to prove that hardware is working.
– Initial plan for this phase (currently scheduled for mid Aug. 2008) was to use
test tools (Test Builder & Test Executor) for configuration and monitoring.
– Delay models are generated by Antenna System, therefore MCCC & Station
Board CMIB must be able to accept models in XML format.
– MCCC Model Server is simply forwarding models to the Station Board
(implementation is simple).
– There are some opinions that, VCI is needed in this phase in order to fully
integrate Antenna System, Correlator and SDM.
2.
System Integration (may start in June 2008, if hardware is delivered to VLA) and
limited observing.
For that phase MCCC should provide:
1.
2.
3.
4.
Configuration Mapper
Correlator Status
Model Server
Logger
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
4
Critical On-The-Sky Testing (aka Critical Hardware Tests) – Aug. 2008
Note: For the full correlator, the ancillary
data products will include Phasing data.
EVLA
Antennas
To FORM brds
To VLA
Antennas
PTC Data Products
Archive: unspecified
type & format
From FORM brds
- correl config
(config mapper)
- models
- dumptrig params
- other ?
Control
script
MCCC
Obs
Executor
Ant
Servers
models
Ethernet
V
C
I
BLB auxiliary data products
(CMIB streaming)
External timecode
& 128 MHz CW
StB science meta-data
(CMIB streaming)
StB auxiliary data products
(CMIB streaming)
To PTC Data
Products
Archive
To RTDD ? To various analysis programs.
Implies the existence of data retrieval
methods/software.
Ethernet
state counts (StB)
Ethernet
10 Stn PTC
Model
Hndlr
C
M
I
B
s
Ethernet,
To StB
CMIBs
C
M
I
B
Proto CBE/FF
Slave
Node
Processes
Lag
Frames
FORM
CMIB
Station Brd
(StB)
HM
Gbps
Meta-data
from
Obs
Executor
?
science meta-data
(StB & BLB ?)
Ethernet
Baseline
Brd (BLB)
Slave
Node
Processes
Slave
Node
Processes
Master
Node
Processes
BDF
Table
Data
PTC
MCAF
Pltfrm
Ethernet
MChost
Ethernet
For the OTS Critical Tests, the PTC is configured
via the System, Rack, and Board level GUIs running
on the PTC Host Computer. The only required
integration with the EVLA M&C System is that high
level models flow from the Observation Executor/
Antenna Servers.
Visibilities
(BDF)
Lag Sets
(BDF)
CMIBs
Lag Frames
Ethernet,
To CMIBs
Minimal
SDM ?
Test Executor
Test Builder
Visibility Archive
System, Rack, & Board
Level GUIs
CBE Config IF
RTDD
PTC Host Cmptr
C
B
E
PTC Data
Products
Archive
Other data
sources ?
Analysis pgms:
- AIPS
- CASA
- Intellig Diff for test vectors
- Other ?
NRAO archive,
special purpose
database, file
hierarchy, or some
combination of
these items ?
Data retrieval, by software &
by users is required.
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
5
System Integration (possibly June2008), Limited Observing - Q3 2008,
Note: For the full correlator, the ancillary
data products will include Phasing data.
EVLA
Antennas
To FORM brds
To VLA
Antennas
Msg Hndlr
Ethernet
V
C
I
Model
Hndlr
Status
Ethernet
state counts (StB)
Ethernet
10 Stn PTC
Ethernet,
To StB
CMIBs
C
M
I
B
Proto CBE/FF
Slave
Node
Processes
Lag
Frames
FORM
CMIB
Station Brd
(StB)
HM
Gbps
Ethernet
Baseline
Brd (BLB)
Slave
Node
Processes
Msg
Hndlr
C
B
E
Master
Node
Processes
Slave
Node
Processes
Ethernet
config
BDF
Table
Data
PTC
MCAF
Pltfrm
CMIBs
Archive
Records:
SDM
Visibilities
(BDF)
Ethernet,
To CMIBs
Lag Frames
status
alerts
Lag Sets
(BDF)
- status
- alerts
- real-time
data products
science meta-data
(StB & BLB ?)
Ethernet
Logs/
Alerts
MChost
C
M
I
B
s
- Meta-data from
Obs Executor
- EVLA M&C
alerts
- EVLA M&C
monitor data
To RTDD ? To various analysis programs.
Implies the existence of data retrieval
methods/software.
BLB auxiliary data products
(CMIB streaming)
MCCC
StB science meta-data
(CMIB streaming)
Ethernet
External timecode
& 128 MHz CW
- correl config
(config mapper)
- models
- dumptrig params
- other ?
Cnfig
Mappr
Obs
Executor
Ant
Servers
StB auxiliary data products
(CMIB streaming)
To PTC Data
Products
Archive
Control
script
- correl config
requests
- CBE config
requests
- models
- dumptrig params
- status requests
PTC Data Products
Archive: unspecified
type & format
From FORM brds
Test Executor
Test Builder
Visibility Archive
System, Rack, & Board
Level GUIs
CBE Config IF
RTDD
PTC Host Cmptr
C
B
E
Ethernet
SDM
PTC Data
Products
Archive
Other data
sources ?
AIPS
CASA
UVFITS
Data retrieval, by software &
by users is required.
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
The standard NRAO
archive, located at
the AOC or a special
archive, possibly
located at the VLA
site ?
6
Status
1.
2.
3.
4.
5.
6.
7.
8.
9.
Still need to define the final version of VCI protocol.
Need to define priorities for implementation of the Configuration Mapper.
In order to configure the correlator using Configuration Mapper we need
Observation Executor and CMIB software that can process configuration
generated by the Configuration Mapper.
Need a GUI tool able to provide visual representation of the correlator. Such tool
would be used for testing of the Configuration Mapper and Observation Executor.
Much of the existing Configuration Mapper code need to be re-written, but
provides a good basis for the final implementation. Should be able to provide a
basic functionality till mid 2008.
Testing of the interface between Configuration Mapper and Observation Executor
should start in June 2008, if not earlier.
Basic implementation of the Model Server will be available in June 2008.
Correlator status may not be available, may need to manually enter status, and
rely on Board & System level GUIs for monitoring.
The ability to provide logs for all the correlator subsystems will not be available
in June 2008. Need to consider deliverables in more detail.
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
7
Plan for the next week
•
•
•
Need to define a final version of VCI, i.e. the interface between the correlator and
the rest of the system (for EVLA that’s Observation Executor).
Over next 4 work days (and perhaps weekend) requirements for the VCI and
Configuration Mapper will be discussed in detail.
The following documents will be basis for the discussion:
–
–
Presentation “WIDAR configuration for the interested user”
Configuration Mapper RFS and
–
VCI Protocol Specification, Version 3.0
Objective:
•
•
Define as much details as possible: complete list of parameters for various
functions/modes, range and format for each parameter.
Define priorities, i.e. functionality needed for critical tests (recirculation, pulsar
binning, pulsar gating, burst mode, etc).
Sonja Vrcic, Dec 12, 2007
MCCC Requirements & Schedule
8