200 likes | 331 Views
ADTX Threshold Scan. RIKEN/RBRC Itaru Nakagawa. Run13 ADTX Threshold Scan. March 3, 2013 MUID1D HV=Run12 Nominal Setting MuTrig e-Log entry=#1127. Run13 ADTX Threshold Scan. Fake Hit Rates (South). Logic=AND2. Logic=OR. Logic=OR. Octant-3 doesn’t necessarily stands out
E N D
ADTX Threshold Scan RIKEN/RBRC Itaru Nakagawa
Run13 ADTX Threshold Scan • March 3, 2013 • MUID1D • HV=Run12 Nominal Setting • MuTrige-Log entry=#1127
Fake Hit Rates (South) Logic=AND2 Logic=OR Logic=OR Octant-3 doesn’t necessarily stands out -> AND2 effect?
Sanghwa’s Gap-by-Gap Threshold Scan South St-1 Oct-2 Gap-2 Noisy Feb.2013
Fake Hit Rates (North) Logic=AND2 Logic=OR Logic=OR North Station-3 Octant-1 stands out Vertical Axis : (average hits/strip)/total#of_trigger / 106ns [Hz]
Accidental Coincidence Fake SG1 Trigger • SG1 ~ R_st1 x R_st2 x R_st3
Accidental SG1 Prediction North Octant-1 Stands out, but not Octant-4
SG1 Rate Octant Fraction (South) Compares Actual SG1 Trigger Rates/oct from Emulator and Prediction from Fake hit rates. Run#385753 : Threshold=20mV Red Dot : Emulator Horizontal Bar : Prediction from Fake Rates
SG1 Rate Octant Fraction (North) Run#385753 : Threshold=20mV • Disagree more than 3sigma. • Both plots are from same data. Why? • Deadtime? Red Dot : Emulator Horizontal Bar : Prediction from Fake Rates
Inter Station Comparison (North) Normalized
Load Map to Threshold Optimization • Before Run13 : Thresholds are set to be constant charge efficiencies. • Run13 Concept • R_oct1=R_oct2=R_oct3=…= R_oct8 • Raise threshold of station which has steeper response to threshold regardless of noisy source St. • Analyze Charge efficiency • Eff_AND2 -> [1 - (1-eff_g1xeff_g2)x (1-eff_g3)] • eff_g? = 0.9 => Eff_AND2=0.98 • Eff_OR -> [ 1- (1-eff)^2] • eff=0.9 => eff_OR=0.99