![]() |
![]() |
|
SAS watchout page
My BACKSCAL (or effective area) has crazy values: help!When backscale or arfgen look at the spatial region used to extract a particular spectrum, they expect to find a region defined in POS(X,Y), DET(DETX,DETY) or EQPOS(RA,DEC) coordinates. However in some circumstances evselect or xmmselect produce a region with the units AXIS2D1(X,Y) or AXIS2D1(DETX,DETY). In general this axis is misinterpreted by the tasks, and causes them to calculate wrong values (often wildly wrong).If bad pixel correction is switched on (withbadpixcorr=yes) this can sometimes be detected by an unfeasibly high bad pixel correction factor in the task output (when SAS_VERBOSITY>=4), e.g.:
This problem has so far been detected in two cases:
The workaround for this problem is straightforward. It is sufficient to use a FITS editor (such as fv) to change the AXIS2D1 string to the right value, e.g. change DSTYP3 = AXIS2D1(Y,X) to DSTYP3 = POS(Y,X), or DSTYP5 = AXIS2D1(DETX,DETY) to DSTYP5 = DET(DETX,DETY), and then run backscale and/or arfgen again.
For complicated spatial regions the identifier may be
AXIS2D2 or AXIS2D3, but
the same principle applies. |
| Copyright 2012© European Space Agency. All rights reserved. |