Abstract

LHCb is planning major changes for its data processing and analysis workflows for LHC Run 3. Removing the hardware trigger, a software only trigger at 30 MHz will reconstruct events using final alignment and calibration information provided during the triggering phase. These changes pose a major strain on the online software framework which needs to improve significantly. The foreseen changes in the area of the core framework include a re-design of the event scheduling, introduction of concurrent processing, optimizations in processor cache accesses and code vectorization. Furthermore changes in the areas of event model, conditions data and detector description are foreseen. The changes in the data processing workflow will allow an unprecedented amount of signal events to be selected and therefore increase the load on the experiments simulation needs. Several areas of improvement for fast simulation are currently being investigated together with improvements needed in the area of distributed computing. Finally the amount of data stored needs to be reflected in the analysis computing model where individual user analysis on distributed computing resources will become inefficient. This contribution will give an overview of the status of those activities and future plans in the different areas from the perspective of the LHCb computing project.

Highlights

  • The LHCb experiment will be upgraded for data taking in Run 3 and after [1]

  • A study of the trigger output rates for different physics scenarios is reported in the LHCb Trigger and Online Upgrade TDR [2]

  • Distributed computing and data analysis In the data flow model used in Run 1, the full raw event information is kept up until the end in the processing steps, the stripping, in which a selected subset of triggered events is provided to users for physics analysis

Read more

Summary

Introduction

The LHCb experiment will be upgraded for data taking in Run 3 and after [1]. Tu fully profit from the increase in instantaneous luminosity from 4 × 1032 to 2 × 1033cm−2s−1 the current L0 hardware trigger will be removed, and a full software trigger will be deployed, with the goal of sustaining trigger capabilities up to the inelastic event rate of 30 MHz. 2. Core software framework The stringent requirements on the data processing throughput of the LHCb upgrade imply that the utilization of computing capacities of current and emerging hardware has to be improved both quantitatively and qualitatively.

Results
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call