[evlatests] Q-band masquerade!

[Bryan Butler]

or, the executor never sent the document.


Walter Brisken wrote:
> Something disturbing might have happened here.  The executor log clearly 
> states:
> 
> INFO: 102apevla 54381 185737 obs2script: setting up source 1642+398 at 
> 45GHz    [source #10]
> 
> And based on Rick's data it is clear that the antennas were commanded into 
> Q-band.
> 
> BUT  Idcaf logs show no sign of an Observation document specifying 45 GHz 
> for this project.  The first thing IDCAF does when it gets an Observation 
> record is write its contents to the log, so it is very unlikely that IDCAF 
> chose to ignore a command that it got.  Instead I worry that this 
> document, which was multicast from the executor, never made it to IDCAF. 
> If multicast packets are being dropped, this could explain some of the 
> eratic behavior that has been reported recently.
> 
> -Walter
> 
> 
> On Mon, 8 Oct 2007, Rick Perley wrote:
> 
>>    Eric suggested filling the data only over the timerange during which
>> the system was known to be at Q-band.
>>    This has been done, (and I added 30 seconds to the start time, just
>> to be sure ...) and it is filled as if it were K-band data, with the
>> default K-band frequencies.
>>
>>
>>
>> Eric Greisen wrote:
>>> Try fillm with exactly the Q time range and see what it is then
>>> called.
>>>
>>> Eric
>>>
>> _______________________________________________
>> evlatests mailing list
>> evlatests at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
>>
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests