SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Trigger Report

gina avatar
gina
37 diapositives · 605 Views · Sep 20, 2014

Trigger Report. UIC Group 012605. Outline . Trigger Status Update of trigger work Problems found and its solutions T0s’ satellites – beam leakage from central orbit Current and future trigger work ZDC Calibrations Bzero Runs Report. General Trigger Status.

#trigger report #trigger report ppt #powerpoint #presentation
Trigger Report - slide 1
01 / 37Trigger Report
1 / 17

Télécharger la présentation

Trigger Report
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Trigger Report UIC Group 012605

  2. Outline • Trigger Status • Update of trigger work • Problems found and its solutions • T0s’ satellites – beam leakage from central orbit • Current and future trigger work • ZDC Calibrations • Bzero Runs Report

  3. General Trigger Status • Trigger declared commissioned starting with run 16185 (on 1/12/05). • Few problems have been found along the way, none of them however have jeopardized the integrity of the data taken • Trigger has stable for a couple of weeks now • No mayor changes planned for the trigger in the near future • Concentrating now in monitoring and software side of the trigger

  4. Bit  Bit Name On/Off Scaledown 0 PN 0 0 1 PP 0 0 2 T0N 0 0 3 T0P 0 0 4 PN*PP_WIDE 1 - 5 T0N*T0P_NARROW 1 - 6 SPEC*TOF 0 - 7 CC/N 0 - 8 HEARTBEAT_L0 0 - 9 TIMECAL 1 - 10 PEDESTAL 0 - 11 PCAL_COSM 0 - 12 SPEC_LED 0 - 13 ZDCTRIG_L0 0 - 14 CC 1 - 15 VETO 1 - Trigger Configuration CuCu200IsColVertex Start Validity time 01/19/2005 18:22:02 L0

  5. Bit  Bit Name On/Off Scaledown 16 L0 1 1024 17 PP*PN(n)_NARROW 1 64 18 PP*PN_NARROW 0 0 19 PP*PN_WIDE 0 0 20 T0N*T0P_NARROW 1 256 21 Spare 0 0 22 PP*PN_beamgas 0 0 23 (T0N*T0P)*VTX 0 - 24 HEARTBEAT_L1 1 - 25 PP*PN(n>0)*ZDC 0 - 26 PP*PN(N>0)_IsCol 0 - 27 VTX(T0)_IsCol 1 - 28 UTM 0 - 29 ZDCTRIG 0 - 30 Spare 0 - 31 BUSY 1 - L1

  6. Update of trigger work 1 • TEQ values for T0 counters finalized. • TAC settings finalized and stable • CuCu200Veretex trigger configuration finalized and stable Minimum Bias Runs (PdlWideOpen )

  7. CuCu200Vertex Runs

  8. Update trigger work 2 • TEQ values for paddle counters set and stable Before TEQ After TEQ

  9. Problems and its solutions • Level 1 efficiency problem found due to fast clear problem. Solved by routing the FC TDC signals using a cable in the FB front panel. • Deficiency on the number of counts from one of the negative T0 counters (8). The problem was due to a problem with the FB time calibrations • Serious problem with the paddle OR, significant shift in the paddle time difference. Problem was due to processing of the data with different FB calibrations. • TDC 4 problems, or widening of the peaks of the calibration spectra for the paddle counters. The cause for this was at the end correlated to the increase of the rate of the time calibrator.

  10. T0’s satellites • Based on studies, these events seem to be real collisions that are induced by collisions among the beam’s satellite bunches, that is, beam leakage from central orbit . Minimum Bias Runs (PdlWideOpen )

  11. The number of collision events from the central bucket seems to depends on the store and store’s age.

  12. T0’s satellites for CuCu200Vertex runs • Percent of events from central buckets much larger due to the cut in the vertex trigger

  13. ZDC Discriminator Thresholds

  14. ZDC Calibrations • Identify and set the 1n peak in different ADC channels (total sum, and individual modules) to 100 GeV or 1 neutron • For hardware sum the resolution seems to be better for negative that for positive side

  15. ZDC Calibrations soft sum

  16. Method 1 Method 2

  17. Method 1 Method 2

  18. Module P2 Module N2

  19. Bzero Run Set • Run Numbers 16361 – 16279 • Taken from 1/14/05 to 1/16/05 • Number of events ~ 21M • Trigger configurations • CuCuMinimumBias (80%) • PdlWideOpen (14%) • T0NarrowOpen (6%)

  20. BZero Runs Trigger Check • TCut PdlTDiff = "abs(PdlTDiff+0.77)<5"; • TCut ZDC = "TrgT.ZDCSumP>420&&TrgT.ZDCSumN>420&&(TrgT.ZDCSumP+TrgT.ZDCSumN)<1110 • TCut PdlSum = "PdlP>400&&PdlN>300"; • TCut HB = "(L1&0x0100)==0"; • TCut IsCol = PdlTDiff&&HB&&(ZDC||PdlSum); • TCut GoodL0 = "(L0&0x0f00)==0"; • TCut GoodT0Time = "TrgT.Extra[19]>0&&TrgT.Extra[20]>0"; • TCut NarrowT0Time = "abs(TrgT.Extra[19]-TrgT.Extra[20]+9.83)<30"; • TCut CleanOctVtx = "abs(15.*(TrgT.Extra[19]-TrgT.Extra[20]+9.83)-OctagonVertex.vz)<30"; • TCut CleanNewOctVtx = "abs(15.*(TrgT.Extra[19]-TrgT.Extra[20]+9.83)-NewOctagonVertex.vz)<30"; • TCut CleanOctDeVtx = "abs(15.*(TrgT.Extra[19]-TrgT.Extra[20]+9.83)-OctDeVertex.vz)<30"; • TCut CleanCorOctDeVtx = "abs(15.*(TrgT.Extra[19]-TrgT.Extra[20]+9.83)-CorOctDeVertex.vz)<30"; • TCut CleanT0Time = GoodT0Time&&"abs(TrgT.Extra[19]-TrgT.Extra[20]+9.83)<2.6"; • TCut CleanT0_19 = "abs(TrgT.Extra[19]-297.49)<2.5"; • TCut OffloT0_19 = "abs(TrgT.Extra[19]-292.49)<2.5"; • TCut OffhiT0_19 = "abs(TrgT.Extra[19]-302.49)<2.5"; • TCut CleanT0_20 = "abs(TrgT.Extra[20]-307.25)<2.5";

  21. Percent of number of events with good L0

  22. Percent of number of events with good L1

  23. Paddles gain stability

  24. Percent of time calibrator events

  25. Paddle Mean

  26. ZDCs

  27. T0 time difference Tcut