Документ взят из кэша поисковой машины. Адрес оригинального документа : http://xmm.vilspa.esa.es/sas/7.1.0/doc/ecubechip2sky/node4.html
Дата изменения: Mon Jul 9 06:48:51 2007
Дата индексирования: Sat Dec 22 13:46:09 2007
Кодировка:
Поисковые слова: р п р п р п р п р п р п р п р п р п р п

XMM-Newton Science Analysis System


ecubechip2sky (eimchip2sky-2.0.1) [xmmsas_20070708_1801-7.1.0]

Meta Index / Home Page

Parameters

This section documents the parameters recognized by this task (if any).

Parameter	Mand	Type	Default	Constraints
templateset	yes	dataset
The name of the input template image. This supplies information about the projection plane and pixel size (via WCS keywords) and pixel dimensions (via the array dimensions) of the output image.
chipcubesets	yes	dataset list
A list of names of input chip cubes (see the definition in the documentation for chipcube).
outsets	no	dataset list	outset.ds
The list of output images (in sky coordinates). See the documentation for eimchip2sky for a description of how they match up with the input cubes.
withindices	no	bool	no
Whether to read the indices parameter.
indices	yes	integer list	1
See the documentation for eimchip2sky for a description of how they work.
attstyle	no	string	template	binnedset|template|user
As described in the documentation for eimchip2sky, in general the attitude (ie, pointing direction and roll angle) of the spacecraft doesn't stay fixed during the course of an exposure. This `wandering' of the attitude can be approximated by sampling the attitude at a series of times during the exposure. A separate coordinate transform is computed for each attitude sample and the output image is build up of appropriately weighted contributions from each transform. The present parameter allows the user to choose whether to supply such a list of attitude samples (attstyle=`binnedset') or to simply compute a single coordinate transform for the whole exposure, either at an attitude read from the _PNT keywords of the templateset (attstyle=`template', the default) or at an attitude submitted by the user (attstyle=`user').
binnedatttab	yes	table
This parameter is read (and only mandatory) if attstyle=`binnedset'. The parameter should give the name of a dataset plus table (eg: `mySet.ds:ATT_TAB'). The table should contain samples of the XMM spacecraft attitude in time bins (see the task binned_att documentation for a description of the format).
weightstyle	no	string	gti	none|binnedset|gti
This parameter is read if attstyle=`binnedset'. A series of attitude samples is supplied; it remains to decide how to calculate the weight for each sample. weightstyle=`none' is only valid if there is only 1 attitude sample: the task will fail with an error otherwise. For weightstyle=`binnedset', the task will seek for weights in a column named WEIGHTS in the binnedatttab table. If weightstyle=`gti', the task attempts to obtain a list of Good Time Intervals (GTIs), the exact way these are supplied being dictated via the parameter gtistyle; these GTIs are ANDed with the attitude time bins; the net GTI in each bin provides the weight.
gtistyle	no	string	fromimages	user|kwd|fromcubes|gtitablist
This parameter is read if weightstyle=`gti'. In this case the task attempts to obtain a list of Good Time Intervals (GTIs); these GTIs are ANDed with the attitude time bins; the net GTI in each bin provides the weight. Note that matters are complicated by the fact that different CCDs usually have different sets of GTIs. Parameter gtistyle specifies the way in which GTIs are supplied. If gtistyle=`user', the task obtains a single, simple GTI for all chip images from the parameters tstart and tstop. The same is true if gtistyle=`kwd', except that the task expects to the start and stop times in keywords TSTART and TSTOP, (or whatever alternates are specified via parameters tstartkwd and tstopkwd), in the FITS table specified by the parameter kwdtab. The alternate gtistyle=`fromcubes' tells the task to look for GTI extensions (via the KEY2IMGS table, see documentation for chipcube) in the cube sets. The final alternate, gtistyle=`gtitablist', affords the most general and flexible specification of GTIs. In this case the task looks for a list of GTI tables in the parameter gtitablist. Note that this parameter must have the same number of elements as chipcubesets.
tstart	yes	real
This parameter is read if gtistyle=`user'. Specifies the start of the single, universal GTI.
tstop	yes	real
This parameter is read if gtistyle=`user'. Specifies the end of the single, universal GTI.
kwdtab	yes	table
This parameter is read if gtistyle=`kwd'. It gives the FITS table description in which to find the GTI start and stop keywords.
tstartkwd	no	string	TSTART
This parameter is read if gtistyle=`kwd'. Name of the keyword in kwdtab which specifies the start of the single, universal GTI.
tstopkwd	no	string	TSTOP
This parameter is read if gtistyle=`kwd'. Name of the keyword in kwdtab which specifies the end of the single, universal GTI.
gtitablist	yes	table
This parameter is read if gtistyle=`gtitablist'. A list of FITS table descriptions, 1 per input image, which should contain GTI lists.
ra	yes	real
This parameter is read (and only mandatory) if attstyle=`user'.
dec	yes	real
This parameter is read (and only mandatory) if attstyle=`user'.
apos	yes	real
This parameter is read (and only mandatory) if attstyle=`user'.
usefast	no	bool	yes
Whether to use a fast, approximate or slow and accurate regridding algorithm.
conserveflux	no	bool	yes
A CCD pixel covers, in general, a different amount of sky to a sky-image pixel. With some sorts of quantities (eg background rate per pixel) this change of area matters; for others (eg exposure time) it does not. In the former case you should set conserveflux to `yes', in the latter, `no'.
withnormalize	no	bool	no
I am no longer sure what this is about. Best to leave it at default!
tempset	no	dataset	tempset.ds
Name of a temporary dataset. If you are running more than 1 invocation of the task in the same working directory, you should name this uniquely for each invocation, to avoid crosstalk.
Parameter	Mand	Type	Default	Constraints