Gary Bernstein, 08/28/2012 03:12 PM
*Anom-R6: Processes that are sending entries to the Survey Table identify anomalies that would invalidate an image, including any of the conditions in Anom-R5, plus: meteor/airplane trails that ruin substantial parts of images.*
If whole frames are unusable for one of the reasons in [[Anom-R5]], they might have to be re-observed. The concern for Anom-R6 is for airplane or very-bright-meteor trails that are so bright that they render a good fraction of the exposure unusable. In which case the Survey Table needs to reflect the fact that the exposure needs to be re-taken, so there is an operational issue.
* [[Anom-R5]] must be run.
* A full night's worth of images have been run through standard DESDM pipeline.
* If no bright trails occur, may need to simulate one on an image.
*Check DB output of Image Health / Quick Reduce for the faulty images from [[Anom-R5]].
* *Eyeball examination* of all exposures from the Minisurvey noting where there are bright asteroid/meteor/satellite/airplane trails, particularly if they will invalidate many CCDs' data.
* Check DB output of Image Health / Quick Reduce / DESDM for the bright trail images - are they flagged as problematic?
* Also may ask whether any part of DESDM generates an appropriate mask. _Not sure if there is currently any code in DESDM intended to do this!!_
If flags are raised for a trail that destroys 10% of a chip and all faulty frames from [[Anom-R5]], test is passed.
If masking of tracks is incorrect, secondary test is failed.
If flags are not raised, either IH/QR must be tuned or DESDM must contain code to detect this and report it to the DB.
If masking is incorrect, DESDM codes need to be iterated.
If no sufficiently bad trails have occurred that would destroy an exposure, then perhaps this is not a problem. Ask observers to monitor images for the first few weeks of survey.