MétaCan
Menu
Back to cohort

Experiences and lessons learned from the End-of-Substructure card production of the ATLAS ITk Strip upgrade

2025· article· en· W4407389288 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

VenueJournal of Instrumentation · 2025
Typearticle
Languageen
FieldPhysics and Astronomy
TopicParticle Detector Development and Performance
Canadian institutionsInstitute of Particle Physics
FundersCERN
KeywordsUpgradeFront and back endsDetectorComputer scienceAtlas (anatomy)Large Hadron ColliderComputer hardwareSubstructureTroubleshootingConvertersElectrical engineeringPhysicsOperating systemTelecommunicationsParticle physicsEngineering

Abstract

fetched live from OpenAlex

Abstract The silicon tracker of the ATLAS experiment will be upgraded for the upcoming High-Luminosity Upgrade of the LHC. The main building blocks of the new strip tracker are modules that consist of silicon sensors and hybrid PCBs hosting the read-out ASICs. The modules are mounted on rigid carbon-fiber substructures, known as staves in the central barrel region and petals in the end-cap regions, that provide common services to all the modules. At the end of each stave or petal side, a so-called End-of-Substructure (EoS) card facilitates the transfer of data, power, and control signals between the modules and the off-detector systems. The EoS connects up to 28 data lines to one or two lpGBT chips that provide data serialization and uses a 10 Gbit s -1 versatile optical link to transmit signals to the off-detector systems. To meet the tight integration requirements in the detector, several different EoS card designs are needed. The power to the EoS is provided by a dedicated dual-stage DC-DC package providing 2.5 V and 1.2 V to the EoS cards. As the EoS production of almost 2000 EoS cards and accompanying DC-DC converters is getting close to completion, the production experience including detailed QC statistics and design validation (QA) results is reported on.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.477
Threshold uncertainty score0.110

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.000
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.0000.000

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.024
GPT teacher head0.286
Teacher spread0.262 · 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