Opened 17 years ago
Closed 15 years ago
#20 closed task (fixed)
ATLOD can handle known CABB birdies
| Reported by: | VincentMcIntyre | Owned by: | MarkWieringa |
|---|---|---|---|
| Priority: | major | Milestone: | 12. Stage 4 - available for testing |
| Component: | MIRIAD - CABB branch | Version: | |
| Keywords: | Cc: | ||
| Estimated Number of Hours: | Add Hours to Ticket: | ||
| Billable?: | no | Total Hours: | 8 |
Description (last modified by )
There will probably be some self-generated interference from CABB, as with the current correlator. ATLOD should be able to flag out the channels affected by this, automatically.
Change History (3)
comment:1 Changed 17 years ago by
| Priority: | minor → major |
|---|
comment:2 Changed 17 years ago by
| Billable?: | unset |
|---|---|
| Component: | prog → MIRIAD - CABB branch |
comment:3 Changed 15 years ago by
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
| Total Hours: | → 8 |
Note: See
TracTickets for help on using
tickets.
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.