ADTX Threshold Scan RIKEN/RBRC Itaru Nakagawa 1. Run13 ADTX Threshold Scan March 3, 2013 MUID1D...

Preview:

Citation preview

ADTX Threshold Scan

RIKEN/RBRCItaru Nakagawa

1

Run13 ADTX Threshold Scan

• March 3, 2013• MUID1D • HV=Run12 Nominal Setting• MuTrig e-Log entry=#1127

2

Run13 ADTX Threshold Scan Run# Threshold [mV] BBCnVTX [MHz] MUID1D

[events]ST-1 Logic

385751 40 1.39 6.5M AND2385752 60 1.36 4.5M AND2385753 20 1.34 1.6M AND2385754 10 1.32 1.3M AND2385755 100 1.31 2.7M AND2385756 80 1.29 1.6M AND2385757 80 1.27 1.8M OR385758 100 1.26 1.7M OR385759 60 1.25 0.5M OR385760 60 1.24 1.5M OR385761 40 1.23 1.6M OR385762 20 1.22 0.3M OR385763 10 1.22 0.5M OR

3

Fake Hit Rates (South)

Logic=AND2 Logic=OR Logic=OR

Octant-3 doesn’t necessarily stands out -> AND2 effect?

4

Sanghwa’s Gap-by-Gap Threshold Scan

Feb.2013

South St-1 Oct-2 Gap-2 Noisy

5

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]6

Inter Station Comparison (South)

7

Inter Station Comparison (North)

8

Accidental Coincidence Fake SG1 Trigger

• SG1 ~ R_st1 x R_st2 x R_st3

9

Accidental SG1 Prediction

10

Accidental SG1 Prediction

North Octant-1 Stands out, but not Octant-4

11

SG1 Rate Octant Fraction (South)

Red Dot : EmulatorHorizontal Bar : Prediction from Fake Rates

Compares Actual SG1 Trigger Rates/oct from Emulatorand Prediction from Fake hit rates.

Run#385753 : Threshold=20mV

12

SG1 Rate Octant Fraction (North)

Red Dot : EmulatorHorizontal Bar : Prediction from Fake Rates

Run#385753 : Threshold=20mV

Disagree more than 3sigma.Both plots are from same data. Why? Deadtime?

13

Inter Station Comparison (South)

14

Inter Station Comparison (North)

15

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

16

Run12 Eff=95% Config

17

BACKUP

18

(Log)

19

(log)

20

Recommended