(The%20Missing)%20TKR%20TEM%20Diagnostics

1
(No Transcript)
2
(The Missing) TKR TEM Diagnostics

• A brief update on the missing TKR TEM
  diagnostics
• We enabled the 1-shot trigger in the 4 tower data
  runs
• Will be default trigger for all data taking
• Large loss of TKR trigger primitives seen
• NB! Trigger (rate) is OK!
• Last week
• Used '3-in-a-row' combinations to verify the loss
  seen by TKR and Online
• Not ideal
• I only counted as loss the complete absence of
  3-in-a-row combinations in a tower
• Difficult to relate this to loss of indivdual
  trigger requests in a single plane
• We would like to know the loss of TKR TEM
  diagnostics per individual plane

3
TKR Trigger Requests Per Plane

• Look at tower 0 only
• Compare 2 tower (run 135002139) and 4 tower (run
  135002769, 1-shot) data
• Require GemWord2
• i.e. There was a pure TKR trigger in the event
• Require GemTkrVector0gt0
• i.e. There was a TKR trigger in tower 0
• No requirements on the other towers
• i.e. Could also be TKR triggers in the other
  towers
• This assumes there are no timing issues between
  towers as the other tower may have opened the
  trigger window.
• But I should then get the same topology in both
  cases
• For each event
• Look at each TKR plane and end
• Was there a trigger request in that plane/end or
  not
• Plot fraction of events that had a trigger
  request

4
(No Transcript)
5
TKR TEM Diagnostics Summary

• With 1-shot trigger
• 'Factor 10' loss in 3-in-a-row combinations per
  tower
• Factor 2 less trigger requests per plane/end
• Only affects TKR trigger primitives.
• Trigger group think they understand why this
  happens
• TKR trigger requires 6-fold coincidence
• Latest layer of the six makes the coincidence
  happen and opens the trigger window
• Most of the layers assert trigger signal before
  coincidence is made
• Current STRETCH value (700 ns) is too short for
  efficiently latching TKR TEM diagnostics data
• Special test run will be taken to scan STRETCH
  values and look at TEM diagnostic latching
  efficiency.
• Stay tuned ....