|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/5.4.1/doc/rgsprods/node3.html
Дата изменения: Fri Jan 10 23:45:03 2003 Дата индексирования: Sat Dec 22 09:05:16 2007 Кодировка: Поисковые слова: arp 220 |
The task takes, for its input, files produced by rgsproc, namely: (i) an event list, (ii) a file containing both a source list and information on selection regions, and (iii) an exposure map. The event list and the region specifications in the source list are used to create the RGS image and spectrum products. After these are made, rgsprods adds a CONTENT keyword to each of the three input files, copies them into the correct PPS filenames, and moves the resulting files to the directory designated by the parameter prodsdir.
Although rgsprods, a perl script, has been designed primarily as a pipeline development tool, it can also be used interactively.
Note that there is some overlap between this task and rgsproc. Both tasks create source and background spectra. However this causes no problems in practice. With default parameter settings, rgsprods will not overwrite files that rgsproc has written.
The method of submitting the names of the three input files to rgsprods has been designed to be convenient, at some sacrifice to generality. The fact is that nearly all the time these filenames occur in one of two basic styles:
| Style: | File template: |
| rgsproc | RRRROOOOOOOOOOIITEEE00_ name .ds, where name can be `filtered', `sources' or `expmap'. |
| pcms | POOOOOOOOOOIITEEEnnnnnn0000.FIT, where nnnnnn can be EVENLI, SRCLI_ or EXPMAP. |
In these templates, RRRR is the rev number, OOOOOOOOOO is the observation identifier, II the instrument (either R1 or R2), EEE the exposure number and T the exposure type (either S or U)).
A parameter has only been provided for the name of the source list. If this file name follows either of the templates above, rgsprods will attempt construct the names of the other two. If not, then the task will fail.