[evla-sw-discuss] Delay models to station boards

[Barry Clark]

It seems to me that we have reached agreement on the first two items
of the four part serial agenda I proposed a week ago.

> From evla-sw-discuss-bounces at donar.cv.nrao.edu  Wed May 14 10:29:27 2008
> From: Barry Clark <bclark at nrao.edu>
> 
> It seems to me that we need to do, in sequence,
> 1.  Reaffirm the long term direction we want to take.
> 2.  Decide how the short term implementation is to proceed.
> 3.  Establish shared use of the code repositories, especially for schema.
> 4.  Determine the details of the records to be passed.
> 

The answers seem to be:

1.  There will be an entity in the correlator software which receives
delay models from the Executor and passes them, unopened, to the appropriate
station board, according to some routing table, the maintenance methods of 
which are yet to be established.

2.  For the PTC, this entity will exist and forward according to a compiled
in routine table.

Proceeding to item 3, 
I suggest the appropriate repository for the schemata is 

https://svn.aoc.nrao.edu/repos/EVLA/commons/src/xsd

On the grounds that 
1.  This is what the component was established to do, 
2.  It is an important step in moving the correlator psychologically as 
    well as physically to New Mexico.  
3.  If it is to be elsewhere, to fit with our way of doing things, we 
    will need to allocate the labor to get a regular overnight compile
    running.  (Not me - I don't know how to talk to Maven and have no 
    desire to learn.  If I do it it will be with gmake, which nobody else
    will love.)

The addresses and ports to be used should be located in EVLAConstants.java
in the commons component.  (This particular class has an amusing dual
language feature - if you execute the main() method, it converts itself
into a C include file.)

In order to promode sharing of the parameters database, the Parameters
class should be moved from the observe component to the commons component.

Similar thought needs to be given to the commonalities of the OPT software.