[ Basic Info | References | User Guide ]
Basic Information on uvaflag
Task: uvaflag
Purpose: Use flags in one visibility dataset to flag another.
Categories: calibration
UVAFLAG is a MIRIAD task which flags correlations in one
visibility dataset based on the flag status of matching
correlations in a template dataset.
The template dataset should be a subset of the visibility dataset
being flagged, and the order of records in the two datasets should
be the same. Normally correlations in the template and visibility
datasets are matched by comparing time, polarisation, baseline and
frequency. However options `nopol' and `nofreq' can turn off the
matching of polarisation and frequency.
Key: vis
The input visibility file to be flagged. No default.
Key: tvis
The template input visibility file. The default is the same
as the `vis' dataset. This default makes no sense without the `nopol'
or `nofreq' options. Several files can be given. Wildcards
are supported.
Key: select
Normal visibility selection, which is applied to the template
dataset. See the help on select for more information.
Key: options
Extra processing options. Several can be given, separated by commas.
Minimum match is supported. Possible values are:
nopol The polarisation of the records in the template are
ignored. If any polarisation in the template is
flagged, then all polarisations in the input are flagged.
This can be useful when applying flagging based on one
polarisation type (e.g. stokes V) to the other polarisations.
nofreq The frequency of the correlations in the template are
ignored. If any channel in the template is flagged, then
all channels in the input are flagged. This can be useful
when applying flagging based on a `channel-0' dataset.
noapply Do not apply the flagging, just report the statistics
about what would be flagged.