Project

General

Profile

Anomalies Resource Needs

Number/name of Requirement or Goal: Anom-R1, R2, R3

DECam observations

Anom-R1,R3 are analysed from repeated bias and dome exposures. To be done at Commissioning (or at start SV) and at end SV to test stability.

Data processing needs

  • Raw images available at some off-mountain site? - No
  • Images with cross-talk, debias, trim, dome-flat correction? - Yes

No flattening needed here, but need individual, not combined, bias / dark / dome exposures.

Telescope or other engineering data

Need most recent bad pixel masks.

Codes and scripts for analysing the test data

  • tool for detecting and counting bad pixels by comparing multiple flats and/or biases.
  • comparison of bad-pixel lists
  • code to identify and count cosmic rays in dark exposures.

Personnel:

Are there real-time decisions to be made during the observations? No

How quickly can / must the data be available and analysed? few days

Who will do it, and where?

Number/name of Requirement or Goal: Anom-R4

DECam observations

  • Field(s) to observe: Fields covering and at a series of distances (TBD ???) from 0<m<6 stars
  • Number, duration of exposures per filter: Require some TBD mix of filters, need at least some exposures to be full 100s
  • Dithering / tiling pattern: No dithering required
  • Sky conditions needed (seeing, photometric, moon phase, etc:): no thick clouds; some in thin clouds to check for effect on scattered light.
  • Other timing constraints: none

Data processing needs

  • Raw images available at some off-mountain site? Yes
  • Images with cross-talk, debias, trim, dome-flat correction? Yes

External data sets

Will need to know distance to and mags of the bright stars.

Codes and scripts for analysing the test data

  • Need eyeball inspection of the images for artifacts from scattered light and uncorrected crosstalk.
  • Measurements of diffuse brightness from scattered light.

Personnel:

Are there real-time decisions to be made during the observations? Could be more efficient by eyeballing images as they are taken further from star, to decide when the star's effect has become negligible and one can quit the activity.

How quickly can / must the data be available and analysed? Good to eyeball real-time; can be analysed with few days' delay.

Who will do it, and where?

Number/name of Requirement or Goal: Anom-R5, R6

DECam observations

These requirements require intentional (or accidental) gross defects introduced into images. Single filter will suffice, but should be normal-cadence observations. Need to induce the following problems, if possible:
a. Bad/missing data on one or more amplifiers
b. Dome occulting beam on a photometric night
c. Guider failure
d, e. Exposure badly out of focus
f. Light on in dome.

And if we are lucky, there will be SV exposures with a big meteor trail or airplane. Actually, meteor trails will be very likely, with varying brightness.

Data processing needs

All the data processing steps that are used in alarm systems and Survey Table update must be operating on the images, as we are testing whether the problems are properly diagnosed by them.

And flattened single exposures need to be available somewhere to a team that is identifying meteor trails and other gross features by eye.

Telescope or other engineering data

DIMM data successfully getting into headers.

External data sets

Codes and scripts for analysing the test data

Personnel:

Are there real-time decisions to be made during the observations? Outputs of near-real-time systems like Image Health must be noted.

How quickly can / must the data be available and analysed? At expected operational cadences of the systems under test.

Who will do it, and where?

Other important resources or things to note

Someone should be eyeballing each SV image for some numbers of nights to mark all meteor and airplane trails, so we can follow up how the DM system treats them.