Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/6.0.0/doc/emchain/node7.html
Дата изменения: Fri Mar 19 00:27:31 2004 Дата индексирования: Sat Dec 22 08:10:35 2007 Кодировка: Поисковые слова: http astrokuban.info astrokuban |
In most cases relying on the bad pixels
registered in the CCF is not enough. This is because
the CCF stores only the bright pixels of relatively high occurrence,
but bright pixels at a low level may be a nuisance as well.
If badpixfindalgo=EM (default) or EP,
the whole analysis of one exposure
(Fig 1)
is run first with emevents
and emenergy
in a simplified mode,
and skipping badpix
and attcalc.
The very bright pixels (which perturb the flare screening) are detected
and flagged using ebadpixupdate.
The resulting files are used to generate Good Time Intervals outside flares
(flares act as noise for the bad pixels
and make detecting them more difficult). Those Good Time Intervals
are exposure specific whatever the value of globalflare.
Then one of two bad pixel finding algorithm is called
(Fig 3), depending on
badpixfindalgo.
The resulting bad pixels file is then used by badpix in the main pass on the data (Fig 1). Dead pixels are read in the CCF, but bright pixels written in the CCF but not uplinked (and not found by the local bad pixel finder) are ignored. This second pass restarts just after emframes. The stopafterbadpixfind parameter allows to stop emchain before the main pass, to investigate in detail how the bad pixels detection worked.
If badpixfindalgo is set to NO, then the first loop is not done and the bright pixels are read from the CCF.
XMM-Newton SOC/SSC -- 2004-03-18