Opened 17 years ago
Closed 16 years ago
#23 closed task (fixed)
Do not try to autoflag CABB data based on sampler statistics
| Reported by: | VincentMcIntyre | Owned by: | MarkWieringa |
|---|---|---|---|
| Priority: | major | Milestone: | 7. Stage 1 - available for testing |
| Component: | MIRIAD - CABB branch | Version: | |
| Keywords: | Cc: | ||
| Estimated Number of Hours: | 7 | Add Hours to Ticket: | 0 |
| Billable?: | no | Total Hours: | 7.0 |
Description
Sampler statistics will not be present in CABB data, so ATLOD should not try to flag the data using sampler statistics.
See also Changes/atlod
Change History (4)
comment:1 Changed 17 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 17 years ago by
comment:3 Changed 17 years ago by
| Billable?: | unset |
|---|---|
| Component: | prog → MIRIAD - CABB branch |
comment:4 Changed 16 years ago by
| Add Hours to Ticket: | → 7 |
|---|---|
| Estimated Number of Hours: | → 7 |
| Resolution: | → fixed |
| Status: | assigned → closed |
| Total Hours: | 0 → 7.0 |
A cabb flag has been added to atlod. It gets turned on when any of the incoming data has a bandwidth >300MHz. This flag is used to prevent any use of sampler stats for flagging.
Note: See
TracTickets for help on using
tickets.
A quick fix for this is to use: options=relax in atlod, this works fine for MOPS data. Once we get some real CABB data, we can make atlod recognize this automatically.