Software Team and Support for Production

1. Software Team and Support for Production David Hutchcroft

2. Staff • David Hutchcroft (Liverpool) • Girish Patel (Liverpool) • Tara Shears (Liverpool) • Mark Tobin (Liverpool) • David Jones (Liverpool) • Kurt Rinnert (Liverpool) • Lisa Dwyer (Liverpool/PhD student) • Ronan McNulty (UCD) • Karol Hennessy (UCD) D. Hutchcroft

3. VELO software project • The VELO software team is based both at Liverpool, Glasgow, UCD and CERN • UCD have associate membership of LHCb and have collaborated with Liverpool over many years • Task are split • Liverpool is leading the digitisation and reconstruction effort and description of the detector • Glasgow is leading the alignment and simulation effort • All are responsible for testbeam analysis of final detector (called ACDC) • Software staff support ALL aspects of the build D. Hutchcroft

4. Core Tasks • Tracking • Pattern recognition • 2D and 3D • Track fitting • Kalman filter based track fit • Alignment • Measuring and correcting the sensor positions • Raw data formats • Simulation of data stream output • Interpretation of raw data stream • Monitoring • Making plots to monitor reconstruction performance • Monitoring of detector conditions and position D. Hutchcroft

5. Physics analysis • Velo is both “VErtex LOcator” and main tracking detector • 8 times as many sensitive planes as rest of the detector! • Need to optimise code for B vertex reconstruction • Proper time resolution for Bs mixing • Vertex position and mass resolution for S/B rate improvements • Trigger optimisations to improve 2D and 3D identification of B vertices • When LHCb data is available • measurement of CKM angles • measurement of b hadron properties • searches for decay rates modified by supersymmetry D. Hutchcroft

6. Module production • Test on sensors, pitch adapters, hybrids, beetle chips and supports • All data from tests logged in database and analysed to check within tolerances • Girish Patel, David Hutchcroft, Tara Shear and Lisa Dwyer • Tests are performed on Beetle chips after bonding to hybrids • Get noise rates • Last chance to reject bad chips • Mark Tobin, Kurt Rinnert and Girish Patel • Laser tests are performed on finished modules • Check every sensor channel is bonded • Check sensor response across full surface • Look for induced shorts between channels • Mark Tobin, Kurt Rinnert and Girish Patel D. Hutchcroft

7. Tests after construction • Burn in tests • Use a TELL1 readout board to run the sensors in the vacuum tank at Liverpool • Repeat the burn in at CERN • Karol Hennessy, Mark Tobin, David Jones and Kurt Rinnert • ACDC • After modules mounted on base plate at CERN • Read out (up to 5) modules with full readout electronics • Use testbeam to validate reconstruction code • Get initial pass as to internal misalignments • CMM and testbeam reconstruction • David Hutchcroft, Mark Tobin, David Jones, Kurt Rinnert, Tara Shears, Lisa Dwyer, Karol Hennessy and Ronan McNulty D. Hutchcroft

8. Summary • Software team will contribute to all aspects of the module qualification and testing • All of our team are already testing hardware components • Also analysing data taken from each of the component and module tests D. Hutchcroft