Pith. sign in

REVIEW 3 major objections 6 minor 5 references

Synchronous and asynchronous Data Quality Control of the ALICE Inner Tracking System in the LHC Run 3

T0 review · 3 major / 6 minor · reviewed 2026-08-07 · deepseek-v4-flash

Pith's one-line read A two-stage data-quality system monitors the ITS2 pixel tracker both live and offline.

desk verdict A useful status report on ALICE ITS2 QC with a real operational story but thin quantitative evidence; referee it for the detector-operations community. read the letter →

arxiv 2506.03212 v1 pith:4DFIE4ZH submitted 2025-06-03 physics.ins-det hep-ex

classification physics.ins-dethep-ex
keywords ALPIDEmonolithicactivepixelsensordataqualitycontrolsynchronousreconstructionasynchronousInnerTrackingSystemdetectorheavy-ioncollisions
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

This paper reports that the data-quality control system for the upgraded Inner Tracking System (ITS2) of the ALICE experiment does what it was built to do: it monitors detector state synchronously on a 1-percent sample of the data stream and asynchronously on the full reconstructed dataset, and on the strength of those two passes the detector has been operated through Run 3 pp and Pb–Pb campaigns with very low noise and a stable pixel charge threshold. A sympathetic reader should care because real-time quality flags decide during data-taking whether a run is usable for physics, while the asynchronous pass produces the final detector maps and calibrations that physics analyses rely on. The paper's evidence includes chip-status plots showing readout-lane failures and their automatic recovery, dead-chip fractions of about 1% in the outer barrel and none in the inner barrel, and cluster-occupancy and track-acceptance maps that look uniform across the detector.

What carries the argument

The central object is the two-stage Data Quality Control architecture of ITS2, built on the ALPIDE monolithic active pixel sensor, a CMOS pixel sensor with 27 µm × 29 µm pixels. The synchronous stage runs dedicated QC checks at the FLP and EPN levels over a 1% sample during online reconstruction, covering data integrity, occupancy, cluster size and topology, track multiplicity, noisy-pixel extraction, thresholds, and chip or lane availability, while the asynchronous stage reconstructs the full dataset with improved calibration and produces trend plots and final detector maps. The mechanism also includes an auto-recovery system that detects problematic readout lanes and restores them at the stave level within 10 to 30 seconds, with permanently dead chips at 1% in the outer barrel and none in the inner barrel.

What would settle it

Take any run tagged GOOD by the synchronous QC and compare the cluster-occupancy map built from the 1% online sample with the map built from asynchronous full-data reconstruction; a stave or lane showing sustained low occupancy or a dead-chip signature in the full-data map but not in the 1% sample map would show that the online sample misses localised damage.

Watch

Extended reading notes

Core claim

The central claim is that the ITS2 QC system achieves reliable monitoring through a two-stage architecture rather than a single pass. During synchronous reconstruction, 13 First Level Processors run raw-data checks per detector segment and 340 Event Processing Nodes run checks that need full-detector information; only 1% of the data is examined in this online phase. In the asynchronous phase, the full dataset is reconstructed with improved calibrations, yielding detector maps and physics-quality quantities. The paper concludes from these results that ITS2 has been successfully operated in pp and Pb–Pb collisions with very low noise and stable pixel charge thresholds, and that uniform cluster and track distributions confirm good acceptance across azimuthal angle and pseudorapidity.

Load-bearing premise

The system assumes that a 1% random sample of the data is representative enough to reveal every localised detector fault, so a damaged region hidden in the other 99% could still let a run be tagged GOOD.

Editorial extensions

If this is right

  • Runs tagged GOOD by the synchronous phase can be trusted as the basis for physics selections, since the asynchronous full-data analysis confirms the same detector state.
  • The auto-recovery mechanism keeps permanently dead chips at about 1% in the outer barrel and at zero in the inner barrel, so the detector sensitive area stays essentially intact through a run.
  • Time-dependent acceptance maps extracted during synchronous QC feed Monte Carlo simulations, linking the actual detector state to simulated event response.
  • Uniform cluster occupancy and track acceptance across azimuthal angle and pseudorapidity support the low-pT heavy-flavor physics program by showing no large acceptance holes in the reconstructed track sample.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • Beyond the paper: because the synchronous pass examines only 1% of the data, the online GOOD tag may miss localised detector faults; comparing occupancy maps between the two passes run-by-run would quantify how often this happens.
  • Beyond the paper: the trend plots produced in the asynchronous post-processing could be mined over months of Run 3 data to detect slow sensor degradation, such as a drift in charge threshold or a gradual rise in fake-hit rate, before it shows up as a physics-quality problem.
  • Beyond the paper: the inter-fill charge-threshold scans already used for calibration could be closed into an automated feedback loop with the threshold-tuning and noisy-pixel-masking tasks, reducing operator intervention during long fills.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 6 minor

Summary. This paper reports on the synchronous and asynchronous Data Quality Control (QC) system of the ALICE ITS2 detector during LHC Run 3. It describes the FLP/EPN processing architecture, lists seven synchronous QC tasks covering data integrity, occupancy, cluster and track properties, noisy-pixel extraction, threshold/dead-pixel checks, and chip/link availability, and presents example online QC plots from Pb-Pb data taking as well as comparisons of synchronous versus asynchronous reconstruction for cluster occupancy and track distributions. The paper concludes that the QC software is operational and that the detector has been run in pp and Pb-Pb collisions with very low noise and a stable pixel charge threshold.

Significance. If the operational claims are accepted, this is a useful reference for the community running large MAPS-based tracking detectors, documenting the architecture and practical experience of the largest such system in high-energy physics. The paper's strength is that it is a report grounded in real LHC Run 3 data and in the actual operating experience of the ALICE detector. The main limitation is that all supporting evidence is qualitative: the plots have no error bars, no quantitative acceptance criteria are given, and there is no comparison against baselines or pre-established thresholds. The paper therefore supports the statement that a QC framework exists and is used, but it only weakly supports the stronger claim that the detector operated stably and efficiently, because 'stable' and 'low noise' are never quantified.

major comments (3)
  1. [Section 3, paragraph 2 and Section 2, item 1] The paper states that in the synchronous phase the QC processes only 1% of data, yet Section 2 lists as the first synchronous task a 'data integrity check of all events'. These two statements are in tension unless the 1% subset applies only to a subset of the seven tasks. The manuscript does not clarify whether the 1% sample applies to all EPN-based tasks, to which tasks it does not apply, how the 1% sample is selected (temporal period, random selection, per FLP, per run segment), and whether the FLP-level raw-data integrity checks run on 100% of the data. This matters because the central advertised function of the synchronous QC is real-time fault detection; if the 1% sample is not representative over time and detector element, a damaged region could be missed and a run could be tagged GOOD while the full data later reveals a problem. Please specify the sampling strategy and the coverage of each of the seven tasks.
  2. [Section 3, Figure 1 and Section 4, Conclusion] The conclusion that the detector has a 'very low noise level and stable pixel charge threshold' is not supported by any quantitative criterion or measurement. Figure 1 is presented as a quality-assessment plot for a run tagged GOOD, but no numerical threshold for FHR, dead-chip fraction, or threshold dispersion is given, nor is the plot compared to a baseline or to other runs. To make the claim load-bearing, please provide the actual measured values or reference the ALICE specifications that define what 'low' and 'stable' mean, and state whether the plotted run satisfies those criteria.
  3. [Section 3, Figures 2 and 3] The comparison of synchronous and asynchronous reconstruction is meant to illustrate ITS2 performance, but the paper only gives qualitative visual observations. The textual comments state that observed differences are due to different algorithms and selection criteria, but no quantitative assessment is provided; for example, no ratio of cluster occupancies, no track-yield comparison, and no statistical uncertainties are shown. Without such numbers, the reader cannot judge whether the differences are within expectation or whether they indicate an operational problem. Please add at least one quantitative metric per figure, such as a mean ratio with uncertainty or a comparison with a Monte Carlo expectation.
minor comments (6)
  1. [Section 3, paragraph 2] There is a typographical error: 'the QC processes only only 1% of data' should read 'the QC processes only 1% of data'.
  2. [Abstract and Introduction] The word 'challeging' in the abstract and in the Introduction should be 'challenging'.
  3. [Section 3, paragraph 1] The description of Figure 1 is unclear about the distinction between fake-hit rate and occupancy; the text first says FHR is measured in the absence of beams, then says the same plot gives hit occupancy during collisions, but it is not stated which quantity is actually shown in the top panel of Figure 1. Please clarify the label of the vertical axis and the definition of the plotted quantity.
  4. [Section 3, paragraph 1] Several sentences have grammar or syntax issues, for example 'The thicker lines corresponding to the full stave not sending data' lacks a verb, and 'which longs (from 10 to 30 seconds)' should be 'which lasts (from 10 to 30 seconds)'.
  5. [References] Reference [4] is cited for the ALICE QC framework, but the title suggests it is an operation and performance paper rather than a framework paper; consider adding a direct reference to the ALICE QC framework software or its documentation.
  6. [Figures 2 and 3] The captions of Figures 2 and 3 do not define all axis labels or color scales; although the text describes them, a reader looking only at the figures cannot determine what is plotted. Please include complete axis and color-scale information in the captions.

Circularity Check

0 steps flagged · score 0.0 of 10

No circularity: the paper is a descriptive detector-operations report with no fitted parameters, predictions, or derivation chain that could reduce to its inputs.

full rationale

This paper describes the ALICE ITS2 Data Quality Control framework and presents monitoring plots from Run 3 pp and Pb–Pb operation. It makes no quantitative predictive claim: the QC plots are direct displays of measured detector occupancy, chip status, cluster occupancy, and track distributions, not quantities derived from fitted inputs. The synchronous/asynchronous comparison (Figures 2 and 3) is explicitly presented as a comparison of two reconstruction modes with different algorithms and selection criteria, and the statement that 'the QC processes only 1% of data' is an honest scope note, not a hidden fit. References to ALICE TDRs and collaboration papers are standard institutional citations for the detector design and computing system; none is used to justify a circular derivation, and the performance statements (low noise, stable threshold) are asserted from operational monitoring, not derived from a self-cited uniqueness theorem. There is no equation, no fitted parameter renamed as a prediction, and no ansatz smuggled in via citation. The paper is self-contained as an operational report, so the circularity score is 0.

Assumptions & free parameters 0 free parameters · 1 assumptions · 0 invented entities

The paper introduces no fitted parameters or new entities; the only implicit input is trust in the cited detector specifications and the ALICE QC framework.

assumptions (1)
  • domain assumption The detector parameters and performance figures quoted from references (pixel pitch, material budget, position resolution) are accurate.
    The paper relies on these values from the TDR and ALPIDE publications without re-deriving them.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Synchronous and asynchronous Data Quality Control of the ALICE Inner Tracking System in the LHC Run 3." pith.science (2026). https://pith.science/paper/4DFIE4ZH

@misc{pith2026250603212,
  author       = {Pith},
  title        = {Pith review of: Synchronous and asynchronous Data Quality Control of the ALICE Inner Tracking System in the LHC Run 3},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/4DFIE4ZH}},
  note         = {Machine review of arXiv:2506.03212}
}
abstract

The Inner Tracking System (ITS) of the ALICE experiment at the CERN Large Hadron Collider (LHC) is the largest Monolithic Active Pixel Sensor technology application in high-energy physics. The upgraded version of the tracking system, called ITS2, consists of seven concentric layers of ALPIDE monolithic active pixel sensors produced in the 180 nm CMOS process, covering a total sensitive area of about 10 m${}^2$. The ALPIDE sensor features a pixel pitch of 27 $\mu$m $\times$ 29 $\mu$m and a position resolution of about 5 $\mu$m. The very low material budget, 0.36\% $X_{0}$/layer for the three innermost layers and 1.10\% $X_{0}$/layer for the outer layers, in combination with the small radial distance of only 23 mm from the beam, leads to an excellent impact parameter resolution at low transverse momentum. This makes the detector well suited for experimentally challeging physics measurements such as the reconstruction of low transverse momentum heavy-flavor particles in the heavy-ion collision environment. This contribution provides an overview of the ITS2 data Quality Control system (QC), a framework designed to synchronously monitor the detector operating parameters and provide asynchronous reconstruction of the collected data, with the goal of guaranteeing a stable and efficient data taking. The monitoring for fake-hit rate, front-end electronics status, data integrity, cluster and track distributions, are presented, together with an overview of the ITS2 performance during the recent Run 3 pp and Pb--Pb data taking campaigns, as extracted from the QC asynchronous reconstruction.

Discussion (0). Sign in to comment.

Reference graph

Works this paper leans on

5 extracted references · 5 canonical work pages

  1. [1]

    ALICE Collaboration, Technical Design Report for the Upgrade of the ALICE Inner Tracking System, J. Phys. G: Nucl. Part. Phys. 41 (2014) 087002

  2. [2]

    ALICECollaboration, ALICE upgradesduring theLHC LongShutdown 2, JINST19 (2024)P05062

  3. [3]

    Aglieri Rinella et al

    G. Aglieri Rinella et al. (ALICE Collaboration), The ALPIDE pixel sensor chip for the upgrade of the ALICE Inner Tracking System, NIM A 845 (2017) 583–587

  4. [4]

    Andrea Sofia Triolo on behalf of the ALICE Collaboration, Operation and Performance of the Upgraded ALICE Inner Tracking System, PoS (VERTEX2023) 006

  5. [5]

    Buncic, M.Krzewicki, P

    P. Buncic, M.Krzewicki, P. Vande Vyvre, Technical Design Report for the Upgrade of the Online-Offline Computing System, CERN-LHCC-2015-006, ALICE-TDR-019. – 4 –

Pith tools

Reviewed August 7, 2026 · model on record in the stance chip above.