Timing Structure and Inhomogeneities of the MAGIC Camera

Contents:


  1. Contents:
    1. Introduction
    2. Signal Reconstruction for Different Average Arrival Times
    3. Other Signal Extractors
    4. Size Dependence of Inhomeneities
    5. Conclusions

-> Back to top

Introduction

This study was performed to show that the nonuniformity of the camera in terms of event and charge distribution
Number of used pixels after image cleaning


 is mainly caused by
              Arrival time distribution in camera
Average arrival time per run vs. time

Knowing that on average the RMS of the arrival time distribution over a run is around 2 to 3 (as can be seen in the plot below), it seems obvious that, depending on the average value of the arrival time (see above), a significant fraction of events has very early or very late arrival times.



These events will be preferably located in those parts of the camera with the earliest/latest arrival times.

-> Back to top
-> Back to Introduction

-> Back to top

Signal Reconstruction for Different Average Arrival Times


To show the effect of the signal reconstruction in the given situation on the event distribution in the camera, several nights have been analyzed on the level of calibrated data files.

Night
Sequence
PedRMS
<Q> [FADC cts.]
<N_pe>
<t> [FADC slices]
timeRMS [FADC slices] <Conv>
2004/10/16
41037 6.77 16.8 2.42 5.32 2.11
0.140
2005/05/07
54816 4.85 13.1 1.79 2.54 1.90
0.136
2005/06/01 56839
4.93 13.1 1.94 5.21 1.86 0.146
2005/06/03 57134 4.73 12.9 1.94 6.11 1.83 0.147
2005/06/17 58739 12.5 26.14 3.85 4.88 2.37 0.146
2005/07/01 59832 4.40 12.2 1.91 4.71 1.95 0.151

Three consecutive runs out of each night were analyzed. The night of June 16 obviously contains moon data and is therefore treated slightly differently.

Comparison of extraction window sizes using Digital Filter


Callisto provides an option to adjust the extraction window for cosmics calibration. The original extraction window when starting calliisto is 0-15 for the high- and 3-14 for the low gain. The option, "MJPedestalY2.PulsePosCheck" can be set in the callisto.rc file; by default it is set to "yes". If it is "yes", before actually calibrating the data the  position of the maxima of pulses above some threshold is filled into a histogram for the first 1000 or so events of a data file. Then a new extraction window is defined by taking the mean of the histogram -2.5 slices for the left edge, and the mean +4.5 slices + the integration window size for the right edge.
For each of the nights the data were calibrated with  both options.

The cuts applied to the data  are:
  1.     inner pixels: 10<N(pe) (20<N(pe) for 2005/06/17 -Moon data)
  2.     outer pixels: 40<N(pe) (80<N(pe) for 2005/06/17 -Moon data)
  3.     summed N(pe) of pixels fulfilling 1. or 2. >250
Using these cuts, the distributions of the average arrival times in the inner (top) and outer (bottom) cameras are plotted for the calibration with (blue) and without (red) the pulse position check.

  1.  Average arrival time  per event distribution plot for 2004/10/16
  2.  Average arrival time  per event distribution plot for 2005/05/07
  3.  Average arrival time  per event distribution plot for 2005/06/01
  4.  Average arrival time  per event distribution plot for 2005/06/03
  5.  Average arrival time  per event distribution plot for 2005/06/17
  6.  Average arrival time  per event distribution plot for 2005/07/01
The plots below show the camera plots with the number of events and the average charge in each pixel (bottom plot), when the cuts 1. and 2. above were fulfilled by a pixel (top plot) .
  1.    Events and average N(pe) camera plot for 2004/10/16
  2.    Events and average N(pe) camera plot for 2005/05/07
  3.    Events and average N(pe) camera plot for 2005/06/01
  4.    Events and average N(pe) camera plot for 2005/06/03
  5.    Events and average N(pe) camera plot for 2005/06/17
  6.    Events and average N(pe camera) plot for 2005/07/01
Conclusions that can be drawn from these plots are:
An event by event comparison has been performed for one run out of each night. The arrival time of each pixel was compared for the calibrations with and without the pulse position check, if the pixel had more than 10 N(pe) (20 N(pe) in the case of the 2005/06/17 moon data) reconstructed without the pulse position check. Also, the summed number of photoelectrons of all pixels is compared for each event, provided that the sum is larger than 100 photoelectrons in both calibrations. For the sum it is required that the pixels are reconstructed with more than 10 (20) N(pe) without the position check.
In the following plots, the top panel shows the pixel-by-pixel reconstructed arrival time without the position check versus that with the position check. The vertical lines show the range which the position check restricts the extraction window to. The bottom panels show the reconstructed log10(sum of pixels), i.e., the size of the events without pulse position check versus the size with position check.
  1. Event by event effect of pulse position check for 2004/10/16
  2. Event by event effect of pulse position check for 2005/05/07
  3. Event by event effect of pulse position check for 2005/06/01
  4. Event by event effect of pulse position check for 2005/06/03
  5. Event by event effect of pulse position check for 2005/06/17
  6. Event by event effect of pulse position check for 2005/07/01
The "stripes" along the horizontal are pulses that cannot be found anymore within the restricted extraction window, and therefore the reconstructed arrival time is random. The little pileups around the borders of the position check window seem to come from pulses that can still be reconstructed partially, but are shifted too later times due to being cut off at the border.
The reconstructed event size agrees for the majority of  the events fulfilling the  common cut of minimum 100 N(pe), however, some few per cent below 10^3 are  apparently  reconstructed at significantly smaller sizes than without position check. Again, the amount of partially reconstructed events seems to depend on the size of the tails outside or close to the extraction borders.

-> Back to top
-> Back to Signal Reconstruction

The average arrival time per event on 2004/10/16 (top: inner, bottom outer camera)

Arrival time per event 2004/10/16
-> Back to Signal Reconstruction

The average arrival time per event on 2005/05/07 (top: inner, bottom outer camera)Arrival time per event 2005/05/07

-> Back to Signal Reconstruction

The average arrival time per event on 2005/06/01 (top: inner, bottom outer camera)Arrival time per event 2005/06/01


-> Back to Signal Reconstruction

The average arrival time per event on 2005/06/03 (top: inner, bottom outer camera)Arrival time per event 2005/06/03

-> Back to Signal Reconstruction

The average arrival time per event on 2005/06/17 (top: inner, bottom outer camera)

Arrival time per event 2005/06/17

-> Back to Signal Reconstruction

The average arrival time per event on 2005/07/01 (top: inner, bottom outer camera)

Arrival time per event 2005/07/01

-> Back to Signal Reconstruction
-> Back to top

Camera plots for 2004/10/16 (left: with pulse position check, right: without pulse position check)

Camera plots for with pos. check 2004/10/16Camera plots w/o pos. check for 2004/10/16
-> Back to Signal Reconstruction

Camera plots for 2005/05/07 (left: with pulse position check, right: without pulse position check)

Camera plots with pos. check for 2005/05/07Camera plots w/o pos. check for 2005/05/07
-> Back to Signal Reconstruction

Camera plots for 2005/06/01 (left: with pulse position check, right: without pulse position check)

Camera plots with pos. check for 2005/06/01Camera plots w/o pos. check for 2005/06/01
-> Back to Signal Reconstruction

Camera plots for 2005/06/03 (left: with pulse position check, right: without pulse position check)


-> Back to Signal Reconstruction

Camera plots for 2005/06/17 (left: with pulse position check, right: without pulse position check)

Camera plots with pos. check for 2005/06/17Camera plots w/o pos. check for 2005/06/17
-> Back to Signal Reconstruction

Camera plots for 2005/07/01 (left: with pulse position check, right: without pulse position check)

Camera plots with pos. check for 2005/07/01Camea plots w/o pos. check for 2005/07/01
-> Back to Signal Reconstruction
-> Back to top

Event by event comparison: No pulse position check vs. pulse position check for 2004/10/16

Event comparison of pos. check 2004/10/16
-> Back to Signal Reconstruction

Event by event comparison: No pulse position check vs. pulse position check for 2005/05/07

Event comparison of pos. check 2005/05/07
-> Back to Signal Reconstruction

Event by event comparison: No pulse position check vs. pulse position check for 2005/06/01

Event comparison of pos. check 2005/06/01

-> Back to Signal Reconstruction

Event by event comparison: No pulse position check vs. pulse position check for 2005/06/03



-> Back to Signal Reconstruction

Event by event comparison: No pulse position check vs. pulse position check for 2005/06/17

Event comparison of pos. check 2005/06/17

-> Back to Signal Reconstruction

Event by event comparison: No pulse position check vs. pulse position check for 2005/07/01

Event comparison pos. check 2005/07/01
-> Back to Signal Reconstruction


-> Back to top

-> Back to top

Other Signal Extractors

It was checked whether other signal extractors reduce/do not show/enhance the timing-camera nonuniformity correlation.  The other signal extractors used were the  "Sliding Window" with a 6(8) slice integration window for the high (low) gain and the Spline integrating over 1 (1.5) slices in the high (low) gain. The extraction window edges of the pulse position check option were set to the same values as for the Digital Filter (-2.5/+4.5+integration size from the mean) .  The result can be summarized as follows:

-> Back to top
-> Back to Other Signal Extractors

Camera plots for 2005/06/01 using Spline (left: with pulse position check, right: without pulse position check)

Camera plots for 2005/06/01 w/splineCamera plot for 2005/06/01 spline, w/o pos. check
-> Back to Other Signal Extractors

Camera plots for 2005/06/01 using Sliding Window (left: with pulse position check, right: without pulse position check)

Camera plots for 2005/06/02 sw w/o pos.check
-> Back to Other Signal Extractors

Camera plots for 2005/05/07 using Sliding Window (left) and Spline (right) without pulse position check

Camera plots for 2005/05/07 using spline
-> Back to Other Signal Extractors
-> Back to top

The average arrival time per event on 2005/06/01 using Spline  (top: inner, bottom outer camera)



-> Back to Other Signal Extractors

The average arrival time per event on 2005/06/01 using Sliding Window  (top: inner, bottom outer camera)



-> Back to Other Signal Extractors

The Average Reconstructed Charge per Pixel as a Function of the Arrival Time for Three Extractors

Average Charge vs. arrival time per pixel

-> Back to Other Signal Extractors

The Reconstructed Charge per Pixel as a Function of the Arrival Time for Three Extractors



-> Back to Other Signal Extractors

-> Back to top

-> Back to top

Size Dependence of Inhomeneities

The influence of a lower event size cut has been investigated. (Note that the event size used here is not the same as the one used in the hillas files, as there is no image cleaning applied). Below the camera plots are shown for 2005/06/01, using a size cut of
  1. 250 N(pe)
  2. 500 N(pe)
  3. 1000 N(pe)
  4. 4000 N(pe)
The camera images seem to be a little bit smoother for size cuts above 500, however, the nonunoformity rermains to some degree. Between size cuts of 500 and 2000 the picture does not change much, at size > 4000 the nonuniformity gets stronger, though.
The logarithm of the average event size is shown below against the average arrival time of the event. Also there, a strong dependence of the average event size on the arrival time can be seen, especially at the early arrival times. The rise at late times might as well be due to physics reasons. This needs to be checked further.
 
-> Back to top
-> Back to Size Dependence

Camera plots for 2005/06/01 with size>250 (left) and size>500 (right) pe without pulse position check

Camera plots for size > 250
-> Back to Size Dependence

Camera plots for 2005/06/01 with size>1000 (left) and size>4000 (right) pe without pulse position check

Camera plots for size > 1000Camera plots with size > 4000
-> Back to Size Dependence
-> Back to top

Average of event size (above 100) vs. the average arrival time of the event (night of 2005/06/01)

Event size vs. avg. arrival time

-> Back to Size Dependence

-> Back to top

-> Back to top

Conclusions

The inhomogeneity of the MAGIC camera with respect to the event and charge distributions seems to be generated by the spatial distribution of the arrival times in the camera. This in turn is caused by the setup of the  trigger delays for the different macro cells. The arrival time  distribution generates arrival time differences between events of up to 2 slices, depending on the position in the camera where the trigger was generated.  Therefore, even with moderate mean arrival times (>4 FADC slices), the arrival time RMS is relatively large. This means that always some part of the events has very early (resp. late) arrival times and is not being reconstructed correctly, i.e, the events are lost or  reconstructed with a too small charge.
This effect is even stronger, if the mean arrival times are in general very early (late), as it happened for instance very often in May.
The effect is usually enhanced by the software (callisto) if the default pulse position check is switched on. It should be clear that shifting the lower edge of the signal extraction window 2 slices up (typical for the pulse position check) is basically the same as shifting the mean of the arrival time 2 slices down.

What should be on the "To Do List" is the following:
-> Back to top

patty@mppmu.mpg.de