Changes between Initial Version and Version 3 of Ticket #20


Ignore:
Timestamp:
06/12/09 13:57:28 (15 years ago)
Author:
MarkWieringa
Comment:

It turns out that there are quite a few internal RFI issues with CABB, most of these are fixed channels (regardless of frequency) in the CABB band. Because CABB uses this data for online delay calibration, they need to be flagged out on-line. Thus the worst RFI is already flagged by the time it gets to atlod. A separate approach was implemented for atlod (option=rfiflag) which lets you specify a number of frequency ranges to flag in a file.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #20

    • Property Status changed from new to closed
    • Property Total Hours changed from to 8
    • Property Component changed from prog to MIRIAD - CABB branch
    • Property Priority changed from minor to major
    • Property Billable? unset
    • Property Resolution changed from to fixed

  • Ticket #20 – Description

    initial v3  
    1 
    21There will probably be some self-generated interference from CABB, as with the current correlator.
    32ATLOD should be able to flag out the channels affected by this, automatically.