Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Closed Access logo, derived from PLoS Open Access logo. This version with transparent background. http://commons.wikimedia.org/wiki/File:Closed_Access_logo_transparent.svg Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Archivio istituziona...arrow_drop_down
image/svg+xml Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Closed Access logo, derived from PLoS Open Access logo. This version with transparent background. http://commons.wikimedia.org/wiki/File:Closed_Access_logo_transparent.svg Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao
addClaim

LHCb Computing TDR

Authors: G. Avoni; BALBI, GABRIELE; M. Bargiotti; BERTIN, ANTONIO; D. Bortolotti; M. Bruschi; CARBONE, ANGELO; +20 Authors

LHCb Computing TDR

Abstract

The Offline Computing system must allow the LHCb physicists to perform an efficient processing of the collected data (about 20 billion events a year), an accurate alignment and calibration of the sub-detectors and an efficient selection of events of interest as well as provide facilities for extracting physics results from the selected samples. The measurements aimed at by LHCb require a very high precision; hence systematic errors must be mastered to a very high degree. Amongst the 2 kHz of HLT-accepted events, a large fraction is dedicated to a very precise calibration and understanding of the detector and its capabilities. Each group of physicists working on specific decay modes of B-particles will only handle a limited number of events; hence they rely heavily on a full central processing chain from the raw data to very elaborated and pre-selected reconstructed data. It is expected that individual analyses will cope with only a few million pre-selected events while manipulation of larger datasets will be handled centrally by a production team. The Computing project is responsible for providing the software infrastructure for all software data processing applications (from L1 trigger to event selection and physics analysis). It is also in charge of coordinating the computing resources (processing and storage) as well as providing all the tools needed to manage the large amounts of data and of processing jobs. In order to develop efficiently the software, for example developing L1 or HLT applications using simulated data, it is beneficial to implement a high level of standardisation in the underlying software infrastructure provided. Algorithms must be able to be executed in very different contexts, from the Online Event Filter Farm to a physicist’s laptop. The Core Software sub-project is in charge of providing this software infrastructure. The large amounts of data and of computing power needs imply that data processing must be performed in a distributed manner, taking best advantage of all resources available throughout the sites that allow the collaboration to use their resources. These resources (CPU and storage) are expected to be accessible through a standard set of services provided to all LHC experiments but also to the larger HEP community and beyond. The LHC Computing Grid project [4] is expected to provide these resources. The LHCb Collaboration is fully committed to participate in the LCG by utilising and contributing to the common software projects as well as making full use of LCG computing Grid infrastructure. It is expected that LHCb will be able to benefit from the developments made inside LCG or available through LCG. In particular, the offline software uses the software developed by the LCG Applications Area. The distributed computing (data management and job handling) uses the Grid infrastructure deployed by LCG as well as baseline services provided through the LCG.

Country
Italy
Keywords

LHCb; LHC;

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
Powered by OpenAIRE graph
Found an issue? Give us feedback
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
0
Average
Average
Average
Upload OA version
Are you the author of this publication? Upload your Open Access version to Zenodo!
It’s fast and easy, just two clicks!