Creates Stokes vectors from a set of 2-dimensional intensity frames POLKA
The main processes applied to the data are:
1) Extraction of the required sub-regions from each input frame.
2) Alignment of all extracted sub-regions using stars within the field.
3) Sky subtraction within each aligned sub-region.
4) Calculation of a Stokes vector for each pixel. This step may be omitted if required by supplying a null value for parameter OUT_S.
The inputs to this application are a set of intensity frames which have been corrected to remove any instrumental effects introduced by the detector (such as de-biassing, flat-fielding, etc.). Output Stokes vectors can only be produced if all input frames contain a POLPACK extension (see application POLIMP). In dual-beam mode, each input frame contains two images of the sky (the O and E ray images). In single-beam mode, each input frame contains only a single image of the sky.
The outputs from this application consist of the aligned, sky-subtracted intensity images, and the cube holding the Stokes vectors. In dual beam mode two output intensity frames are created for each input frame, one containing the O ray image, and the other containing the E ray image. In single-beam mode one output intensity frame is created for each input frame, holding the usable area of the corresponding input frame. The user may choose not to create any or all of these outputs. For instance, the Stokes vectors may be produced without retaining the aligned intensity images (see parameters OUT_S, OUT_E, OUT_O and OUT).
Use of this application divides into two stages. In the first stage, a Graphical User Interface (GUI) is used to obtain all the information required to produce the output data files from the user. This includes identifying stars, masks and sky regions on each of the supplied input images. This is the labour-intensive bit. Once this has been completed your satisfaction, the second stage is entered in which the output data files are created. Once initiated, no further interaction on your part is required. This is the computationally intensive bit. The GUI makes use of various applications from POLPACK, KAPPA and CCDPACK to perform all these tasks. Note, if the find the image display area too small for comfort you can make it bigger using the DPI parameter described below.
A step-by-step tutorial on the use of the GUI is available within the "
Help"
menu at the right hand
end of the menu bar (see also the STARTHELP parameter).
Various options controlling the behaviour of the GUI can be set on the command line by assigning
values to the parameters listed below. Alternatively, most of them can be set using the "
Options"
menu in the menu bar at the top of the GUI. If not supplied on the command line, these parameters
usually adopt the values they had on the previous invocation of POLKA. The values shown in square
brackets in the parameter descriptions below are the initial default values.
’
s preference, even if the DPI value returned by the
X server is correct. Note, this value cannot be set from the GUI’
s "
Options"
menu. [!] "
O-ray"
image, and
all the GUI controls related to the E-ray areas are disabled. This parameter is only used
when processing polarimeter data (see parameter POL). It’
s value cannot be set from the
"
Options"
menu within the GUI. [TRUE] 1 - Shift of origin.
2 - Shift of origin and rotation.
3 - Shift of origin and magnification.
4 - Shift of origin, rotation and magnification.
Only mapping types 1 and 3 are available when processing dual-beam polarimeter data. Mapping types 2 and 4 are also available when processing single-beam data. [1]
"
stdout"
is supplied, then the messages will be directed to standard
output (usually the screen). If a null (!) value is supplied, then no log file will be created.
Note, this parameter cannot be set from the GUI’
s "
Options"
menu. [!] "
Group
Expressions"
for information on the allowed formats for this list. Any asterisk within the
supplied string is replaced in turn by each of the input image names. If a null (!) value is
given, then the intensity images are not saved. Note, the output images cannot be specified
within the GUI. "
Group Expressions"
for
information on the allowed formats for this list. Any asterisk within the supplied string is
replaced in turn by each of the input image names. If a null (!) value is given, then the E-ray
intensity images are not saved. Note, the output images cannot be specified within the GUI. "
Group Expressions"
for information on
the allowed formats for this list. Any asterisk within the supplied string is replaced in
turn by each of the input image names. If a null (!) value is given, then the E-ray intensity
images are not saved. Note, the output images cannot be specified within the GUI. "
Help"
menu or the F1 key on the
keyboard. [TRUE] "
Options"
menu in the GUI. [TRUE] "
Images"
menu. It may take one of the following values:
ZOOMED – The new image is displayed with the current zoom factor and image centre.
UNZOOMED – The zoom factor and image centre are reset so that the new image just fills the image display area in at least one dimension. [ZOOMED]
’
im1,im2,im3,im4’
cube out_o=! out_e=! ’
im1’
to ’
im4’
, subtracts a
sky background from each (estimated from areas within the object frames), and stores the
corresponding Stokes vectors in ’
cube’
. The aligned intensity images are not saved. ’
in.lis’
, subtracts the sky frames read from the text file ’
sky.lis’
, aligns them and stores them in the
images named in the text file ’
out.lis’
. All other parameters are reset to their initial default values
listed in the parameter descriptions above. No Stokes vectors are produced. If present, WCS information is copied from each input NDF to the corresponding output NDFs.
The following components are added to the POLPACK extension in the output intensity images (the extension is first created if it does not already exist):
RAY – A string identifying which of the two rays the image contains. This will be either "
O"
or "
E"
.
This is only written in dual-beam mode (see parameter DUALBEAM).
IMGID – An string identifier for the input image from which the output image was derived. If the input image already contains a POLPACK extension with a IMGID value, then the IMGID value is copied unchanged to the corresponding output images. Otherwise, the name of the input image (without a directory path) is used.
The following components are added to the POLPACK extension in the output cube holding Stokes parameter (the extension is first created if it does not already exist):
STOKES – A string containing one character for each plane in the data cube. Each character identifies the quantity stored in the corresponding plane of the data array, and will be one of I, Q, U or V.
Intermediate files created during the execution of POLKA are stored in a separate directory created
each time POLKA is run, and deleted when POLKA exits. The directory will have a name of the form
"
polka_temp_nnn"
where nnn
is some number. This directory will be created within the directory specified by the HDS_SCRATCH
environment variable. If HDS_SCRATCH is not defined then it will be created within the current
directory.