Access an image for modification IMG_MOD[n][x]
The [n] and [x] parts of the name are optional. If used [n] indicates the number of dimensions of the data (1 to 3, the default is 2) and [x] the data type (one of R, D, I, W, UW, B or UB, the default is R). So for instance if you wanted to use 3-D data with a data type of DOUBLE PRECISION, the subroutine that you should call is IMG_MOD3D.
’DATA,BIAS,FLAT’). A pointer to
the data of each image is then returned (in this case the IP argument should be passed as an array of
size at least the number of parameter names). The advantage of obtaining a sequence of images in
this manner is that the images are guaranteed to have the same shape and the same data
type.
The message which complains when "bad" (undefined) pixels are present in the input data can be
stopped by following each parameter name by the character "!", i.e. ’DATA!,BIAS!,FLAT’ will inhibit
checking the images associated with parameters ’DATA’ and ’BIAS’, but will check the image
’FLAT’. "Bad" pixels have the symbolic value VAL__BAD[x] which is defined in the include file
PRM_PAR.
The input image is accessed in the type that you ask for regardless of its storage type. This may occasionally cause problems if these two types differ. This arises because when the image is converted to and from its storage type it is not always possible to guarantee that a valid value will result (for instance many numbers that you may store in a REAL variable cannot be stored in an INTEGER variable). When an image element cannot be converted it is assigned the appropriate bad value.