Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.stsci.edu/documents/dhb/web/c26_stisdataanal.fm5.html
Дата изменения: Wed Jul 1 20:35:22 1998 Дата индексирования: Sat Dec 22 17:00:17 2007 Кодировка: Поисковые слова: arp 220 |
If a narrow slit is used for the science, an ACQ/PEAK acquisition may have been performed. The slit is scanned across the object with a pattern determined by the aperture selected. The telescope is then slewed to center the star in the aperture, and a confirmation image (a 32 x 32 grid) is obtained; the accuracy of the ACQ/PEAK is 5% of the slit width. Note that the last extension in the file (image_raw.fits[4]) contains the values in the individual steps of the ACQ/PEAK (use listpix to view these values).
Type |
Enclosed |
Gaussian |
Direct |
---|---|---|---|
Star
|
1.59
|
1.57
|
1.49
|
Sky
|
15.22
|
142.84
|
4.81
|
ACQ Data
An examination of the target acquisition data (either from the raw data or the paper products) will allow you to detect gross errors in the centering of your target; note that, if retrieving data via StarView, you must request uncalibrated data to receive target acquisition observations. A comparison of the initial [sci,1] and post-coarse slew [sci,2] images should show the object moving close to the center of the acquisition sub-array.
Users of STIS data must request "uncalibrated" data when retrieving ACQ and
ACQ/PEAK observations through StarView. Since ACQ-like data do not get
-calibrated there are no calibrated data products.
You can also verify that the fluxes in both images, which are found in the science header under the keyword MAXCHCNT, are consistent by performing the following steps in IRAF:
cl> imheader image_raw.fits[1] long+ | grep MAXCHCNTThe first value will be the target flux in the maximum checkbox (3X3 for POINT sources, user-defined for DIFFUSE sources) in the initial image, while the second is the maximum checkbox in the post-coarse slew image. If the fluxes are not consistent, or if the object did not move closer to the center of the array, there is likely a problem with your acquisition.
cl> imheader image_raw.fits[4] long+ | grep MAXCHCNT
cl> listarea image_raw.fits[4]
Sample 1 2 3
Line
1 4707. 260769. 0.
For a 3-step linear peakup, the pixel [1,1] is the leftmost scan position, [2,1] is the middle position, and [3,1] is the rightmost position. See Figure 23.3.
Figure 23.3: Flux Values at Each Stage in Peakup
cl> imstat image_raw.fits[1]fields="image,npix,mean"This will give you an output like the following:
cl> imstat o4de01jdq_raw.fits[1]
# IMAGE NPIX MEAN
o4de01jdq_raw.fits[1] 32704 8.241
The total counts in the image is the product of the number of pixels (NPIX) and the mean value (MEAN), or 269,514 in this example.
Note that you will need to perform one correction to the mean value prior to your comparison. The flux values in the peakup scan have been adjusted to subtract the minimum flux value in the peakup data (which is why one value in the peakup is always zero). This value needs to be subtracted from the counts in the confirmation to do a proper comparison. The value can be found in pixel 712 of the _spt image; to display the value on the screen, do the following in IRAF:
cl> listpix image_spt.fits[1] | grep 712In the example, the value was 6008, which means the corrected number of counts in the confirmation image is 263,506.
Comparison of the maximum flux value during the peakup (260,769) with the flux in the post-ACQ/PEAK confirmation image (263,506) should show that the flux in the confirmation image was greater than or equal to the maximum flux in the peakup grid. If this is not the case, then there is likely a problem with your peakup acquisition.