Opened 15 years ago

Closed 15 years ago

#82 closed defect (fixed)

Flow-on effects of including autocorrelations

Reported by: VincentMcIntyre Owned by: MarkWieringa
Priority: major Milestone: 11a. Release Stage 2
Component: MIRIAD - CABB branch Version:
Keywords: autocorrelation Cc:
Estimated Number of Hours: 1 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0

Description

If you atlod with options=noauto, the autocorrelations are still loaded. This leads to some confusion when running tasks like {{blflag}}} & uvplt.

Is this a bug or a feature? What changes should be made to miriad:

  • Should atlod no longer have options=noauto?
  • Should tasks like blflag be modified to ignore autocorrelations

(eg we could add options=noauto) ?

  • Or should we just change the manual and tell users to adjust their procedures?

Change History (2)

comment:1 Changed 15 years ago by VincentMcIntyre

see also ticket:76

comment:2 Changed 15 years ago by MarkWieringa

Resolution: → fixed
Status: new → closed

options=noauto has been restored. Future versions of atlod may need to include auto correlation data if we want to redo the online tsys calibration. The information for this is stored in bin 1 and 2 of the autocorrelations.

Note: See TracTickets for help on using tickets.