pipeline.hif.cli.gotasks.hif_lowgainflag

pipeline.hif.cli.gotasks.hif_lowgainflag = <pipeline.hif.cli.gotasks.hif_lowgainflag._hif_lowgainflag object>

hif_lowgainflag —- Flag antennas with low or high gain

Flag antennas with unusually low or high gain.

Deviant antennas are detected by analysis of a view showing their calibration gains. This view is a list of 2D images with axes ‘Time’ and ‘Antenna’; there is one image for each spectral window and intent. A flagcmd to flag all data for an antenna will be generated by any gain that is outside the range [fnm_lo_limit * median, fnm_hi_limit * median].

Output

results – If pipeline mode is ‘getinputs’ then None is returned. Otherwise the results object for the pipeline task is returned.

——— parameter descriptions ———————————————

vis The list of input MeasurementSets. Defaults to the list of

MeasurementSets specified in the h_init or hif_importdata task. ‘’: use all MeasurementSets in the context

Examples: ‘ngc5921.ms’, [‘ngc5921a.ms’, ngc5921b.ms’, ‘ngc5921c.ms’]

intent A string containing the list of intents to be checked for

antennas with deviant gains. The default is blank, which causes the task to select the ‘BANDPASS’ intent.

spw The list of spectral windows and channels to which the

calibration will be applied. Defaults to all science windows in the pipeline context.

Examples: spw=’17’, spw=’11, 15’

refant A string containing a prioritized list of reference antenna

name(s) to be used to produce the gain table. Defaults to the value(s) stored in the pipeline context. If undefined in the pipeline context defaults to the CASA reference antenna naming scheme.

Examples: refant=’DV01’, refant=’DV06,DV07’

flag_nmedian True to flag figures of merit greater than

fnm_hi_limit * median or lower than fnm_lo_limit * median.

fnm_lo_limit Flag values lower than fnm_lo_limit * median fnm_hi_limit Flag values higher than fnm_hi_limit * median pipelinemode The pipeline operating mode.

In ‘automatic’ mode the pipeline determines the values of all context defined pipeline inputs automatically. In ‘interactive’ mode the user can set the pipeline context defined parameters manually. In ‘getinputs’ mode the user can check the settings of all pipeline parameters without running the task.

dryrun Run the task (False) or just display the command (True) acceptresults Add the results of the task to the pipeline context (True) or

reject them (False).

——— examples ———————————————————–