[evla-sw-discuss] model propagation idea
Bruce Rowen
browen at nrao.edu
Tue May 20 15:23:02 EDT 2008
I spoke with Ken a bit about this on Monday and I agree the
enumerations I used for 'baseBandId' were a bit naive. For 8-bit
usage A, B, C, D work (ex. bb0 & 1 = A(right)) but for 3-bit usage a
single station board can have (for example) A1C1 (bb0=A1, bb1=C1). So
basically it 's better to just not even try 8^)
These were added to cover the case where a delay model document
needed to be forwarded to it's station board by a third party reading
the document. It looks like Kevin's testing/proposal makes this
unnecessary so I'll just drop the two attributes 'antennaId' and 'ifId'.
I'll revert the 'bbId' to reflect your 'bbIdType' which allows for 0-7.
Since the EVLA M&C knows the mapping (physical) of which model is to
be applied to which base band (data path), The CMIB will just place
the model into the base band (data path) that carries the matching
embedded identifier. This is what is currently done for the sub bands
(filters).
-Bruce
On May 20, 2008, at 12:54 PM, Sonja Vrcic wrote:
>
> I am afraid that this proposal introduces completely different
> terminology (IDs) from what we have agreed so far.
> In the VCI protocol, on the explicit request from the EVLA
> engineers, Antenna ID is defined as a string.
>
> Here is an example of the VCI message that assigns Station ID and
> Baseband IDs to the Station Board hardware.
>
> <stationHw id="1" >
> <basebandHw stationBoard="1-0-0" dataPath="0" source="FORM"
> sourceId="0" bbId="0" polarization="R"/>
> <basebandHw stationBoard="1-0-0" dataPath="1" source="FORM"
> sourceId="1" bbId="1" polarization="L"/>
> <basebandHw stationBoard="1-0-4" dataPath="0" source="FORM"
> sourceId="0" bbId="2" polarization="R"/>
> <basebandHw stationBoard="1-0-4" dataPath="1" source="FORM"
> sourceId="1" bbId="3" polarization="L"/>
> <basebandHw stationBoard="1-1-0" dataPath="0" source="FORM"
> sourceId="0" bbId="4" polarization="R"/>
> <basebandHw stationBoard="1-1-0" dataPath="1" source="FORM"
> sourceId="1" bbId="5" polarization="L"/>
> <basebandHw stationBoard="1-1-4" dataPath="0" source="FORM"
> sourceId="0" bbId="6" polarization="R"/>
> <basebandHw stationBoard="1-1-4" dataPath="1" source="FORM"
> sourceId="1" bbId="7" polarization="L"/>
> <antenna type="EVLA" id="Antenna_1"/>
> </stationHw>
>
>
> Detailed description of this message can be found in the VCI
> Protocol Specification available here:
> https://mitr.drao.nrc.ca/widar/private/Software.html
> For definition of the identifiers, please check WIDAR Correlator
> System Numbering Plan:
> https://mitr.drao.nrc.ca/widar/private/System.html
>
> 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.
>
> 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 (?!).
> 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. Interface ID (range: A, B, C or D) was
> not even identified as something that the correlator should be
> aware of. 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.
>
> Hardware IDs:
> StationBoard / DataPath / Filter ID
>
> DataStream IDs (arbitrarily assigned by the user/operator):
> Station / Baseband / Subband ID
>
>
> 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.
>
> Subband ID to Filter ID mapping will be normally selected by the
> correlator, and is not necessarily known by the Executor.
> Therefore, Delay Models should identify subband using either
> Station/Baseband/Subband IDs or
> StationBoard MLID (rack-crate-slot)/ DataPath / Subband ID.
>
> If we want to be purists and to use hardware IDs, then Executor
> should specify
> StationBoard MLID (rack-crate-slot)/ DataPath / Filter ID
> 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.
>
> Sonja
>
>
>
>
> Bruce Rowen wrote:
>>
>>> Does anybody have issues with this port mapping scheme or the
>>> unicast UDP between Executor and the VCI for the delay models ?
>> Slightly related, I've updated the model schema http://
>> www.aoc.nrao.edu/asg/widar/schemata/cmib/models/
>> 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.
>
>
>
>
>> -Bruce * following the lead of Steven Colbert
>>> Kevin _______________________________________________ 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
>
> -- 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
> Sonja.Vrcic at nrc-cnrc.gc.ca http://www.drao-ofr.hia-iha.nrc-cnrc.gc.ca/
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
More information about the evla-sw-discuss
mailing list