ID monitoring and performance shift: Known Issues

The purpose of this page is to collect all known issues about the ID monitoring and performance shift. Please try to keep this up-to-date.

ID Global

• Hits: in case of PIX and SCT being included in the run at different times. The number of PIX and SCT hit per tracks may be different wrt to reference. If this is the case, agreement between the number of SCT hits, for tracks with at least one hit in the other subdetectors should match the reference.
• Noise: the change in NO levels is currently undestood to be due to the higher luminosity

ID Alignment

• residuals pull X: currently larger residual X pull are observed for PIX barrel. Between run 158045 and 158548 the release has changed from 15.6.10.5 to 15.6.10.7, while reference uses 15.6.8.7. The cause of the discrepancy maybe be due to changes in the reconstruction release. Experts are investigating.
• residuals: currently reference histograms for ES1 and ES2 are different. Investigating the cause of the problem...

ID Alignment performances:

• Kshort: as of July 5, larger width between data and reference plots are expected, due to the update in the reference. Experts are working to fix the problem.
• W->enu: reference is from the MC sample while the data is mostly background.Data vs reference mismatch are expected.

ID Beam spot:

• drop and jump in num prim vtx in corrispondence of trigger prescale changes (TrigKeys) drop and jump in the number of primary vertex distribution is expected

-- GiorgioCortiana - 05-Jul-2010