[evlatests] VLA archive oddities

[Rick Perley]

    ???  AB1248, when I filled it, shows a code of 'AB124', not 'AL0124'. 
    I'm confused ...

    Concerning AL693:

    The oddity is due to the observers using two frequencies, with two 
different bandwidths.  The odd datapoint noted by Michael is the 
'cross-product' between them -- change of frequency without change of 
bandwidth (or vice versa).  Some snipped of data has been mislabeled.  
It's flagged as bad, and never made it to the output file.  No serious 
harm...

    Rick

Michael Rupen wrote:
> Hello folks,
>
>    the modcomp-free data appears rather oddly in the VLA archive.
>
> * AL693 from June 28, a continuous single-subarray run of 8 hours not
>    crossing IAT midnight, shows up as two overlapping files.
>    - Loading these two data sets into AIPS, the data from the overlapping
>      time range seems to be the same.  One obvious oddity is that there is
>      a change in frequency (and consequently FQID) at the time the second data
>      set starts.  There are however 0 visibilities with this "odd" FQID.
>
> * AB1248 shows up with the wrong project code (AL0124), consistent
>    with the naming problems others have mentioned.  NOTE however that
>    messing up the project codes for "real" data is much more serious than
>    doing so for test runs:
>    - The observer will not be able to find his/her data simply by checking
>      the project code reported in the log he/she receives.
>    - The password will be different for different names.
>    - In particularly nasty cases the mis-modified project code may actually
>      overlap with an existing one.
>
> * The configuration (should be "A") is set to "?"
>
> TTFN,
>
>              Michael
>
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
>