|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/7.1.0/doc/arfgen/node32.html
Дата изменения: Thu Nov 15 16:15:38 2007 Дата индексирования: Sat Dec 22 08:43:14 2007 Кодировка: Поисковые слова: arp 220 |
By default the task will reduce the effective area produced in the ARF if the source area contains bad pixels/columns or contains area which lies outside the CCD boundaries. For an extended source this reduction is simply the ratio of the dead area within the source region to the good area. For point sources a fine grid is used to determine the contribution to the enclosed energy of each dead point, i.e. the dead regions are normalised by the fraction of the point spread function lying within that region before being subtracted from the total effective area. The task uses the parameter extendedsource to choose between these options. Although the correction for point sources is quite good the extended source correction assumes a uniform surface brightness of the source. If this condition is not met then quite large errors can be introduced. There is currently no way of performing an accurate correction for chip gaps and bad pixels within extended source regions within arfgen.
In a similar way the task corrects for area of the source region which is outside the FOV (selectable with the parameter ignoreoutoffov), outside the observing window or on a CCD explicitly excluded by a CCD selection within the data subspace.
This behaviour can be turned off by setting withbadpixcorr=false. CCD gaps and area outside the FOV are automatically corrected for if withbadpixcorr=true. To correct for bad pixels, a file containing bad pixel extensions must be specified on the command line by badpixlocation=file. The bad pixel information is usually stored in the event file from which the spectrum was constructed. Bad columns and bad rows (MOS only) are also handled if they are specified in the OFFSETS column of the badpixlocation file. Pixels adjacent to chip gaps, bad pixels and bad columns are also corrected for if the FLAG selection in the datasubspace has been set accordingly. The code checks each bit mask in the event flag to see if pixels next to a particular type of bad pixel or bad column should be excluded. In this way spectra created with, for example, the #XMMEA_EM and #XMMEA_SM flagging can produce different effective areas for certain selection regions.
The task creates temporary files called BADPIXnn.ds, where nn is the
CCD number, in the current directory while calculating the bad pixel
correction. To make these files permanent specify
withfilteredset 
yes
on the command line.