STOFF @ pA run
20-29 January 2013
F. Bellini for the TOF group
30 January 2013
STOFF shifts @ doodle
We need 2 people/week  please book last 3 slots
Reminder: daily QA meeting @ 15:30 (P2+Vidyo)
LHC13b
Run 195390 without TOF
✗
Maps from DQM
Run 195344
 Stable config!
LHC13b Runs
LHC13b runs – cpass1 (http://alimonitor.cern.ch/prod/jobs.jsp?t=3939):
195483, 195482, 195481, 195480, 195479, 195478, 195391, 195390, 195389,
195351, 1953461, 195344
LHC13b runs – pass1_wSDD(http://alimonitor.cern.ch/prod/jobs.jsp?t=3944):
195483, 195482, 195481, 195480, 195479, 195478, 195391, 195390, 195389,
195351, 1953461, 195344
Good
Good, but without manual calibration ( available for ppass2 from 27/01, see
Savannah #100083, http://savannah.cern.ch/bugs/?100083)
No TOF
No output available yet
1Run with no SDD
Cpass1 - Time alignment and matching efficiency
Good time alignment
Good average matching efficiency = 72%
as expected
Ppass1_wSDD - Time alignment and matching efficiency
Good time alignment
Good average matching efficiency ~ 72%
As cpass1, as expected
Cpass1, ppass1 – TOF time calibration (I)
At cpass1 the TOF times are not fully calibrated
 secondary peaks in the t-texp distribution
correspond to uncalibrated channels
 channel by channel calibration (available since
28/01) should re-align the times, see Savannah
https://savannah.cern.ch/bugs/?100114
 Such calibration was not yet available at
ppass1_wSDD and ppass1_woSDD, therefore the
peaks are still present
cpass1
 Time alignment to be verified after ppass2
ppass1_wSDD
Cpass1, ppass1 – TOF time calibration (II)
Ppass1_wSDD
At cpass1 and ppass1 the TOF times are not fully
calibrated  secondary bands in the t-texp
distribution correspond to uncalibrated channels
Consequence for PID: contamination of the
p band by the pion tail from uncalibrated
channels  effect on nσ-cut PID for p
Usage of the forthcoming ppass2 for
optimal PID performances is
recommended
TOF resolution
LHC13c (with min. bias)
All runs with TOF
LHC13d (with rare triggers)
Run 195869-720 without TOF
✗
✗
LHC13c,d runs
LHC13c runs – cpass1 (http://alimonitor.cern.ch/prod/jobs.jsp?t=3975):
195677, 195676, 195675, 195673, 195644, 195635, 195633, 195596, 195593,
195592, 195568, 195567, 195566, 195532, 195531, 195529
LHC13d runs – cpass1 (http://alimonitor.cern.ch/prod/jobs.jsp?t=3978):
195873, 195872, 195871, 195869, 195867, 195831, 195830, 195829, 195827,
195826, 195787, 195783, 195767, 195765, 195761, 195760, 195727, 195726,
195725, 195724, 195723, 195722, 195721, 195720, 195682, 195681
Good
Bad, to be understood
Output available but no TOF
No output available yet
Low stat (<10k evts)
LHC13c Cpass1
Time alignment and matching efficiency
Good time alignment
Good average matching efficiency = 72% as expected
LHC13d Cpass1
Time alignment and matching efficiency
Good time alignment only for 195721
Hypothesis for the other runs: something wrong in TPC calibration?
 to be understood
Matching efficiency ~ 71%, close to expected
Run 195867 has slightly higher matching eff  to be understood
Run 195682 has low stat
Summary
• Cpass1: 11/12 LHC13b runs with TOF, 9/9 with QA output and TOF analysed
– Time alignment ( Δt < 10 ps) ✔
– Matching efficiency (<ε> ~ 72 %) ✔
– TOF resolution ~ 83 ps ✔
• Ppass1_wSDD: 11/12 LHC13b runs with TOF, 8/8 with QA output and TOF
analysed
– Time alignment ( Δt < 2 ps) ✔
– Matching efficiency (<ε> ~ 72 %) ✔
PID: since full calibration is available only since 28/01,
ppass2 is recommended for analysis and PID studies
Summary
• LHC13c cpass1: 16/16 LHC13c runs with TOF, 8/8 with QA output and TOF
analysed
– Time alignment ( Δt < 10 ps) ✔
– Matching efficiency (<ε> ~ 72 %) ✔
– PID still to be checked
• LHC13d cpass1: 24/26 LHC13d runs with TOF, 6/24 with QA output and TOF
analysed
– Time alignment ( Δt >> 20 ps) for 5/6 runs ✗
– Matching efficiency for 4/6 runs is ok (<ε> ~ 71 %) ✔
– PID still to be checked