[evlatests] Multiple Configurations ...

[Rich Moeser]

On 01/26/2016 11:25 AM, Ken Sowinski wrote:
> On Tue, 26 Jan 2016, Rick Perley wrote:
>
>>    The explanation for the multiple 'configurations' is clear, but
>> another question is raised ...
>>
>>    There were 5 antennas moved yesterday.  It's clear that each time
>> an antenna was taken out, another 'configuration' was made.  At
>> P-band, five different configurations resulted.
>>
>>    However, the antenna files for each of the five are identical --
>> the fact that antennas were taken out of service for a while, then
>> reappeared later in a different place, didn't reach the Executor.
>> Indeed, the first of the five P-band files contains the data taken at
>> the beginning of the run (with all 27 antennas in the original
>> positions), and the data at the end of the run, when five of them were
>> in new positions.  The other four databases all correspond to short
>> periods of time during which the actual number of antennas available
>> was less than 27.  Yet all five databases have the same AN file.
>>
>>    There's no harm in this, as the new antennas provided no fringes
>> after having been replanted.
>
> I checked with the operator of yesterday who verified that when the
> antennas were put back in service (whether they should have been is
> another question) parminator and the executor were updated to the
> new pad.  If, as Rick reports, the moved antennas appear to be at
> their original pads, then MCAF or the filler chain must have caused it.

MCAF was not aware that any moves took place. The pad values in the 
AntennaPropertyTable documents for the moved antennas were identical to 
those prior to the moves.

-Rich

>
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.nrao.edu
> https://listmgr.nrao.edu/mailman/listinfo/evlatests