50 likes | 186 Vues
This report discusses the PU Peak2 cut impacts on yield versus luminosity, along with L1 VeloClusters cut effects. Notable findings include errors on both sides that have since been corrected. It highlights issues where L1 returns were incomplete if L0 was false, and a dimuon trigger error. The report includes insights from Marko Zupan regarding solid and dashed curves representing data points. Additionally, discrepancies in L1 efficiency due to low statistics are addressed, alongside updates on ongoing statistics collection for improved high luminosity metrics.
E N D
PU Peak2 and Multiplicity Cuts • PU peak2 cut: yield versus lumi • Timing: L1VeloClusters cut • Status of note on L1L0 eff vs mult. cuts
PU peak2 cut: Yield vs Lumi • Marko Zupan and MFL • Two errors found on both sides (all fixed now): • Both: L1 returns incomplete if L0=false • MZ: dimuon was never triggering • MFL: forgot to recalculate ratio of ncoll>0 / ncoll=0 which depends on luminosity • Still waiting for full stats to get better numbers at high luminosity. Currently: • MZ: 200k MBIA, 2300 Bs->DsK • MFL: 500k MBIA, 2300 Bs->DsK
Yield and Effs. vs Lumi • Marko Zupan: solid symbols with dashed curve • MFL: open symbols with solid curve • Triangles: no pk2 cut • Circles: pk2 cut = 3 • Still some discrepancy left in L1 eff. Due to low stats ? To be understood…
Gain in L1 time and L1VeloClusters cut No cut No cut L0: No pk2 and multipl. cuts L0: nominal pk2 and multipl. cuts
L1L0_multipl_cuts note • The note is on its way • Circulate draft before the week-end