AOFlagger
Static Public Attributes | List of all members
aoflagger::StrategyFlags Class Reference

Lists the flags that can be used to alter a default strategy. More...

#include <aoflagger.h>

Static Public Attributes

static const unsigned AUTO_CORRELATION
 Erase any flags that are already set. More...
 
static const unsigned FAST
 Optimize for speed at cost of accuracy and robustness.
 
static const unsigned HIGH_TIME_RESOLUTION
 Optimizes for observations with high time resolution. More...
 
static const unsigned INSENSITIVE
 Make the strategy less sensitive to RFI than the default telescope settings. More...
 
static const unsigned LARGE_BANDWIDTH
 Observation was made at larger bandwidth than common. More...
 
static const unsigned NONE
 No flags: use the default strategy for the telescope.
 
static const unsigned ROBUST
 Increase robustness by decreasing convergence speed. More...
 
static const unsigned SENSITIVE
 Make the strategy more sensitive to RFI than the default telescope settings. More...
 
static const unsigned SMALL_BANDWIDTH
 Observation was made at smaller bandwidth than common.
 
static const unsigned TRANSIENTS
 Make strategy insensitive for transient effect. More...
 
static const unsigned USE_ORIGINAL_FLAGS
 Will assume that the original flags that are already set in the observation denote bad data and should be ignored. For example, certain observatory correlators output flagged data when the data from an antenna is (temporarily) not received.
 

Detailed Description

Lists the flags that can be used to alter a default strategy.

These flags can have different effects on strategies for different telescopes. Some might only have effect for specific telescopes, i.e., specific values of TelescopeId. Flags can be combined with the arithmetic 'OR' ('|') operator.

See also
AOFlagger::MakeStrategy()

Member Data Documentation

◆ AUTO_CORRELATION

const unsigned aoflagger::StrategyFlags::AUTO_CORRELATION
static

Erase any flags that are already set.

If this flag is not specified, the flags that have already been set will be combined with the flags found by the flagger.

Optimize for auto-correlations.

◆ HIGH_TIME_RESOLUTION

const unsigned aoflagger::StrategyFlags::HIGH_TIME_RESOLUTION
static

Optimizes for observations with high time resolution.

Observations with a high time resolution are those that are sampled much faster than the typical second-scale resolution required for imaging observations. Examples are observations for fast pulsars or fast radio burst.

◆ INSENSITIVE

const unsigned aoflagger::StrategyFlags::INSENSITIVE
static

Make the strategy less sensitive to RFI than the default telescope settings.

Can be used if the flagger seems to destroy too much data. In this case, you might consider also using ROBUST instead.

◆ LARGE_BANDWIDTH

const unsigned aoflagger::StrategyFlags::LARGE_BANDWIDTH
static

Observation was made at larger bandwidth than common.

Depending on the telescope, this might e.g. try to divide frequency dependent power out before flagging.

◆ ROBUST

const unsigned aoflagger::StrategyFlags::ROBUST
static

Increase robustness by decreasing convergence speed.

This flag trades flagging speed for better convergence properties, which might be useful when having a large dynamic range in RFI or the default strategy is not working well. Opposite of FAST.

◆ SENSITIVE

const unsigned aoflagger::StrategyFlags::SENSITIVE
static

Make the strategy more sensitive to RFI than the default telescope settings.

This creates also more false positives, but might be useful if the default setting seems to leave too much RFI in. Opposite of SENSITIVE.

◆ TRANSIENTS

const unsigned aoflagger::StrategyFlags::TRANSIENTS
static

Make strategy insensitive for transient effect.

This would make the strategy insensitive to RFI that is broadband but rapidly changes over time. This could be useful when searching for transients. Note that many celestial transients, such as most pulsars, are not strong enough to be noticable on high resolution, and the loss in RFI sensitivity is quite severe, so it is advisable to play around with strategies when optimizing for transient detections.


The documentation for this class was generated from the following file: