001282371 001__ 1282371
001282371 003__ SzGeCERN
001282371 005__ 20180529220150.0
001282371 0247_ $$2DOI$$a10.1016/j.nuclphysbps.2011.04.011
001282371 0248_ $$aoai:cds.cern.ch:1282371$$pcerncds:FULLTEXT$$pcerncds:CERN:FULLTEXT$$pcerncds:CERN
001282371 035__ $$9Inspire$$a918393
001282371 037__ $$aATL-DAQ-PROC-2010-026
001282371 041__ $$aeng
001282371 088__ $$9ATL-COM-DAQ-2010-117
001282371 100__ $$0AUTHOR|(CDS)2077430$$9#BEARD#$$aSutton, Mark$$uSheffield U.
001282371 110__ $$aThe ATLAS collaboration
001282371 245__ $$aThe performance of the ATLAS Inner Detector Trigger algorithms in pp collisions at the LHC
001282371 269__ $$aGeneva$$bCERN$$c01 Aug 2010
001282371 260__ $$c2011
001282371 300__ $$a4 p
001282371 520__ $$aThe ATLAS Experiment, Inner Detector trigger algorithms have been running online during data taking with proton-proton collisions at the Large Hadron Collider (LHC) since December 2009. Preliminary results on the performance of the algorithms in collisions at a centre-of-mass energies of 900GeV and 7TeV are discussed. The ATLAS trigger performs the online event selection in three stages. The Inner Detector information is used in the second and third triggering stages, referred to as Level-2 trigger (L2) and Event Filter (EF) respectively, or collectively as the the High Level Trigger (HLT). The HLT runs software algorithms on large farms of commercial CPUs and is designed to reject collision events in real time, keeping the most interesting few events in every thousand. The average execution times per event at L2 and the EF are around 40~ms and 4~s respectively and the Inner Detector trigger algorithms can use only a fraction of these times. Within these times, data from interesting regions of the Inner Detector have to be read out through the network, unpacked, clustered and converted to the ATLAS global coordinates. The pattern recognition follows to identify the trajectories of charged particles (tracks), which are then used in combination with information from the other subdetectors to accept or reject events depending on whether they satisfy certain trigger signatures.
001282371 540__ $$3Preprint$$aCC-BY-4.0
001282371 594__ $$aPROC
001282371 595__ $$aCERN CDS-Invenio WebSubmit
001282371 65017 $$2SzGeCERN$$aDetectors and Experimental Techniques
001282371 65027 $$2SzGeCERN$$aDAQ and Trigger
001282371 6531_ $$9CERN$$aTrigger
001282371 6531_ $$9CERN$$aInner Detector
001282371 6531_ $$9CERN$$aATLAS
001282371 6531_ $$9CERN$$aLHC
001282371 693__ $$aCERN LHC$$eATLAS
001282371 690C_ $$aCERN
001282371 690C_ $$aINTNOTE
001282371 690C_ $$aPUBLATLAS
001282371 690C_ $$aINTNOTEATLASPUBL
001282371 690C_ $$aARTICLE
001282371 710__ $$5PH-EP
001282371 773__ $$c211-214$$n1$$pNucl. Phys. B, Proc. Suppl.$$v215$$y2011
001282371 859__ [email protected]
001282371 8564_ $$uhttps://cds.cern.ch/record/1280910$$yOriginal Communication (restricted to ATLAS)
001282371 8564_ $$uhttps://cds.cern.ch/record/1282371/files/ATL-DAQ-PROC-2010-026.pdf$$zStamped by WebSubmit: 01/08/2010
001282371 916__ $$sn$$w201070
001282371 961__ $$c20101213$$h1433$$lCER01$$x20100801
001282371 963__ $$aPUBLIC
001282371 960__ $$a13
001282371 962__ $$b1980824$$k211-214$$nsienna20100607
001282371 970__ $$a000709075CER
001282371 980__ $$aINTNOTEATLASPUBL
001282371 980__ $$aConferencePaper
001282371 980__ $$aARTICLE