[daip] New Ticket - [!SRH-788730]: UVAVG and sort-order

[Michael Bietenholz]

New Ticket: UVAVG and sort-order

UVAVG, with OPCO='', even when run on data that *is* in TB order, sometimes leaves data *not* in TB order.  I think it happens if say the first part of an averaging interval on some baseline is flagged.  Then theaveraged vis. record on that baseline gets a time-stamp that is out of sync with all the others baselines for that time interval and could leave things out of "T" order.

It should probably not mark its output data set as being in "TB" order when it is not.
Ideally it would check if this is happening and mark data as unsorted and alert user.

(I ran UVAVG on a data set which had been MSORTed to TB, output UV-file was marked 'TB'
but a subsequent INDXR failed  with: 
QUITTING: FILE CONTAINS DATA WHICH IS OUT OF TIME ORDER
All you have to do is MSORT the data again and you're fine.

Ticket Details
===================
Ticket ID: SRH-788730
Department: AIPS Data Processing
Priority: Default
Status: Open
Link:  https://help.nrao.edu/staff/index.php?_m=tickets&_a=viewticket&ticketid=2007