100 likes | 172 Views
Trigger systematics on cusp-effect. Spasimir Balev 28.04.2005. Codes to MBX. For version 15.21 of MBX (27.07.2003) and later, MFKTRIG needs L1code0 OR L1code2 . L1code0 : (Q1+Q2) * [ NUT(ntpeakloose) + Q1/10*NUT(LKRminbias) + (Q1*!Q2*1u*!AKL/D4)*(KMU3-PRE) ] L1code2 :
E N D
Trigger systematics on cusp-effect Spasimir Balev 28.04.2005
Codes to MBX • For version 15.21 of MBX (27.07.2003) and later, MFKTRIG needs L1code0ORL1code2. • L1code0: (Q1+Q2) * [ NUT(ntpeakloose) + Q1/10*NUT(LKRminbias) + (Q1*!Q2*1u*!AKL/D4)*(KMU3-PRE) ] • L1code2: (Q1+Q2) * [ Q2*!AKL + Q1/100 + KLrandom ] • In the normal data-taking periods: • 99.9% of triggered by MFAKE events have L1code0 set to 1 • almost all of them pass through NUT(ntpeakloose) • 9.5% of them pass through Q1/10*NUT(LKRminbias) • 31.6% of triggered by MFAKE events have L1code2 set to 1 • 98% of them pass through Q2*!AKL • 3% of them pass through Q1/100
NT-PEAK bad periods • In the bad NT-PEAK periods: • only 26% of the triggered by MFAKE events have L1code0 set to 1 • 93% of them pass through Q1/10*NUT(LKRminbias) • 99% of them have NUT(ntpeakloose) bit set to 1, but it is switched OFF from L1 code • 82% of triggered by MFAKE events have L1code2 set to 1 • 98% of them pass through Q2*!AKL • 3% of them pass through Q1/100 Good events / all events SS0 SS123 15663 15753 15732 15652 15688
70% L1 to MBX inefficiency 40% L1 to MBX inefficiency 3% 0.7% NT-PEAK bad periods (summary) • Bad period [15652 – 15663] • Bad period [15688 – 16732] NT-PEAK with huge rate, switched OFF from L1 to MBX (also switched OFF from L2) • Bad period [15733 – 15753] NT-PEAK is only with Y-projection requirement huge inefficiency • Rejection level for SS123 -18% (only bad periods and removed) • To do: • NUT bad bursts? • They reject mostly events from the bad NT-PEAK periods, but not all of them • May be we can cut the oscillations of NT-PEAK before the bad periods…
Kaon mass vs. day-sample Full SS123 Bad periods rejected <MK> - MKPDG, keV Day-sample
(Q1+Q2) inefficiency Without bad periods 1 and 2 Full SS123 117/140 123/141 Slope: -0.012 ± 0.017 Slope: 0.011 ± 0.015 114/140 123/140 M002 * Control trigger: NT-PEAK (or T0N for NT-PEAK bad periods)
NT-PEAK inefficiency 152/148 Slope: -0.0005 ± 0.0425 Without bad periods 1 and 2 M002 151/147 * Control trigger: 1TRK-P (and L1code0 through Q1/10*NUT(Minbias))
1-TRK-P bit inefficiency Without bad periods 1 and 2 Full SS123 137/148 139/148 Slope: -0.030 ± 0.074 Slope: -0.023 ± 0.075 136/147 138/147 M002 * Control trigger: NT-PEAK (or T0N for NT-PEAK bad periods)
1-TRK-P trigger inefficiency Without bad periods 1 and 2 Full SS123 153/148 178/148 Slope: 0.56 ± 0.20 Slope: 0.63 ± 0.22 151/147 177/147 M002 * Control trigger: T0N
Summary • We have to be careful with the good events in bad NT-PEAK periods, because they are going through different trigger chain (Q2*!AKL) • The rejection of these periods simplify the evaluation of systematics from the trigger, but leads to big distortions in achromat UP/DOWN ratio, which is important for “neutral asymmetry” analysis (but not for cusp-effect). • The c2 of the fits of inefficiency as a function of M002 are practically the same for linear and quadratic fitting function • c2 is good for each component of the trigger chain • The slopes in linear fit are compatible with 0 for each component of the trigger chain and within 3s for the trigger itself