Difference between revisions of "Data Analysis - Timing Windows and Reference Times"

From Xem2
Jump to navigationJump to search
(Created page with "==Reference Times== <font size=+1>The reference times must be determined before moving onto the timing windows.</font> We use multihit TDCs and ADCs, which can have multiple...")
 
Line 1: Line 1:
 
==Reference Times==
 
==Reference Times==
<font size=+1>The reference times must be determined before moving onto the timing windows.</font>  We use multihit TDCs and ADCs, which can have multiple hits recordedGiven the rate of physics triggers, and the wide width of the drift chamber reference time, it is quite likely the wrong hit is takenWe shrink the timing windows by cutting on the raw adc or tdc spectra
+
 
 +
===Selecting Proper Reference Times===
 +
Reference times are a copy of the pre-trigger that is distributed to all read-out controllers (ROCs), which subsequently read out the detector signals associated with the signal. Hall C uses multi-hit TDCs and ADCs, so there can be multiple hits within the match window width of the TDC or within the programmable trigger window of the ADCThe reference time is subtracted from the detector signals within hcana, and '''hcana uses the first hit within the window if multiple hits are present.'''  The number of hits within a TWW or PTW is dependent on the physics data rate, the TWW or PTW length, and the number of pre-triggers required to fire the DAQ.  Refer to accidental rate exercise below to understand this more.  In order to subtract the correct reference time from all detectors, we must set the reference time, which decreases the probability hcana chooses the incorrect hit in the ADC or TDC of the reference time (copy of the pre-trigger).  This type of data analysis procedure is generally considered a 'Cut' because we are restricting ourselves to the data that falls after or within a range that is motivated by physics.
 +
Carlos Yero has created an '''Analysis Notes''' document, which contains important information about the possible reference times in different trigger configurationsMost of the information in this section is based on that document.
 +
; Carlos Yero DocDB ref. 1032 v1.
 +
 
 +
===Accidental Rate Example===
 +
 
 
{| class="wikitable"
 
{| class="wikitable"
 
!colspan="3"|Online Running Information
 
!colspan="3"|Online Running Information

Revision as of 11:27, 1 September 2021

Reference Times

Selecting Proper Reference Times

Reference times are a copy of the pre-trigger that is distributed to all read-out controllers (ROCs), which subsequently read out the detector signals associated with the signal. Hall C uses multi-hit TDCs and ADCs, so there can be multiple hits within the match window width of the TDC or within the programmable trigger window of the ADC. The reference time is subtracted from the detector signals within hcana, and hcana uses the first hit within the window if multiple hits are present. The number of hits within a TWW or PTW is dependent on the physics data rate, the TWW or PTW length, and the number of pre-triggers required to fire the DAQ. Refer to accidental rate exercise below to understand this more. In order to subtract the correct reference time from all detectors, we must set the reference time, which decreases the probability hcana chooses the incorrect hit in the ADC or TDC of the reference time (copy of the pre-trigger). This type of data analysis procedure is generally considered a 'Cut' because we are restricting ourselves to the data that falls after or within a range that is motivated by physics. Carlos Yero has created an Analysis Notes document, which contains important information about the possible reference times in different trigger configurations. Most of the information in this section is based on that document.

Carlos Yero DocDB ref. 1032 v1.

Accidental Rate Example

Online Running Information
Responsibility Check Frequency Reporting Sections
Casey Morean Every kinematic change Commissioning Activity
Every trigger change Page on XEM Web JSROOT

Timing window Calibration

Online Running Information
Responsibility Check Frequency Reporting Sections
Casey Morean Every kinematic change Commissioning Activity
Every trigger change Page on XEM Web JSROOT