MétaCan
Menu
Back to cohort
Record W2162943282 · doi:10.1109/tns.2002.1003741

High-level triggers in ATLAS

2002· article· en· W2162943282 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Transactions on Nuclear Science · 2002
Typearticle
Languageen
FieldPhysics and Astronomy
TopicParticle Detector Development and Performance
Canadian institutionsTRIUMFUniversity of Alberta
Fundersnot available
KeywordsAtlas (anatomy)Event (particle physics)SoftwareGranularityLarge Hadron ColliderComputer scienceData acquisitionFlexibility (engineering)Selection (genetic algorithm)Real-time computingParticle physicsPhysicsOperating systemArtificial intelligence

Abstract

fetched live from OpenAlex

The trigger and data-acquisition system of ATLAS, a general-purpose experiment at the Large Hadron Collider (LHC), will be based on three levels of online selection. Starting from the bunch-crossing rate of 40 MHz (an interaction rate of 1 GHz at design luminosity-/spl sim/ 10/sup 34/ cm/sup -2/s/sup -1/), the first level trigger (LVL1) will reduce the rate to about 75 kHz using purpose-built hardware. An additional factor of about 10/sup 3/ in rate reduction is to be provided by the high-level triggers (HLTs) system, with two main functional components: the second-level trigger (LVL2) and the event filter(EF). LVL2 has to provide a fast decision (guided by the information from LVL1), using only a fraction of the full event, however, already at full granularity and can combine all subdetectors. At the EF, a refined selection is made with the. capability of full event reconstruction and the use of detailed calibration and alignment parameters. The HLT software architecture will provide a common and rather "lightweight" framework, able to execute the various selection algorithms and to control the sequence of execution according to the event properties and configuration parameters. System flexibility is a strong requirement in order to adapt to changes, e.g., in luminosity and background conditions. This paper will present the approach chosen for the software design of the HLT selection framework and of the algorithm interface, giving examples for selection sequences and algorithms. Based on currently existing prototypes, results for both the expected physics (signal efficiency, background rejection) and system (execution time) performance will also be shown.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.797
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.028
GPT teacher head0.231
Teacher spread0.203 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it