Документ взят из кэша поисковой машины. Адрес оригинального документа : http://hea-www.harvard.edu/PROS/PUG/node53.html
Дата изменения: Unknown
Дата индексирования: Mon Oct 1 23:11:14 2012
Кодировка:
Поисковые слова: п п п п п п п п п п п п п п п п п п п п р п р п р п р п р п р п

   
*qpappend* -- Append a list of input qpoes to produce a single qpoe file

Read a list of input qpoe files (including filters) and produce an appended output qpoe file. The event lists and TSI records are appended; the DEFFILT (good time intervals) are merged; history is preserved, with additional history records for the append; ONTIME will be the sum of the ONTIMES; DTCOR will be the ONTIME weighted DTCORS; MJD-OBS,DATE-OBS,TIME-OBS will be the minimum of the input values. As currently implemented, many of the header keywords MUST match exactly in all of the append files. The output keywords which define WCS will be taken from the first file in the list. (See the help files for further details.) Any type of filtering can be applied to the input qpoe file, including region filtering. In addition, the output event definition can be different (generally smaller) than the input event definition. If it is greater, a warning is issued and the ``extra'' part of the record is undefined.
The following will merge together the two observational pieces of AR LAC to form a single MERGED file. (This is obviously a contrived example, but can be used for testing.)

  cl> xray
  xr> xdataio
  xp> page merge.lst        # an ascii file listing the two input qp files

  xdata$rp110590.qp[time=(1606720.00:1607484.00)]
  xdata$rp110590.qp[time=(1611613.00:1612817.00)]

  xp> qpappend @merge.lst ``'' merge.qp large

@ is an iraf symbol to indicate that the task should use the contents of merge.lst as its input.

An additional task, qpappend_ftsi, is a modified version of qpappend. An option exists to keep the temporal status intervals (TSI) records from the first file only instead of concatenating all the TSI records. This option is useful to avoid excessively large qpoe files which are occasionally generated (e.g. when performing complex manipulations on segments of the same qpoe file).