Opened 14 years ago
Closed 14 years ago
#117 closed enhancement (fixed)
atlod rfiflag L/S range needs to be updated
| Reported by: | JamieStevens | Owned by: | MarkWieringa |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | MIRIAD - CABB branch | Version: | |
| Keywords: | atlod lband sband | Cc: | |
| Estimated Number of Hours: | 0 | Add Hours to Ticket: | 2 |
| Billable?: | yes | Total Hours: | 0 |
Description
With 4 out of the 5 L/S receivers currently on the array being the wideband type, it is time to update atlod to stop it cutting out too much of the usable band.
Currently, when 'options=birdie,rfiflag' is specified to atlod while loading L data, the band outside the range 1.2 - 1.9 GHz is flagged. I propose that the full 1.1 - 3.1 GHz range be made available.
This will probably have to be date-dependent, to support old CABB data. I think all L/S data after 17th August 2010 can be assumed to have the entire L/S range usable for antennas 2,3,4 and 6. At this time, CA01 still has the old L/S band receiver, and antennas 1 & 5 will be upgraded by 22nd October 2010.
Change History (1)
comment:1 Changed 14 years ago by
| Add Hours to Ticket: | 0 → 2 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Done. Atlod has been updated as requested. The birdie option just flags the bottom and top 100 channels. rfiflag flags additional bad frequency ranges. After we get some experience with observing in the 1.1-3.1 GHz band we may want to exclude some more ranges in the previously unused parts of the band.