<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt><br>
I am afraid that this proposal introduces completely different
terminology (IDs) from what we have agreed so far. <br>
</tt><tt>In the VCI protocol,</tt><tt> on the explicit request from the
EVLA engineers, Antenna ID is defined as a string. <br>
<br>
Here is an example of the VCI message that assigns Station ID and
Baseband IDs to the Station Board hardware.<br>
<br>
<stationHw id="1" ><br>
<basebandHw stationBoard="1-0-0" dataPath="0" source="FORM"
sourceId="0" bbId="0" polarization="R"/><br>
<basebandHw stationBoard="1-0-0" dataPath="1" source="FORM"
sourceId="1" bbId="1" polarization="L"/><br>
<basebandHw stationBoard="1-0-4" dataPath="0" source="FORM"
sourceId="0" bbId="2" polarization="R"/><br>
<basebandHw stationBoard="1-0-4" dataPath="1" source="FORM"
sourceId="1" bbId="3" polarization="L"/><br>
<basebandHw stationBoard="1-1-0" dataPath="0" source="FORM"
sourceId="0" bbId="4" polarization="R"/><br>
<basebandHw stationBoard="1-1-0" dataPath="1" source="FORM"
sourceId="1" bbId="5" polarization="L"/><br>
<basebandHw stationBoard="1-1-4" dataPath="0" source="FORM"
sourceId="0" bbId="6" polarization="R"/><br>
<basebandHw stationBoard="1-1-4" dataPath="1" source="FORM"
sourceId="1" bbId="7" polarization="L"/><br>
<antenna type="EVLA" id="Antenna_1"/><br>
</stationHw><br>
<br>
<br>
</tt><tt>Detailed description of this message can be found in the VCI
Protocol Specification available here:<br>
<a class="moz-txt-link-freetext" href="https://mitr.drao.nrc.ca/widar/private/Software.html">https://mitr.drao.nrc.ca/widar/private/Software.html</a><br>
For definition of the identifiers, please check WIDAR Correlator System
Numbering Plan: <br>
<a class="moz-txt-link-freetext" href="https://mitr.drao.nrc.ca/widar/private/System.html">https://mitr.drao.nrc.ca/widar/private/System.html</a><br>
<br>
</tt><tt>I don't know which peace of the EVLA M&C software will
generate this
message (Executor, Observation Preparation or something else), but it
must have knowledge about antenna, FORM and Station Board hardware. I
presume that, during the testing, this information will be entered by
the user (probably using some GUI.<br>
</tt><br>
<tt>It seems to me very dangerous to have Baseband ID mean two
different things in the VCI configuration and in the Delay Model
messages, even if you don't consider Delay Models part of VCI (?!).<br>
We agreed long ago that Station ID (range 1 - 255) will be assigned by
the EVLA M&C as specified above, and that Baseband ID is an integer
in the range 1 to 7. </tt><tt>Interface ID (range: A, B, C or D) was
not even identified as something that the correlator should be aware of.</tt><tt>
If you really want to have hardware oriented IDs in the Delay Models,
use terminology as defined in VCI, otherwise we will have a terrible
confusion. <br>
<br>
Hardware IDs:<br>
StationBoard / DataPath / Filter ID<br>
<br>
DataStream IDs (arbitrarily assigned by the user/operator):</tt><br>
<tt>Station / Baseband / Subband ID<br>
<br>
<br>
Mapping of Station ID and Baseband ID into Station Board hardware
(Rack-Crate-Slot DataPath) is specified (and therefore known) by the
EVLA M&C. <br>
<br>
Subband ID to Filter ID mapping will be normally selected by the
correlator, and is not necessarily known by the Executor. <br>
Therefore, Delay Models should identify subband using either
Station/Baseband/Subband IDs or <br>
</tt><tt>StationBoard MLID (rack-crate-slot)/ DataPath / Subband ID</tt><tt>.
<br>
<br>
If we want to be purists<b> and </b>to use hardware IDs, then Executor
should specify <br>
</tt><tt>StationBoard MLID (rack-crate-slot)/ DataPath / Filter ID<br>
During the testing Filter ID will be selected by the user (via GUI),
later Executor may get Filter ID from the MCCC and use it in the delay
Models. <br>
</tt><tt><br>
Sonja <br>
<br>
</tt><tt><br>
<br>
</tt><br>
Bruce Rowen wrote:
<blockquote cite="mid:218678F3-93E3-42F6-A213-2FF2CA5778CA@aoc.nrao.edu"
type="cite">
<blockquote type="cite">
<pre wrap="">Does anybody have issues with this port mapping scheme or the unicast
UDP between Executor and the VCI for the delay models ?
</pre>
</blockquote>
<pre wrap=""><!---->
Slightly related, I've updated the model schema
<a class="moz-txt-link-freetext" href="http://www.aoc.nrao.edu/asg/widar/schemata/cmib/models/">http://www.aoc.nrao.edu/asg/widar/schemata/cmib/models/</a>
vciDelayModelBeta.html
to include optional parameters 'antennaId' [1-32] and 'ifId' [A-D]
should it be for whatever reason we decide to peek inside the XML
documents received at the MCCC. These attributes would allow for the
MCCC document reader to determine which antenna/IF the model is
intended for.
These parameters are optional so they should not be included unless
we go that route.
'baseBandId' [0-1] is still logical and we might consider making it
[R | L] (right/left) or even something more removed from plain
numbers just to improve the 'logicalness'* of it.
</pre>
</blockquote>
<br>
<br>
<br>
<br>
<blockquote cite="mid:218678F3-93E3-42F6-A213-2FF2CA5778CA@aoc.nrao.edu"
type="cite">
<pre wrap="">
-Bruce
* following the lead of Steven Colbert
</pre>
</blockquote>
<blockquote cite="mid:218678F3-93E3-42F6-A213-2FF2CA5778CA@aoc.nrao.edu"
type="cite">
<blockquote type="cite">
<pre wrap="">
Kevin
_______________________________________________
evla-sw-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:evla-sw-discuss@listmgr.cv.nrao.edu">evla-sw-discuss@listmgr.cv.nrao.edu</a>
<a class="moz-txt-link-freetext" href="http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss">http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
evla-sw-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:evla-sw-discuss@listmgr.cv.nrao.edu">evla-sw-discuss@listmgr.cv.nrao.edu</a>
<a class="moz-txt-link-freetext" href="http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss">http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="90">--
Sonja Vrcic
Software Engineer
National Research Council
Herzberg Institute of Astrophysics
Dominion Radio Astrophysical Observatory,
Penticton, BC, Canada
Tel:(250)490-4309/(250)493-2277ext.309
<a class="moz-txt-link-abbreviated" href="mailto:Sonja.Vrcic@nrc-cnrc.gc.ca">Sonja.Vrcic@nrc-cnrc.gc.ca</a>
<a class="moz-txt-link-freetext" href="http://www.drao-ofr.hia-iha.nrc-cnrc.gc.ca/">http://www.drao-ofr.hia-iha.nrc-cnrc.gc.ca/</a>
</pre>
</body>
</html>