60 likes | 173 Views
M. Gorski Part 1. Preliminary results on bad timing of the RPC trigger About a week ago DT claimed that our timing was off by 25 BX in wheel+2 and 5-6 BX in wheel +1. They observed no such effect when RPC trigger was not operational It seems, that the culprit is the TTU trigger.
E N D
M. Gorski Part 1. Preliminary results on bad timing of the RPC trigger About a week ago DT claimed that our timing was off by 25 BX in wheel+2 and 5-6 BX in wheel +1. They observed no such effect when RPC trigger was not operational It seems, that the culprit is the TTU trigger
I considered four classes of events: 1) Both RPC PAC and TTU triggers are on maybe some other triggers present 2) PAC is on, TTU is off, maybe others 3) PAC is off, TTU is on, maybe others 4) PAC and TTU are off, there is other one (otherwise we wouldn't record the event) I plot the BX difference between events (next page)
Only a peak corresponding Peaks at ΔBX 5-7 and 22-25 to trigger rules cutoff Small trigger rules peak
Conclusion: it is only TTU trigger (not accompanied by PAC) which produces bad behavior. Part 2. The mysterious peak at bx=134. It has been observed quite some time ago, that in the distribution of BXses there is a peak around BX 134. Recently it reappeared, see next page.
BX distribution when no TTU BX distribution when only TTU present present – huge peak at BX 134 ±1