XMM-Newton SAS Home Page
XMM-Newton Science Analysis System


asmooth (asmooth-2.32) [xmmsas_20211130_0941-20.0.0]

Errors

This section documents warnings and errors generated by this task (if any). Note that warnings and errors can also be generated in the SAS infrastructure libraries, in which case they would not be documented here. Refer to the index of all errors and warnings available in the HTML version of the SAS documentation.

outMaskWrongSizeerror 
 outmaskset and inset have different dimensions.
 
wholeImageUnmaskederror 
 There are no TRUE-valued pixels in outmaskset.
 
weightImageWrongSizeerror 
 weightset and inset have different dimensions.
 
exposureMapWrongSizeerror 
 expimageset and inset have different dimensions.
 
weightImageNegativeValueserror 
 Some of the pixels of weightset have negative values.
 
weightImageAllZeroerror 
 All the pixels of weightset are zero-valued.
 
varianceImageWrongSizeerror 
 invarianceset and inset have different dimensions.
 
varianceImageNegativeValueserror 
 Some of the pixels of invarianceset have negative values.
 
inImageNegativeValueserror 
 No variance image was supplied, so the task has tried to use the inset as its own variance image. However this is not possible because some of the pixels of inset are negative-valued.
 
badConvolverStyleerror 
 The value of parameter convolverstyle was not recognized.
 
badExpMapUseerror 
 The value of parameter expmapuse was not recognized.
 
badSmoothStyleerror 
 The value of parameter smoothstyle was not recognized.
 
badUserWidthserror 
 The list of convolver widths userwidths was found not to be monotonically increasing, as it should be.
 
badWidthRangeerror 
 The value of maxwidth was found to be less than or equal to minwidth.
 
tooManyConvolverserror 
 More than 999 convolvers were generated while trying to calculate a library of convolvers from the template image intemplateset.
 
badWidthScaleStyleerror 
 The value of parameter widthliststyle was not recognized.
 
noConvolverserror 
 The user has set smoothstyle=`adaptive' and withuserwidths=`yes', but hasn't supplied any convolvers in userwidths.
 
convolverWidthsBadOrdererror 
 The list of convolver widths userwidths was found not to be monotonically increasing, as it should be.
 
minConvolverWidthEqualsZeroerror 
 This won't work with widthliststyle=log - in this case the user must specify a minwidth greater than zero.
 
badIndexImageerror 
 The maximum index found in the index image exceeds the number of convolvers.
 
zeroNormConvolvererror 
 The sum of the convolver elements is zero. Such convolvers are not allowed.
 
indexImageWrongSizeerror 
 inindeximagearray and inset have different dimensions.
 
indexImageNegativeValueserror 
 Some of the pixels of inindeximagearray have negative values.
 
uselessVarianceImagewarning 
 The user has requested writevarianceset='yes', but the configuration of the task is such that no variance set has been calculated. That is, a variance set for the smoothed output is only calculated if readvarianceset=`yes' or smoothstyle=`adaptive'.
corrective action: A zero-valued variance set is written anyway.
 
outMaskTooNarrowwarning 
 This happens if there are substantial zero-valued areas of weightset which are not masked by outmaskset. The user can avoid this by either reducing the size of the holes in weightset or increasing the coverage of outmaskset.
corrective action: Pixels where this occurs are set to zero in outset and flagged in badmaskset.
 
dynamicRangeTooLargewarning 
 The dynamic range is calculated by dividing max(abs(I)) by median(abs(I), I ne 0), where I is the weighted, exposure-corrected input image. If this value is larger than a cutoff (currently 40000), this warning is issued.
corrective action: No action.
 
onlyOneConvolverwarning 
 The user has set smoothstyle=`adaptive' and withuserwidths=`yes', but has only supplied one convolver in userwidths.
corrective action: Task proceeds as normal.
 
negativeValuesInOutputwarning 
 This warning only occurs if inset, weightset and all convolvers are everywhere non-negative. In this case one might expect that all values of the output image would also be non-negative. However, small negative values can sometimes occur if the FFT was used in the convolution. The user probably ought to check the output to make sure that it looks ok.
corrective action: Such pixels are set to zero.
 
negativeValuesInVarianceOutputwarning 
 Small negative values can sometimes occur if the FFT was used in the convolution. Even if this was the case, the user probably ought to check the output variance image to make sure that it looks ok. If the FFT was not used then it probably indicates a bug and you should contact the code developer.
corrective action: Such pixels are set to zero.
 

XMM-Newton SOC -- 2021-11-30