| NoSourcesFound | error | |
| The eboxdetect
task failed to find any
sources in the image accumulated from the input event list. This is
a very unlikely scenario. If it arises, something is fundamentally wrong
with the input event table. | ||
| WrongSourceCoordinates | error | |
| The reference source coordinates are given
in a wrong/unrecognized format - see above for the correct one. | ||
| NoSourceCoordinates | error | |
| No coordinates have been given for a selected
reference source. | ||
| TooLittleSources | error | |
| Less than two reference sources have been selected.
The above schemes needs at least two because there are three degrees of
freedom. | ||
| NumericalError | error | |
| There has been a numerical error - this should
not happen. | ||
| SourceMismatch | error | |
| The source detection procedure has failed to
uniquely find the user-selected reference source in a newly accumulated
image. Try to increase the source radius. | ||
| maxiterationsReached | error | |
| The maximum number of iterations have been
performed without achieving convergence - this is a very unlikely situation. | ||
| error | ||
| All errors of evselect, eboxdetect, attcalc. | ||
| NegativeSourceCounts | warning | |
| The eboxdetect
task has
computed a negative flux for a found source - this should not happen.
corrective action: ignore source | ||
| PossibleSourceConfusion | warning | |
The task has failed to uniquely
identify the user-selected reference sources in a newly accumulated
image. The source cross-identification is based on a simple integrated
flux criterion which is known to be deficient. There is no real problem
as long as the sources in question are sufficiently spatially separated.
If this is not the case, the algorithm will not abort execution but
the user should see an oscillating behavior in  .
corrective action: ignore | ||
| error | ||
| All warnings of evselect, eboxdetect, attcalc. | ||
