Next: 8.5 Mapping
Up: 8 Data Processing Level:
Previous: 8.3 Common processing steps
A large fraction of this section is dedicated to the processing of chopped measurements. Although the chopped observing mode is not scientifically validated for OLP Version 7, it is not expected that the algorithms for determining the background subtracted signal will change. A preliminary correction for signal losses in chopped mode with respect to staring mode has been implemented in this version of the software. This correction is not scientifically validated and is likely to change in a future version.
In this section the extraction of (point-)source emission from source+background emission in chopped and staring measurements (whenever possible) is described in detail. Subsequently the conversion from power on the detector in units of W to flux density in Jy or surface brightness in MJy/sr is presented. Finally, the writing of the resulting data to product files is briefly described.
Operation: Sorts out the source and background records for each
chopper cycle; possible data gaps from telemetry drops are handled.
In case the observation consists of one or more measurements, each valid chopper cycle should be determined in order to be able to perform the background subtraction.
The size of a chopper cycle depends on the chopper mode used:
In case of a chopped measurement, the first chopper step is always on the background and in negative spacecraft Y-direction (cf. section 3.6). For all available AOTs except PHT32, NSTEP is set to 1 in case sawtooth or triangular chopping mode was selected. The PHT-S dark measurement is always treated as a staring measurement.
The presence of possible data gaps due to telemetry drop-outs is determined by checking whether the time difference between the current and the next record is according to the chopper dwell time. If this is not the case, the current and following records are skipped until the beginning of a new cycle is found. The start of a new cycle is inferred from the chopper step number. As each chopper cycle starts with the maximum negative offset, the step number should have the value:
As soon as a full valid cycle has been encountered, the data are passed to perform the background subtraction. In case of staring mode, this step is skipped and a flux calculation is performed.
Operation: Perform the background subtraction for a given chopper cycle and chopper mode.
Caveat: OLP Version 7 include weighting factors (cf.
sections 8.4.2.3 and 8.4.2.2) which have not been scaled by the
factor 2 in the average. This does not invalidate the weighting,
but in the calculation of the of the mean in section
8.4.3 the value of will be too low by a factor 2.
The observer should multiply the final uncertainty by 2 to obtain the
correct values. In a future version of the software this omission
will be corrected.
For a given chopper cycle the background in-band power is subtracted from the [source+background] in-band power to obtain the source in-band power. This operation is repeated until the end of a measurement is encountered. Weighting factors are derived from the uncertainties which are used for the averaging of all chopper cycles at the end of a measurement.
In the following sub-sections we describe the background subtraction method for the different chopper modes. Note that each cycle in triangular chopping mode consists of 4 plateaux referring to 2 [source+background] and 2 different background positions. In sawtooth mode there are 3 plateaux: 1 [source+background] and two different background positions. The following symbols are used:
All in-band powers are given in Watts, the weights are dimensionless.
Each cycle contains only 1 [source+background] plateau and 1 reference background position. For chopper cycle i:
The weighting factor is determined from the in-band power uncertainties:
where is the uncertainty in power for the measurement on [source+background], etc.
Each chopper cycle contains 1 [source+background] chopper plateau and 2 reference positions. For chopper cycle i:
Pi(s) = Pi(s+b) - Pi(b).
With weighting factors:
where = 1 in OLP7, but the correct value should be 4; is the uncertainty in power for the measurement on [source+background], etc.
Each chopper cycle contains 2 [source+background] chopper plateaux and 2 reference positions. For chopper cycle i:
For chopper cycle i:
Pi(s) = Pi(s+b) - Pi(b)
A weighting factor is also determined from the power uncertainties:
has the same meaning as in the previous subsection.
Operation: determine the average source and background powers of all chopper cycles in a measurement.
For all chopper cycles in a measurement, the weighted average is computed from the parameters per chopper cycle. For a given set of powers with weights obtained over a measurement, the weighted mean is derived from:
(8.3) |
P(X) can be either the power of the source or background. The corresponding uncertainty is calculated from the weights:
(8.4) |
In rectangular mode the following mean powers are derived for each pixel:
In sawtooth and triangular mode the following mean powers are derived for each pixel:
Operation: Derive the average target powers in staring mode.
This is a null operation as there is only one record per measurement.
Operation: Compute the background averaged over all pixels in
the array for a chopper reference position.
A weighted mean of all the pixels is found - if there are n of these where
then(8.5) |
(8.6) |
where j refers to the pixels in an array. For sawtooth and triangular chopped modes, this is done at both background positions.
Operation: Correct the background subtracted source in-band power
for possible signal losses due to the application of chopped mode.
In Derive_SPD, see section 7.3.9, the empirical correction factors per detector pixel were determined for signal losses in chopped mode. The correction factors are transferred to Derive_AAR processing via the SPD product header (section 8.3.1). The correction can only be applied as soon as the difference signal between [source+background] and background is known which is only computed in Derive_AAR. Since the in-band power is proportional to signal the correction can be carried out at the present processing stage.
In case of the C100 array, it has been observed that the chopped signal of pixel 6 responds completely differently compared to the other pixels in the array. It is therefore decided for OLP Version 7 to remove the observed background subtracted in-band power and to replace this by the average of the in-band powers of the equivalent pixels - in terms of illumination - on the array (cf Table 3.1):
P(s, pixel 6) = (P(s, pixel 2)+P(s, pixel 4)+P(s, pixel 8))/3, | (8.7) |
where s refer to the source flux after background subtraction. Subsequently, to correct for signal losses, for a given pixel j: >
(8.8) | |||
(8.9) |
where Pc refer to the corrected in-band power and Cchop(j) is the signal loss correction for pixel j.
Operation: Derive the sum of the in-band powers of all pixels for a given PHT-C array.
In case the observer requested the measurement of a point source flux with the PHT-C detector arrays, the total [source+background] power as well as the background power on the array is determined by summing the respective powers over all pixels.
(8.10) |
and for the [source+background] and background power:
(8.11) | |||
(8.12) |
The uncertainties are computed according to:
(8.13) |
The relations for and are similar.
Operation: In case the observer has requested a point source
measurement, a 2 dimensional Gaussian function is fitted to the intensity
pattern on the array. This processing is done in addition to the sum of
all pixel in-band powers (section 8.4.7).
Caveat: This method of providing point source photometry is not
scientifically validated. In particular in the case of faint sources and noisy
data, the derived fluxes and uncertainties are not
reliable.
To secure a converging fit, an interpolation is performed whenever there are undefined in-band powers for some pixels. The fitting of the 2 dimensional Gaussian itself is performed using standard iterative fitting routines provided by the NAG mathematical routines library (routines E04FDF and E04YCF).
The following parameters are obtained:
Details of the procedure are given in the next subsections (sections 8.4.8.1 and 8.4.8.2).
The fitting routine described in section 8.4.8.2 requires only valid pixel intensities on the detector array. Interpolation is necessary in case there are `bad' data pixels. The observed in-band power on a pixel is flagged `bad' if there is no valid chopper plateau cycle during a given measurement.
A check is performed to determine whether there is a sufficient
number of good pixels for interpolation.
For C200 one pixel is allowed to be missing. For C100 the
criteria are (1) the presence of the centre pixel (pixel 5) where the source
is expected to be and (2) there must be at least 2 good pixels on any side
of the array. Criterion (2) is imposed to avoid interpolation using an
already interpolated value.
The rules for interpolation are
C200: a b : a = b + c - d c d C100: a b c : b = (a + c)/2 d e f g h i a = b + d - (c + g)/2
Note that there is a rotational symmetry about each side; only one orientation is given. The accuracy of the method depends on
The height of the source peak, its position, and the background level is obtained by fitting a Gaussion function to the data. The accuracy of this method depends on the correctness of the assumption of a Gaussian on top of a constant background. The in-band power dstribution is considered as a 2 dimensional array:
where and
The x and y axes are the first (along spacecraft Z-axis) and second (along spacecraft Y-axis) dimension of the pixel array, respectively, with origin at the centre of the array. A chi-squared ``goodness of fit'' function is defined as
The best fit can be found by determining the minimum of .For C100, estimates of the uncertainties on the parameters can be derived from the Jacobian of the function at the solution. Detailed discussion of the method is beyond the scope of this document; the NAG algorithm E04YCF is used. The nominal uncertainty of the fit is
where is the number of degrees of freedom which is determined by the number of pixels n, the number of parameters (4), and the number of interpolations performed on C100 (section 8.4.8.1):Since the position of the peak is irrelevant of the size of it and the background it is located, and (c,d) are largely independent of each other. Thus adding 2 to the degrees of freedom is justified. This argument implies that the uncertainties for C100 may be overestimated. For C200 it is assumed that:
The variances are calculated from:
where mpix is the mean pixel value used to scale into the correct units:
The uncertainty of the fit is estimated as
Operation: Convert the mean in-band power on a detector to a monochromatic flux density (Jy) assuming a or - equivalently - constant spectral energy distribution.
Caveat: The uncertainty in the PHT-S flux densities contains
a systematic term coming from the uncertainty in the spectral response
function (see eqn. 8.17 and 8.21), this
term should have been removed.
The PHT-S subsystem is not calibrated by performing an FCS measurement within the AOT. Therefore the PHT-S signals are directly converted to flux density assuming a fixed responsivity for each PHT-S pixel and a fixed spectral response function. This requires a flux density computation with is different from all other AOTs. The distinction is made in the following subsections.
The monochromatic flux density in Jy is derived as follows (cf eqn. 5.6):
(8.14) |
with uncertainty
(8.15) |
where,
In the case of PHT-S (AOT P40) the signal spixel with uncertainty (in V/s) for each pixel is converted to a flux density through:
(8.16) |
with uncertainty
(8.17) |
where,
Operation: Convert flux density in Jy to surface
brightness in MJy/ster.
The surface brightness calculation assumes that the point source flux density has been derived. Based on the point source flux density the surface brightness is determined.
The surface brightness is obtained by applying the relationship:
(8.18) |
with the uncertainty computed according to
(8.19) |
where with the same definitions as in the previous sections,
The values of were computed by using a model which takes into account the ISO telescope mirrors as well as the physical sizes of the apertures in case of PHT-P or detectors in case of PHT-C. The model provided the 2-dimensional beam profile (or ``footprint'') of each possible aperture/filter (PHT-P) or pixel/filter (PHT-C) combination. The value of was eventually obtained from the integral of the footprint.
In the case of PHT-S (AOT P40) the signal spixel (in V/s) with uncertainty is directly converted to surface brightness:
(8.20) |
with uncertainty
(8.21) |
where
Operation: Write a complete PHT-P point source photometry
product.
Write the product FITS header followed by the processed data in a binary table with each record containing the data for a single filter or aperture.
Detailed product descriptions can be found in section 12.4, subsection 12.4.2 (product PPAP).
Operation: Write a complete PHT-P extended source or raster photometry
product.
Write the product FITS header followed by the processed data in a binary table with each record containing the data for a single filter, aperture or raster point.
Detailed product descriptions can be found in section 12.4, subsections 12.4.3 (PPAE) and 12.4.9 (PPAS) for single pointing and raster products, respectively.
Operation: Write a complete PHT-C point source photometry
product.
Write the product FITS header followed by the processed data in a binary table with each record containing the data for a single filter.
Detailed product descriptions can be found in section 12.4, subsection 12.4.4 (PCAP).
Operation: Write a complete PHT-C extended source or raster
photometry product.
Write the product FITS header followed by the processed data in a binary table with each record containing the data for a single filter or raster point.
Detailed product descriptions can be found in section 12.4, subsections 12.4.5 (PCAE) and 12.4.10 (PCAS) for single pointing and raster products, respectively.
ISOPHOT Data Users Manual, Version 4.1, SAI/95-220/Dc