STScI Logo

ckwxxx tools


NAME · USAGE · DESCRIPTION · EXAMPLES · SEE_ALSO

NAME

ckwfoc,ckwfos,ckwhrs,ckwhsp,ckwwfpc,ckwwfp2, ckwnicmos, ckwstis1, ckwstis2, ckwstis3, ckwstis4 -- Standard HST instrument calibration psets.

USAGE

ckwfoc
ckwfos
ckwhrs
ckwhsp
ckwwfpc
ckwwfp2
ckwnicmos
ckwstis1
ckwstis2
ckwstis3
ckwstis4

DESCRIPTION

These psets are the standard Hubble Space Telescope (HST) instrument calibration psets used with the chcalpar family of tasks. These psets are used to store changes in HST data calibration header keywords.

These are not actual tasks, but are psets (Parameter SETS). These are similar to IRAF task parameters, but are often used by groups of tasks for passing information. Any of the parameter-specific tasks, such as `eparam' or `lparam' can be used on a pset. (Type "help eparam" for further information.) In the context of chcalpar, there is a pset defined for each of HST's science instruments. The names of the psets are of the form ckwxxx, where "xxx" is the instrument identification, e.g., ckwhrs for the Goddard High Resolution Spectrograph.

Due to the complexity of the STIS instrument, there are four psets depending upon the detector and obstype of the data files. ckwstis1 applies to the CCD Imaging data; ckwstis2 applies to the CCD Spectroscopic data; ckwstis3 is for the MAMA Imaging data; and ckwstis4 is for the MAMA Spectroscopic data.

Psets can be invoked as tasks. Invoking a pset actually runs the task eparam. The parameters that eparam is editing will be the parameters of the pset. Theses calibration parameter psets can be invoked this way. However, they are meant to be used with chcalpar.

For chcalpar, you can also provide a customized pset instead of using a standard pset. You can also start from scratch, but we suggest starting with one of the standard psets and modifying it as appropriate.

If the data that will be used with chcalpar and the customized pset has a header keyword "INSTRUME", then you should define a parameter called instrument and give it as the default value for the header keyword value.

If you create a parameter file, you must define it in IRAF, for example:

        cl> task newpset = "directory$newpset.par"

Once defined, the pset can be used in chcalpar just as any of the other standard psets.

EXAMPLES

These examples are lines from the various psets. The lines define the parameter name, whether or not it is required, any default values, minimum and maximum values, and a short description.

1. A parameter from the ckwhrs pset which defines the keyword diohfile and specifies only a description:

        diohfile,s,h,"",,,"diode response header file"

2. A parameter from the ckwhrs pset which defines a list of possible values for the parameter dqi_corr. The possible values are " ", "perform", "omit", and "complete".

        dqi_corr,s,h," ","| |perform|omit",,"data quality initialization"

3. Since all HRS data have the header parameter "INSTRUME = HRS", the ckwhrs pset defines the parameter instrument:

        instrument,s,h,"hrs","|hrs",,"Instrument represented by this pset"

4. Copy the pset for ckwwfpc to the home directory and define it. Afterwards, the new file can be edited as described above.

        cl> stsdas
        st> copy tools$ckwwfpc.par home$newwfpc.par
        st> task newwfpc = home$newwfpc.par

SEE ALSO

chcalpar, eparam, getcal, modcal, parameters, putcal


Source Code · Package Help · Search Form · STSDAS