*, ?, [a-z], {one,two,three}
all of which have usual meanings, i.e. any number of characters,
a single character, a range of characters, and a list of strings.
The simplest return would then be:
and all the images in the current directory would be accessed. Other possibilities include specifications such as:IN > *
IN > bias/* (all images in the bias/ subdirectory)
IN > rdata/*,bdata/* (all images in the rdata/ and bdata/
subdirectories)
IN > ffr* (all images whose names begin with ffr)
IN > NGC2261_? (all images whose names begin with NGC2261,
followed by one extra character)
If any of the image names you specify is an HDS container file holding more than one NDF structure, then each NDF contained directly within that file is processed as a separate image. If the data product you are using is supplied in this form, which for instance is sometimes the case for a set of frames from one exposure of a mosaic camera, this makes it much easier to process a group of images at once. So if you had an appropriate container file expos1234.sdf, then just supplying:
would allow processing of a whole group of related images. Note that it is easy to convert Multi-Extension FITS files (MEFs) into HDS container files -- this is explained in sectionIN > expos1234
.
The names of images given to programs (except for XREDUCE) do not normally require the addition of the file extension. This is only necessary when there is some ambiguity over which files to use (when for instance several images of the same name, but of different types are available). However, the file extension will be accepted if given. So for instance repeating the last examples for IRAF data frames could look like:
IN > bias/*.imh IN > rdata/*.imh,bdata/*.imh IN > ffr*.imh IN > NGC2261_?.imh
CCDPACK