... minimization^1.1

In practice, the CORRECTED_DATA column isn't used until corrected data intended for imaging is desired; the observed data is corrected on-the-fly by the uv-plane solver.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... correction^1.2

If the dataset has not been observed for polarization imaging, or if polarization imaging is not desired, the application of P can be omitted and the parallactic angle will be implicitly subsumed into the G calibration. In any case, it is important to be consistent with regard to application of P.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... image^1.3

The means of forming reliable images from marginally calibrated data involves careful use of deconvolution mechanisms and is described in the Imager documenation.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... time^1.4

Ambitious users may wish to avoid this problem in the short term by copying calibrated data from the CORRECTED_DATA column to the DATA column. This is not recommended, in general, since it the original data is lost (unless it is copied to an additional column). It will be unnecessary in the near future when incremental calibration comes online.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.