... Meta Index / Home Page This section documents the parameters recognized by this task (if any). ... sets . ... list of data-sets . ... list of valid data sets . List of FITS files containing the input images in different bands . ... List of FITS files containing the exposure maps for the corresponding images listed in sets. tmpflatsets . ... list of valid file names . List of FITS files that will contain the temporary flatfielded images (images divided by their corresponding exposure maps). ...

Next: Column label: TELESCOP Up: File Formats Required Previous: MJD --- column . Data for all the telescopes at an observatory can be stored in a single MIDAS table file, called (by default) esotel.tbl. A standard path needs to be established for this file. ... Each observatory file should contain a C*72 descriptor OBSERVATORY that contains the name of the observatory, preferably as it is given in [ 6 ]. ... Each column label can be a standard FITS keyword, if an appropriate one is available. ...

... We now describe the input parameters to the self-calibration tasks. ... For selfcal , you need not perform source , dra , or ddec selection if you use the selradec option (see below). minants : The minimum number of antenna that must be present before the tasks will attempt to find a solution. ... and phase : This determines whether the self-calibration tasks solve for just phase ( options=phase , which is the default) or amplitude and phase solution ( options=amplitude ). mfs : . ...

... IRAF supports two kinds of parameters, auto parameters and hidden parameters, which are treated differently. auto parameters are updated every time a task is run. ... Parameters for each task are contained in `parameter files' in the uparm sub-directory in `myiraf'. ... im > imhead.longheader=yes # explicitly setting <task.param>=<value> im > eparam imhead # Edit the parameter file to update one or more # parameters at the same time # see next section . ...