Request simulations of the interleaved calibration events
Summary
Request simulation samples of the interleaved FF and pedestal calibration events for the array of telescopes. This is required for the end-to-end testing of the camera calibrations for each of the telescopes of the array.
Prior to the request, we need:
-
Identify all the necessary data processing steps for each kind of the telescope in the array -
Should be addressed in #186 (closed)
-
-
Ensure that all required functionality is implemented for each kind of the telescope -
Charge extraction algorithms -
Calibration coefficient derivation methods
-
-
Estimate a minimal required statistics for the "normal operations" -
Define a set of external conditions for simulations (NSB levels, presence or absence of stars, simulations of the possible hiccup events like car flashes, etc.)
Definition of calibration simulations to cover a various set of external conditions:
- Two pedestal levels, the nominal (LST: 0.25 p.e./ns, MSTs: 0.22 p.e./ns, SST: 0.03 p.e./ns) and half moon (LST: 1.20 p.e./ns, MSTs: 1.06 p.e./ns, SST: 1.06 p.e./ns) NSB levels, containing stars in the field of view with a flasher intensity 6.0 p.e./ns (or 72 p.e per 12 ns). 25.000 events for each calibration type (pedestal and flasher events) and for each pedestal level aggregating to 100.000 events in total.
- Raising pedestal level from the nominal to the half moon NSB level containing stars in the field of view with a flasher intensity 6.0 p.e./ns (or 72 p.e per 12 ns) using 50.000 events for each calibration type (pedestal and flasher events).
- Simulating regions of trouble, e.g. car flash - external artificially produced light which affects more than half of the camera pixels. Pedestal level set to nominal and flasher intensity 6.0 p.e./ns (or 72 p.e per 12 ns). using 50.000 events for each calibration type (pedestal and flasher events). One region of trouble to be introduced for ~500 events in the middle of the observation block.
IMPORTANT NOTE:
For testing our camera calibration routines, the usage of a correct timestamp is very important. Especially, for point 2) and 3) the strictly sequential order of recorded events is crucial.
Edited by Tjark.Miener