Difference between revisions of "TOF Calibration"

From GlueXWiki
Jump to: navigation, search
Line 1: Line 1:
One place to start learning about TOF calibration is with the location of the source code on github where one finds a README file explicitly listed at the bottom of the [https://github.com/JeffersonLab/hd_utilities/tree/master/TOF_calib '''''code listing'''''].
+
One place to start learning about TOF calibration is with the location of the source code on github where one finds a README file explicitly listed at the bottom of the [https://github.com/JeffersonLab/hd_utilities/tree/master/TOF_calib '''''code listing''''']. Note that the tof calibration code itself is located in the git repository '''hd_utilities''' in the directory '''TOF_calib''' and consists mostly of root scripts controlled by regular shell scripts. These calibration procedure requires root input files that contain the TOF raw data. These root files are created using the plugin '''TOF_calib''' located in the github repository '''halld_recon''' in '''src/plugins/Calibration/'''.
  
 
A more details description of the calibration procedures and basic ideas behind the approach can be found in a GlueX document
 
A more details description of the calibration procedures and basic ideas behind the approach can be found in a GlueX document

Revision as of 13:59, 23 February 2022

One place to start learning about TOF calibration is with the location of the source code on github where one finds a README file explicitly listed at the bottom of the code listing. Note that the tof calibration code itself is located in the git repository hd_utilities in the directory TOF_calib and consists mostly of root scripts controlled by regular shell scripts. These calibration procedure requires root input files that contain the TOF raw data. These root files are created using the plugin TOF_calib located in the github repository halld_recon in src/plugins/Calibration/.

A more details description of the calibration procedures and basic ideas behind the approach can be found in a GlueX document tofcalib.pdf. It is not up to date regarding the functional form that is used for the walk correction fit but the basic ideas remain the same.

Calibration

The TOF calibration is manly focused on timing, the most important observable the TOF detector is providing. The main correction to the measured time from any given PMT is the walk correction caused by the fact that leading edge discriminators are used to generate the logical signal from the analog PMT signal. Up to now this walk correction has been determined by the shape of the two dimensional distribution of time vs. ADC integral where the time has been referenced to the time as reported by the flash ADC integral. This has the disadvantage that for high rate paddles close to the photon beam line the integral can be distorted due to pile up. A better approach is to use the ADC peak amplitude instead. However such a distribution requires a different functional form as a model. In addition it is also no longer possible to model the full ADC range with one functional form for all paddles at all locations and still have a stable procedure. Instead the ADC region is divided in two with the location of the separation being the dip before the rise of the minimum landau distribution in the ADC response function.

  1. The functional form has four parameters and is as follows:
    a + b*pow(ADC,-0.5) + c*pow(ADC,-0.33) + d*pow(ADC,-0.2)
    The two distinct fit regions are indicated by the two colors blue and red, the jump at ADC 4090 is due to overflow and binning effects.
    The vertical axis is Ttdc-Tadc, the horizontal axis is ADC amplitude.
    Walk fit example.jpg
  2. Using this approach for the walk correction and leaving the rest of the calibration procedure
    the same leads to much more stable results for the timing offsets over the whole running period.
    Here we show paddle 9 with both PMTs on either end.
    Note the variation of the offsets is very small (<10ps) for these two PMTs
    Tpar paddle9.jpg
  3. The stability of the PMT response over the run period is shown here for PMT10.
    In this particular instance the gain reduction is about 5%.
    Adc vs time pmt10.jpg