Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/documents/dhb/web/c26_stisdataanal.fm4.html
Дата изменения: Wed Jul 1 20:35:22 1998
Дата индексирования: Sat Dec 22 16:57:23 2007
Кодировка:

Поисковые слова: arp 220
[Top] [Prev] [Next] [Bottom]

23.4 TIME-TAG Data

As described in "Tabular Storage of STIS Data" on page 20-5, raw time-tagged Sdata are stored in an event table which contains separate columns for the x and y pixel coordinates and the arrival time of each detected photon event. There will also be an associated table containing "good time intervals." In general these data can be analyzed in one of two ways:

Using Existing PROS Time Series Analysis Software

The PROS xray and the xtiming packages in IRAF-originally developed to analyze Roentgen Satellite (ROSAT) data-can be used to do time series analysis of the STIS TIME-TAG data. To use this package, the *_tag.fits files need to be converted to PROS QPOE format (extension *.qp), using the task fits2qp. A few particularly useful tasks within the PROS software package are listed in Table 23.3.


Useful PROS Tasks

Task

Purpose

period

Find period from a dataset

fldplot

Plot the light curve with the period folded into it

chiplot

Chi-square plot for various periods

ltcurv

Plot simple light curve from a dataset

Note that the times given in the first column of the raw time-tag data (which is the time relative to the start of the exposure) are not corrected for the time delay due to the motion of the earth or the spacecraft. The change in time delay due to the motion of the spacecraft can be a maximum of about 30 millisec in one orbit. The absolute time delay relative to the time-frame at the earth barycenter can itself be much larger. To correct for these effects, the ephemeris of the earth and the spacecraft are necessary. A separate task is being developed at present, similar to the tasks for the High Speed Photometer (HSP), to correct for these effects and to convert the times to the barycenter of the earth. This task can be used by observers, or can be processed at STScI as a special request, for those science uses of TIME-TAG where it becomes an important effect.

Using inttag to Produce ACCUM Images of Specified Time Slices

The inttag task can be used to integrate STIS timetag data into an image or set of images. The default behavior for inttag is to accumulate all events from the table, writing the results as one image set in the output FITS file. The user has the option, however, to specify explicitly a starting time, time interval, and number of intervals over which to integrate, in which case a collection of image sets will be written to the output file, simulating a REPEATOBS ACCUM observation. Breaking the data into multiple, short exposures can be useful not only for variable targets but also to improve the flatfielding when the Doppler shift is significant.

To generate each time-filtered image, inttag compares the arrival time for each event to both the user-specified interval and the set of good time intervals. (Good time intervals, or GTIs, are intervals during which STIS is known to be taking valid data.) If the event qualifies, the raw x and y coordinates will be mapped to the appropriate output pixel location (to account for binning, subarray location, and Doppler correction for echelle spectroscopy), and the detected photon count of the output pixel will be incremented.

The inttag task requires two arguments: the names of the input and output FITS files, in that order. Optional parameters include writing the output image(s) in high-res format (the default is low-res). To specify times interval(s) different from the entire duration of the exposure, specify the starting time in seconds since the beginning of the exposure (sttime, the default is INDEF, meaning to start at the beginning of the first GTI), the integration time in seconds (increment, the default is INDEF, meaning to end at the last GTI), and the number of intervals (rcount, the default is one). If no other value is specified, one ACCUM image set will be created containing all the events. A simple example would be to create a single image set, including only the first 1000 seconds:

cl> inttag stis_tag.fits kilo_raw.fits sttime=0 increm=1000

A somewhat more complex example is to create 20 high-res imsets, each 100 seconds in duration, starting at the first time in the GTI table. Note that while 20 imsets were specified, fewer may actually be written if any of the 100-second intervals is not contained within any GTI, or if the last time in the GTI table is less than 2000 (i.e. 100 sec * 20 intervals); inttag will report how many imsets were created.

cl> inttag stis_tag.fits multi_raw.fits sttime=0 \

>>> increm=100 rcount=20 high+

Once the images have been created, it is straightforward to process them with calstis and analyze the output images or spectra, as appropriate (see "Recalibration of STIS Data" on page 21-29).



[Top] [Prev] [Next] [Bottom]

stevens@stsci.edu
Copyright © 1997, Association of Universities for Research in Astronomy. All rights reserved. Last updated: 07/01/98 10:49:54