Документ взят из кэша поисковой машины. Адрес оригинального документа : http://xmm.vilspa.esa.es/sas/7.0.0/doc/epexposure/node16.html
Дата изменения: Thu Jun 29 01:18:02 2006
Дата индексирования: Sat Dec 22 12:35:20 2007
Кодировка:
Поисковые слова: п п п п п п п п п п п п п п п п п п п

XMM-Newton Science Analysis System


epexposure (epexposure-0.6.2) [xmmsas_20060628_1801-7.0.0]

Meta Index / Home Page

Comments

• Handling of out-of-time events: the number of out-of-time events depends on the spatial selection, i.e. on the amount of events which are assumed to originate from the target source, as well as on the readout mode. So this effect can not be handled as a livetime factor in an early stage of the pipeline processing but needs to be addressed as a mode-dependent PSF effect by higher SAS tasks.

• It has to be verified in orbit that there is a flat MIP distribution before one just can use the NDISCLIN counter to calculate $FC1$. If not this will imply the MIP deadtime correction has to be done properly on a column-by-column basis by looking at the Discarded Lines Map which will be transmitted at least once at the end of each observation.

• Handling of counting mode: One will need to check the EPDH counter to see how much time of an exposure was observed in counting mode (and hence did not produce any scientific data and entries in an event list). This deadtime will be stored via a good time interval (GTI) by the task epframes.

• Document EPIC-EST-OP-002, Sect.14.7 mentions the scientific data structures `First and Second Lost Synch Data' which are related to a loosing of the nominal scientific data flow. It needs to be verified that such a gap in the scientific data flow is addressed in the ODF creation already.

• For (e.g.) timing analysis there is a need to not only compute the statistical livetime factors but also to create a list of good time intervals. epframes already creates such GTIs corresponding to the flagged frames. But also the deadtimes due to the chopper, the counting mode and CCD readout (which is significant for burst and small window modes) should be accessible as GTIs to be created by higher SAS tasks.