Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/5.4.1/doc/rgsbadpix/node3.html
Дата изменения: Fri Jan 10 22:32:35 2003 Дата индексирования: Sat Dec 22 10:16:37 2007 Кодировка: Поисковые слова: meteor shower |
rgsbadpix combines the calibration bad pixel data from the CCF with any hot pixels found by analyzing the raw telemetry for one CCD from an RGS exposure in spectroscopy mode. The result is stored in the BADPIXn extension tables of the input spectroscopy dataset, or in a separate dataset if requested (withbadpixset=yes). When the same bad pixel is identified by both the CCF and the telemetry analysis, the output bad pixel table mentions only the CCF version. CCF bad pixels that lie outside the telemetry window of the exposure are not included. The columns of the BADPIXn tables describe these properties: location, type and source. Location is specified in chip-oriented coordinates, and describes a column segment of similar bad pixels in terms of its minimum y-axis coordinate and upward extent. The type codes are described in the CAL documentation. The source codes are as follows:
A bad pixel obtained from the CCF, and listed there as having been uplinked to the on-board data preprocessor (DPP). Such pixels should never appear in the telemetry, and should therefore never be identified by the telemetry analysis. There is no option to exclude these from the output bad pixel tables; to do so would corrupt the exposure map.
A bad pixel obtained from the CCF, but not listed as having been uplinked to the DPP. These are regarded as advisory, and may be excluded from the output bad pixel tables (withadvisory=no). One would hope that any of these listed as hot would also be identified by the telemetry analysis.
A bad pixel identified by analysis of the telemetry. The current algorithm only attempts to find isolated hot pixels and columns. This process is optional and may be disabled (withfoundhot=no).
Four parameters control the hot pixel finding algorithm, which is an implementation of John Peterson's memo, RGS-COL-CAL-00015. First the pixels are analyzed individually for excessive activity and then the same is done for whole columns. pixnoiselimit and colnoiselimit respectively are the minimum uncalibrated energies for considering single-pixel events in the first and second phases. pixsharpness and colsharpness respectively control the degree of excessive activity required to flag a pixel or column as hot. Refer to section 8 for the precise meaning of the sharpness parameters. Frames marked with IN_BAD_FRAME in the FLAG column of the EXPOSURE table are considered bad and their pixels are discarded. No hot pixel finding algorithm is available for HTR (high time resolution) mode data.
Throughout this document a marks items that do not apply to HTR
mode data.