[evlatests] Initialization problems

[Walter Brisken]

The first integration labeling issue is puzzling to me.  I've gone over 
the idcaf code related to this again and it seems reasonable.  If an 
integration time ends in a new scan, it should be labeled as the new scan, 
but flagged for the first integration.  Can someone point me to a dataset 
where there is a supposed first integration labeling problem?  do we know 
if it is the beginning or the end of the target source scan that has the 
leakage from the calibrator?  The beginning is the only way I can see that 
making any sense.

Rick -- for this new problem, can you tell me the experiment name and the 
time (UT prefered) that you saw incorrect frequencies so I can look at the 
IDCAF logs to see what it thought was going on?

Thanks,

Walter

On Fri, 29 Aug 2008, Ken Sowinski wrote:

> On Fri, 29 Aug 2008, Rick Perley wrote:
>
>>    All of these tests involve short observations of multiple sources at
>> multiple frequencies and bands.  For all these tests -- with a single
>> exception-- the first observation is at P-band, in continuum, with
>> requested frequencies of 327.5 and 307.5 MHz, and a bandwidth of 3.125MHz.
>
> It looks like this has the same cause as the problem that idcaf
> with the first scan if the correlator setup changes from the first
> to second scan of a file.  Have we ever determined whether idcaf is
> confused about what it is told or the executor is misinforming it?
>
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
>