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

[Rich Moeser]

Correction...
The WIDAR schema files are at 
https://svn.aoc.nrao.edu/repos/widar/trunk/schema/

Rich Moeser wrote:
> The schema files for WIDAR are available at 
> https://svn.aoc.nrao.edu/repos/WIDAR/schema so I don't think it's 
> necessary to copy those to the EVLA SVN repository. I've set up a 
> prototype maven project that takes the schemata from the WIDAR SVN 
> repository, runs it through the JAXB compiler, and bundles the resulting 
> JAXB classes into a standalone jar file. This is pretty much the same 
> approach I have taken with the ALMA SDM schemata and it works just fine.
>
> The Javadoc for the JAXB classes is at 
> http://www.aoc.nrao.edu/asg-internal/software/evla/javadoc/widar-schema/05212008-snapshot/apidocs.
>
> To use these classes you must add the following dependency to your 
> project pom.xml file:
>     <dependency>
>       <groupId>nrao</groupId>
>       <artifactId>widar-schema</artifactId>
>       <version>05212008-snapshot</version>
>     </dependency>
>
> To use the JAXB classes in your Java code you must include the import 
> statement "import edu.nrao.evla.widar.xml.jaxb.*;".
>
> The JAXB classes included in the jar file are from the following schema 
> files:
> vciCommon.xsd
> vciDelayModel.xsd
> vciRequest.xsd
> vciResponse.xsd
> widarCommon.xsd
>
> --Rich
>
> Barry Clark wrote:
>   
>> 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.
>> _______________________________________________
>> evla-sw-discuss mailing list
>> evla-sw-discuss at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
>>   
>>     
>
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
>