By default, the bounds of the output pixel grid are chosen so that they just encompass all the transformed input data, but they can be set explicitly using Parameters LBOUND and UBOUND.
Two algorithms are available for determining the output pixel values: resampling and rebinning (the method used is determined by the REBIN parameter).
The Mapping to use can be supplied in several different ways (see Parameter MAPPING).
PARAMS(1) is required by all the above schemes. It is used to specify how many pixels are to contribute to the interpolated result on either side of the interpolation or binning point in each dimension. Typically, a value of 2 is appropriate and the minimum allowed value is 1 (i.e. one pixel on each side). A value of zero or fewer indicates that a suitable number of pixels should be calculated automatically. [0]
PARAMS(2) is required only by the Gauss, SincSinc, SincCos, and SincGauss schemes. For the SombCos, SincSinc, and SincCos schemes, it specifies the number of pixels at which the envelope of the function goes to zero. The minimum value is 1.0, and the run-time default value is 2.0. For the Gauss and SincGauss scheme, it specifies the full-width at half-maximum (FWHM) of the Gaussian envelope. The minimum value is 0.1, and the run-time default is 1.0. On astronomical images and spectra, good results are often obtained by approximately matching the FWHM of the envelope function, given by PARAMS(2), to the point-spread function of the input data. []
The resampling algorithm steps through every pixel in the output image, sampling the input image at the corresponding position and storing the sampled input value in the output pixel. The method used for sampling the input image is determined by the METHOD parameter. The rebinning algorithm steps through every pixel in the input image, dividing the input pixel value between a group of neighbouring output pixels, incrementing these output pixel values by their allocated share of the input pixel value. The way in which the input sample is divided up between the output pixels is determined by the METHOD parameter.
The two algorithms behaviour quite differently if the transformation from input to output includes any significant change of scale. In general, resampling will not alter the pixel values associated with a source, even if the pixel size changes. On the other hand, the rebinning algorithm will change the pixel values in order to correct for a change in pixel size. Thus, rebinning conserves the total data value within a given region where as resampling, in general, does not (but see the discussion of the CONSERVE parameter below).
Resampling is appropriate if the input image represents the spatial density of some physical value (e.g. surface brightness) because the output image will have the same normalisation as the input image. However, rebinning is probably more appropriate if the image measures (for instance) flux per pixel, since rebinning takes account of the change in pixel size.
Another difference is that resampling guarantees to fill the output image with good pixel values (assuming the input image is filled with good input pixel values), whereas holes can be left by the rebinning algorithm if the output image has smaller pixels than the input image. Such holes occur at output pixels which receive no contributions from any input pixels, and will be filled with the value zero in the output image. If this problem occurs the solution is probably to change the width of the pixel spreading function by assigning a larger value to PARAMS(1) and/or PARAMS(2) (depending on the specific METHOD value being used).
Both algorithms have the capability to introduce artificial artefacts into the output image. These have various causes described below.
KAPPA --- Kernel Application Package