290 likes | 449 Views
Update of analysis of technical run data. T. Spadaro. Outline: done and to do. Done in the past: block by block time resolution T0 correction per column of blocks muon clustering algorithm first studies of time correlation with other detectors Update :
E N D
Update of analysis of technical run data T. Spadaro
Outline: done and to do Done in the past: • block by block time resolution • T0 correction per column of blocks • muon clustering algorithm • first studies of time correlation with other detectors Update: • absolute time-zero correction block by block • Novel time reconstruction for LAV, analysis of hit topologies • Analysis of time distributions and LAV-CHOD correlation To do: • efficiency studies for photons Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Study of hit categories on data Data of run 390: • 1 CHOD candidate and 1 Cedar candidate in time • 1 cluster on LKr in time + 1 additional LKr cluster close in space with CHOD hit • Occupancy of few % Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Study of hit categories on data • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Data of run 390: • 1 CHOD candidate and 1 Cedar candidate in time • 1 cluster on LKr in time + 1 additional LKr cluster close in space with CHOD hit • Event selection aiming at enriching LAV content AnalyzeTDC hit pairs for Low and High threshold of the same physical channel Station 1 status High status Low Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Study of hit categories on data • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Data of run 390: • 1 CHOD candidate and 1 Cedar candidate in time • 1 cluster on LKr in time + 1 additional LKr cluster close in space with CHOD hit • Event selection aiming at enriching LAV content AnalyzeTDC hit pairs for Low and High threshold of the same physical channel Station 2 status High status Low Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Time correlation vs category: complete hits • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low Odd structure at negative and positive times, check if there are other hits for that channel in the same event Plot dTvsNToT(Low) ? dTleading(High-Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Check edge population for complete hits Station 1 status High dTleading(High-Low) (ns) status Low 1 2 3 4 1 2 3 4 1 2 3 4 NToT (Low) NToT (Low) NToT (Low) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Leading-leading category • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low Both trailing edges lost due to HPTDC 5-ns dead time? Is there a contribution from the 3-time-slot acquisition window? Plot dTvsT(DAQ,Low) dTleading(High-Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Check DAQ effect for leading-leading category Station 1 status High status Low TCedar – Tleading(High) (ns) “physics” peak TCedar – Tleading(High) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Check DAQ effect for leading-leading category TCedar (ns) Station 1 status High Tleading(High) (ns) status Low TCedar (ns) Complete Leading-leading Tleading(High) (ns) Tleading(High) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Leading-leading time correlation • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low High-threshold trailing lost, due to HPTDC 5-ns dead time? If so, ToT of Low threshold should be smaller than that for complete hits: Plot vsToT(Low) dTleading(High-Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
High threshold trailing missing High-threshold trailing lost, due to HPTDC 5-ns dead time? If so, ToT of Low threshold should be smaller than that for complete hits ToT(Low) (ns) ToT(Low) (ns) dTleading(High-Low) (ns) dTleading(High-Low) (ns) True, but not always, maybe a DAQ effect is present, too? Check it by plotting also vsTleading high Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Leading-leading time correlation • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low Low-threshold trailing lost, due to DAQ window? Plot dTvsTrail(DAQ, High) dTleading(High-Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Leading-leading time correlation • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low Where are both leading times? Plot vsT(DAQ,Low) Plot vsNToT Plot vsNHit/event dTtrailing(High-Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Trailing-trailing time correlation Station 1 status High status Low TCedar – Ttrailing(Low) (ns) “physics” peak TCedar – Ttrailing(High) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Leading-leading time correlation • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low High-threshold leading lost... ... configuration of low threshold is strange (Tr-Le) Check vsNToT(Low) Check vsT(DAQ,Tr, High) dTtrailing(High-Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Leading-leading time correlation • Hit status definition: • 1: Tr-Tr 4: Le-Tr • 2: Tr-Le 5: Le (only hit) • 3: Le-Le 6: Tr (only hit) Correlate leading hit times Station 1 status High status Low dT(trailing High- leading Low) (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Time calibration from muon run Run 392 (muon run), merged thanks to Giuseppe including LKr info minimal request: 1 CHOD candidate Use muon run for time calibration: rescale all of the LAV times by subtracting the LAV-CHOD time difference Use High-threshold hits, global time resolution < 1 ns Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Time calibration from muon run Use Low-threshold hits, since there is no slewing correction: non-zero offset, ~ -3 ns (compatible with expectation: ~ Trise/2) resolution worse, ~ 2ns Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Check LAV-CHOD correlation CHOD population comparing muon and kaon run muon run YCHOD (cm) XCHOD (cm) kaon run XCHOD (cm) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Check CHOD-LAV alignment, muon run Check time and position correlation with respect to CHOD, Hi-thr a second peak 25-ns away, time-correlated muon run DT (ns) Df (rad) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Check LAV-CHOD correlation Select main time peak, plot a.u. ratio N(CHOD&LAV)/N(CHOD) muon run YCHOD (cm) XCHOD (cm) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Compare muon and kaon run Check time and f correlation with respect to CHOD, low-threshold second peak ~40 ns away from the main peak muon run Df (rad) DTCHOD-LAV(ns) kaon run Df (rad) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Compare muon and kaon run Second peak enhanced in the kaon run and for the low threshold kaon run low threshold DTCHOD-LAV(ns) TLAV (ns) low threshold muon run TLAV (ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Compare muon and kaon run Second peak enhanced in the kaon run and for the low threshold kaon run low threshold muon run high threshold DTCHOD-LAV(ns) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Compare muon and kaon run Second peak related to real muons: reflection of a physics signal muon run high threshold 2 hits in station 1 1 hit in station 1, 1 hit in station 2 DTLAV-LAV (ns) DfLAV-LAV(mrad) Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Compare muon and kaon run Second peak appearance is channel dependent: check high threshold DTCHOD-LAV (ns) muon run Electronic channel of low threshold Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Compare muon and kaon run Second peak appearance is channel dependent: check low threshold DTCHOD-LAV (ns) muon run low threshold Electronic channel of low threshold Update of analysis of Tech. run data - CERN - NA62 PVeto WG
Conclusions and to-do Absolute time-zero correction block by block satisfactory • resolution < 1 ns on the entire LAV station A secondary channel-dependent reflection peak biased the time alignment: • maximum of event occupancy met when (part of) main peak and all of the secondary peak are sampled in the 75-ns DAQ window • main peak is partly cut expect an effect on efficiency • effect of DAQ window has an impact on hit topologies LAV-CHOD correlation studied in muon runs • Second peak related to real muons: reflection of a physics signal • geometrical correlation to be validated with MC Final validation of LAV capability after optimization of HW setup will be done: • muon runs, using specific channels completely contained in the DAQ window • kaon runs, using photons (on going) Update of analysis of Tech. run data - CERN - NA62 PVeto WG