| Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/7.1.0/doc/omfchain/node13.html Дата изменения: Mon Jul 9 08:29:39 2007 Дата индексирования: Sat Dec 22 11:06:38 2007 Кодировка: Поисковые слова: redshift survey | 
 
 
 
 
 
 
 
 may not be a good approximation to the extraction
area. Furthermore, the background extraction region is an annulus,
possibly with circular areas excluded (see the OMREGION task
description), and these excluded circles are not necessarily totally
enclosed by the annulus. In addition, the FAST-mode OM window is small,
and a part of the source and background areas falls out of this window.
The source and background counts should be
scaled to the CAL circular area in order to correct them for the
coincidence loss. This scaling is sensitive to the currently used
OM PSF. If the source and background areas are affected by the 
source proximity to the edge of the OSW or if the real OM PSF differes
from that, taken from the current calubration file (CCF), than the 
OMLCBUILD output count rates could vary from exposure to exposure
for the same source. The effect could be increase for bright sorces 
due to the 8-pixel pattern noise. In order to avoid these variations
and to obtain a uniform combined light curve, it is better to use 
a fixed radius for the source extraction area for all the exposures
in the ODF. This radius should not be 
less than 6 pixels.
This is currently used as the default value for the chain in order to get
better signal-to-noise ratio.
One may change this parameter by using  the command `omfchain srcradius=...`.
If srcradius is set to a negative value, it will be fixed while
 processing all
the exposures (its default value is negative). Changing srcradius
 parameter one should also properly esablish
the background extraction area setting bkginner and bkgouter
parameters (see description of the parameters).
 may not be a good approximation to the extraction
area. Furthermore, the background extraction region is an annulus,
possibly with circular areas excluded (see the OMREGION task
description), and these excluded circles are not necessarily totally
enclosed by the annulus. In addition, the FAST-mode OM window is small,
and a part of the source and background areas falls out of this window.
The source and background counts should be
scaled to the CAL circular area in order to correct them for the
coincidence loss. This scaling is sensitive to the currently used
OM PSF. If the source and background areas are affected by the 
source proximity to the edge of the OSW or if the real OM PSF differes
from that, taken from the current calubration file (CCF), than the 
OMLCBUILD output count rates could vary from exposure to exposure
for the same source. The effect could be increase for bright sorces 
due to the 8-pixel pattern noise. In order to avoid these variations
and to obtain a uniform combined light curve, it is better to use 
a fixed radius for the source extraction area for all the exposures
in the ODF. This radius should not be 
less than 6 pixels.
This is currently used as the default value for the chain in order to get
better signal-to-noise ratio.
One may change this parameter by using  the command `omfchain srcradius=...`.
If srcradius is set to a negative value, it will be fixed while
 processing all
the exposures (its default value is negative). Changing srcradius
 parameter one should also properly esablish
the background extraction area setting bkginner and bkgouter
parameters (see description of the parameters). 
implot set= sky_image_file.FIT withsrclistset=y srclistset=osw_source_list_file.FIT device=your_device (e.g. /XW) itv=1 radius=3 maxsrc=10 colour=7.
While often there will be only one object in the image, one should check for spurious detections, which could affect the analysis of the target source and also for missed sources or prominent objects in the window, which may contaminate the target. At the current time, bright contaminating sources are not treated properly, and, if present, affect the light curve of the target (and vice versa) - this will be rectified in a future version of the relevant SAS tasks. It is possible to change the detection efficiency via the boxscale, smoothsize, nsigma, and contrast parameters.