[evla-sw-discuss] Software System Design

Kevin Ryan kryan at nrao.edu
Thu Oct 1 11:52:05 EDT 2009


On Sep 30, 2009, at 11:42 AM, Barry Clark wrote:

> Suggested system design
> ...
>
> 12.  Alerts will be multicast in the same fashion as antenna alerts,
> for the same purposes.  It may be necessary to have an alert forwarder
> within the correlator system to provide translation to understandable
> antenna and subband identifications, although Station Boards probably
> have enough information to be able to construct an alert.

I'm hoping this is meant just for simple things like logging/archiving  
and not as a basis of acquiring system state for control/monitor  
purposes.

The MCCC should provide an operator user interface for the functional  
operation of the correlator in a manner similar to that provided by  
CPCC for the correlator's physical control/monitor (power,  
temperature, smoke alarms, power plant ...).

WIDAR has a nice package of REST/HTTP communication classes that are  
mature and tested and that can easily be used by EVLA components for  
WIDAR interface purposes and everyone is certainly welcome to use them.

> 13.  Delay polynomials will be transmitted from the Executor in the
> current fashion, and distributed as now, with the expectation that
> eventually the polynomial distributor will need information from the
> ResourceManager to know where to send them.

Currently the CPCC is doing this but it really should be relieved of  
this duty by MCCC at some convenient point in time.

Kevin




More information about the evla-sw-discuss mailing list