A Comparative Analysis of the CERN ATLAS ITk MOPS Readout: A Feasibility Study on Production and Development Setups

Felix Sebastian Nitz; Lukas Flad; Tobias Krawutschke

A Comparative Analysis of the CERN ATLAS ITk MOPS Readout: A Feasibility Study on Production and Development Setups

T0 review · 1 major / 0 minor · reviewed 2026-05-16 · grok-4.3

Challenge this review Download PDF Read on arXiv ↗ Review JSON

Pith's one-line read A testbed and verification methodology qualifies the MOPS-Hub for production in the ATLAS ITk Detector Control System.

desk verdict This paper lays out a detailed test methodology for the MOPS readout in the ATLAS ITk upgrade but contains no data, results, or validation of its own. read the letter →

arxiv 2602.08488 v1 submitted 2026-02-09 physics.ins-det cs.SYeess.SY

Lukas Flad , Felix Sebastian Nitz , Tobias Krawutschke This is my paper · ORCID

classification physics.ins-detcs.SYeess.SY

keywords MOPSATLASITkDetectorControlSystemtestbedverificationmethodologylatencymeasurementCANinterfaceFPGA

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

The paper describes a dedicated testbed and set of test cases to evaluate the MOPS readout system for the upcoming ATLAS Inner Tracker upgrade. It compares a Raspberry Pi-based mock-up controller with the final FPGA-based MOPS-Hub through measurements of latency, jitter, and data integrity on CAN and UART interfaces. The approach includes specific load profiles for different operational scenarios and acceptance criteria to ensure the system performs reliably under the demands of the High-Luminosity LHC. This provides a repeatable way to verify the architecture before it is deployed in production.

What carries the argument

The MOPS readout verification testbed with unified time-stamping scheme and non-intrusive signal taps to measure latency, jitter, and data integrity under defined load profiles.

What would settle it

A performance failure or safety issue in the MOPS-Hub during actual ATLAS ITk operation that passes all test cases, load profiles, and acceptance criteria would show the methodology is insufficient.

Watch

Extended reading notes

Core claim

The paper introduces a testbed and verification methodology for the MOPS readout, defining test cases for two DCS-readout architectures: a preliminary Raspberry Pi-based MOPS-Hub Mock-up and the final production FPGA-based MOPS-Hub. The methodology specifies the measurement chain for end-to-end latency, jitter, and data integrity across CAN and UART interfaces, including a unified time-stamping scheme, non-intrusive signal taps, and a consistent data-logging and analysis pipeline. It details load profiles and scalability scenarios together with acceptance criteria to qualify the MH architecture for production and deployment in the ATLAS ITk DCS.

Load-bearing premise

The defined test cases, load profiles, and acceptance criteria will be sufficient to catch all relevant failure modes before production deployment.

Editorial extensions

If this is right

The procedure enables direct comparison of latency, jitter, and data integrity between the Raspberry Pi mock-up and FPGA production setups.
Reproducible measurements are ensured by the consistent chain of non-intrusive taps, unified time-stamping, and data-logging pipeline.
Scalability is addressed through explicit scenarios covering baseline operation, full-crate stress, and CAN interface channel isolation.
Acceptance criteria and measurement uncertainty considerations allow pass/fail decisions for production qualification.

Reading between the lines

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

This structured testbed approach could be adapted to qualify readout systems for other detector upgrades in high-energy physics.
Early identification of issues through these tests could reduce integration risks during the full ITk installation phase.
The methodology's emphasis on reproducibility supports potential automation of analysis for larger-scale production testing.

Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

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

Desk Editor's Note

read the letter

The core point is that this work describes a testbed and procedure for qualifying both a Raspberry Pi mock-up and the final FPGA-based MOPS-Hub, including unified timestamping, non-intrusive taps on CAN and UART, and specific load profiles for baseline, full-crate stress, and channel isolation. It sets acceptance criteria and notes on measurement uncertainty to support reproducibility. That structured outline is the main contribution here, and it is useful for anyone who needs to build a repeatable qualification process for similar detector control hardware in a large experiment. The authors clearly thought through the end-to-end measurement chain and scalability scenarios, which shows practical engineering attention to the production setup versus the development one. Credit for spelling out those details without overclaiming what the tests will prove. The obvious limitation is the complete absence of any executed tests or measured outcomes. The paper states outright that results and comparative analysis go into a companion paper, so the claim of providing a qualifying procedure rests only on the description of the cases and criteria. Without data, there is no way to check whether those cases actually surface the relevant failure modes or whether the acceptance thresholds are tight enough. This is a methods outline, not a completed validation. The work is aimed at the ATLAS ITk DCS group and engineers handling similar monitoring systems for pixel detectors. A reader already embedded in that project would find the test definitions and pipeline practical to adapt. Outside that narrow context it offers little new technique. I would send it to peer review because the methodology is concrete and tied to an active upgrade, even though it will need the companion results to carry real weight.

Referee Report

1 major / 0 minor

Summary. The manuscript outlines a testbed and verification methodology for the MOPS readout in the ATLAS ITk DCS. It defines test cases for the MOPS-Hub Mock-up and the production MOPS-Hub, including measurement chains for end-to-end latency, jitter, and data integrity across CAN and UART interfaces with unified timestamping, as well as load profiles such as baseline operation, full-crate stress, and channel isolation, along with acceptance criteria. The objective is to establish a repeatable qualification procedure, with results deferred to a companion paper.

Significance. If the proposed test suite is shown to be comprehensive, this work would provide a valuable, reproducible framework for qualifying critical components of the detector control system ahead of the High-Luminosity LHC upgrade, potentially improving the reliability of monitoring pixel system voltages and temperatures.

major comments (1)

[Abstract] Abstract: The central claim that the defined test cases, load profiles, and acceptance criteria constitute a sufficient qualification procedure for the MH architecture is not substantiated, as the manuscript presents no experimental data, execution of the tests, or validation that the criteria catch relevant failure modes; results are explicitly deferred to a companion paper, leaving the adequacy of test coverage unverified.

Simulated Author's Rebuttal

1 responses · 0 unresolved

We thank the referee for the constructive review of our manuscript. We address the single major comment below, clarifying the intended scope of this work as a methodology definition paper.

read point-by-point responses

Referee: [Abstract] Abstract: The central claim that the defined test cases, load profiles, and acceptance criteria constitute a sufficient qualification procedure for the MH architecture is not substantiated, as the manuscript presents no experimental data, execution of the tests, or validation that the criteria catch relevant failure modes; results are explicitly deferred to a companion paper, leaving the adequacy of test coverage unverified.

Authors: This manuscript is deliberately scoped to define a repeatable testbed, verification methodology, test cases, load profiles, measurement chains, and acceptance criteria for qualifying the MOPS readout architectures. As stated in the abstract, the experimental execution, results, and validation of whether the criteria catch relevant failure modes are reserved for a companion paper. The central claim here is that the defined procedure provides a clear, reproducible framework, not that its sufficiency has been demonstrated by data in this document. We maintain that separating the methodology definition from its application is appropriate and do not plan to add experimental results or alter the manuscript structure. revision: no

Circularity Check

0 steps flagged · score 0.0 of 10

Descriptive methods paper with no derivations, fits, or self-referential predictions

full rationale

The manuscript is a methods outline that defines a testbed, measurement chain (latency/jitter/integrity via CAN/UART with unified timestamping), load profiles (baseline, full-crate stress, channel isolation), and acceptance criteria for qualifying the MH architecture. It contains no equations, fitted parameters, predictions, or derivation steps that reduce to prior quantities by construction. No self-citations are invoked to justify uniqueness, ansatzes, or load-bearing premises. The central claim is simply that the described procedure is repeatable; this is presented as a methodological contribution without any circular reduction. The deferral of results to a companion paper does not create circularity in the present text.

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

This is an engineering methods paper; no free parameters, mathematical axioms, or invented physical entities are introduced.

how reviews work

0 comments

Cite this review

Pith. "Pith review of A Comparative Analysis of the CERN ATLAS ITk MOPS Readout: A Feasibility Study on Production and Development Setups." pith.science (2026). https://pith.science/paper/2602.08488

@misc{pith2026260208488,
  author       = {Pith},
  title        = {Pith review of: A Comparative Analysis of the CERN ATLAS ITk MOPS Readout: A Feasibility Study on Production and Development Setups},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/2602.08488}},
  note         = {Machine review of arXiv:2602.08488}
}

read the original abstract

The upcoming High-Luminosity upgrade of the Large Hadron Collider (LHC) necessitates a complete replacement of the ATLAS Inner Detector with the new Inner Tracker (ITk). This upgrade imposes stringent requirements on the associated Detector Control System (DCS), which is responsible for the monitoring, control, and safety of the detector. A critical component of the ITk DCS is the Monitoring of Pixel System (MOPS), which supervises the local voltages and temperatures of the new pixel detector modules. This paper introduces a dedicated testbed and verification methodology for the MOPS readout, defining a structured set of test cases for two DCS-readout architectures: a preliminary Raspberry Pi-based controller, the "MOPS-Hub Mock-up"(MH Mock-up), and the final production FPGA-based "MOPS-Hub" (MH). The methodology specifies the measurement chain for end-to-end latency, jitter, and data integrity across CAN and UART interfaces, including a unified time-stamping scheme, non-intrusive signal taps, and a consistent data-logging and analysis pipeline. This work details the load profiles and scalability scenarios (baseline operation, full-crate stress, and CAN Interface Card channel isolation), together with acceptance criteria and considerations for measurement uncertainty to ensure reproducibility. The objective is to provide a clear, repeatable procedure to qualify the MH architecture for production and deployment in the ATLAS ITk DCS. A companion paper will present the experimental results and the comparative analysis obtained using this testbed.

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

50 extracted references · 50 canonical work pages

[1]

et al.,The ATLAS experiment at the CERN Large Hadron Collider,J

G.A. et al.,The ATLAS experiment at the CERN Large Hadron Collider,J. Instrum.3(2008) S08003

work page 2008
[2]

et al.,High-Luminosity Large Hadron Collider (HL-LHC): Technical design report, Tech

O.A. et al.,High-Luminosity Large Hadron Collider (HL-LHC): Technical design report, Tech. Rep. CERN, Geneva (2020), DOI

work page 2020
[3]

CERN. Geneva. The LHC experiments Committee,Technical design report for the ATLAS Inner Tracker Pixel detector, 2017. 10.17181/CERN.FOZZ.ZP3Q

work page doi:10.17181/cern.fozz.zp3q 2017
[4]

CERN. Geneva. The LHC experiments Committee,Technical design report for the ATLAS Inner Tracker Strip detector, 2017

work page 2017
[5]

Thompson,ATLAS ITk Pixel detector overview, 2025

E.A. Thompson,ATLAS ITk Pixel detector overview, 2025

work page 2025
[6]

Möbius,Pixel detector studies for the ATLAS ITk upgrade for the HL-LHC, Ph.D

S. Möbius,Pixel detector studies for the ATLAS ITk upgrade for the HL-LHC, Ph.D. thesis, Georg-August-University Göttingen, 2023. 10.53846/goediss-9911

work page doi:10.53846/goediss-9911 2023
[7]

Chubinidze,ITk Pixel System Test of the ATLAS Experiment,J

Z. Chubinidze,ITk Pixel System Test of the ATLAS Experiment,J. Instrum.20(2025) C02038

work page 2025
[8]

et al.,The detector control system of the ATLAS experiment,J

A.B.P. et al.,The detector control system of the ATLAS experiment,J. Instrum.3(2008) P05006

work page 2008

Show all 50 references

[9]

Ahmad,The Monitoring of Pixel System (MOPS) chip for the Detector Control System of the ATLAS ITk Pixel detector,J

R. Ahmad,The Monitoring of Pixel System (MOPS) chip for the Detector Control System of the ATLAS ITk Pixel detector,J. Phys. Conf. Ser.2374(2022) 012094

2022
[10]

Ahmad, A

R. Ahmad, A. Adam, J. Besproswanny, M. Karagounis, P. Kind, S. Kersten et al.,Second generation Monitoring of Pixel System (MOPS) chip for the Detector Control System (DCS) of the ATLAS ITk Pixel detector,J. Instrum.18(2023) C04015

2023
[11]

Description and manual to use the MOPS chip

R. Ahmad, “Description and manual to use the MOPS chip.” – 14 –
[12]

MOPS-Hub for beginners documentation MOPSv2

M.I. Lezki, S. Kuehn, S.G. Sevilla and L. Flad, “MOPS-Hub for beginners documentation MOPSv2.”
[13]

Qamesh, R

A. Qamesh, R. Ahmad, M. Karagounis, P. Kind, T. Krawutschke, F. Nitz et al.,An FPGA-based Data Aggregator for the New ATLAS ITK Pixel DCS, Nov., 2024. 10.48550/arXiv.2410.24057

2024 doi
[14]

Qamesh, R

A. Qamesh, R. Ahmad, D. Ecker, T. Fischer, M. Karagounis, P. Kind et al.,System integration of ATLAS ITK Pixel DCS ASICs,J. Instrum.18(2023) C05003

2023
[15]

Swoboda,The detector control system for ALICE, Technical Report CERN-1999-009.371, CERN, Geneva (1999)

D. Swoboda,The detector control system for ALICE, Technical Report CERN-1999-009.371, CERN, Geneva (1999)

1999
[16]

Chochula, A

P. Chochula, A. Augustinus, P. Bond, A. Kurepin, M. Lechman, J. LÃ¥Ng et al.,Challenges of the ALICE Detector Control System for the LHC RUN3,Proceedings of the 16th Int. Conf. on Accelerator and Large Experimental Control SystemsICALEPCS2017(2018) 5 pages, 1.172 MB

2018
[17]

et al.,The LHCb data acquisition during LHC Run 1,J

F.A. et al.,The LHCb data acquisition during LHC Run 1,J. Phys. Conf. Ser.513(2014) 012033

2014
[18]

Barillère and S

R. Barillère and S. Haider,LHC gas control systems, Tech. Rep. CERN, Geneva (2007)

2007
[19]

C. Adam, D. Barberis, S. Crépé-Renaudin, K. De, F. Fassi, A. Stradling et al.,Computing shifts to monitor ATLAS distributed computing infrastructure and operations,J. Phys. Conf. Ser.898(2017) 092004

2017
[20]

et al.,The CMS Experiment at the CERN LHC,J

S.C. et al.,The CMS Experiment at the CERN LHC,J. Instrum.3(2008) S08004

2008
[21]

Holme, M

O. Holme, M. González-Berges, P. Golonka and S. Schmeling,The JCOP framework, Tech. Rep. CERN, Geneva (2005)

2005
[22]

Ecker, P

D. Ecker, P. Dubru, S. Foged, N. Kanellos, P. Moschovakos, V. Ryjov et al.,EMCI-EMP: Developments and Experience with the Novel Detector Control Solution,J. Instrum.20(2025) C01020

2025
[23]

The ATLAS Collaboration,Commissioning of the atlas muon spectrometer with cosmic rays,Eur. Phys. J. C70(2010) 875

2010
[24]

The ATLAS Collaboration,Readiness of the atlas tile calorimeter for lhc collisions,Eur. Phys. J. C70 (2010) 1193

2010
[25]

Aprile, G

A. Aprile, G. Avolio, A. Campagna, M. Capua, D. Cuce’, E. Ferraro et al.,Production and test of monitored drift tubes for the muon spectrometer of the atlas experiment,IEEE Transactions on Nuclear Science49(2002) 1077

2002
[26]

et al.,Radiation-tolerant, SRAM-FPGA based trigger and readout electronics for the ALICE experiment,IEEE Trans

J.A. et al.,Radiation-tolerant, SRAM-FPGA based trigger and readout electronics for the ALICE experiment,IEEE Trans. Nucl. Sci.55(2008) 76

2008
[27]

Dhara, A

P. Dhara, A. Roy, P. Maity, P. Singhai and P.S. Roy,Design of the data acquisition system for the nuclear physics experiments at VECC, inProc. 9th Int. Workshop Personal Comput. Particle Accelerator Controls (PCaPAC’12), (Kolkata, India), pp. 269–271, Dec, 2012

2012
[28]

et al.,The ATLAS Level-1 calorimeter trigger,J

R.A. et al.,The ATLAS Level-1 calorimeter trigger,J. Instrum.3(2008) P03001

2008
[29]

et al.,Phase-II upgrade of the ATLAS L1 central trigger, Tech

A.K. et al.,Phase-II upgrade of the ATLAS L1 central trigger, Tech. Rep. CERN, Geneva (2024)

2024
[30]

Butkowski, T

Ł. Butkowski, T. Kozak, P. Prędki, R. Rybaniec and B. Yang,FPGA firmware framework for MTCA.4 AMC modules, inProc. 15th Int. Conf. on Accelerator and Large Experimental Physics Control Systems (ICALEPCS2015), p. WEPGF074, 2015, DOI

2015
[31]

et al.,A demonstration of a time multiplexed trigger for the CMS experiment,J

R.F. et al.,A demonstration of a time multiplexed trigger for the CMS experiment,J. Instrum.7(2012) C01060

2012
[32]

et al.,The GBT project, inTopical Workshop on Electronics for Particle Physics, CERN, 2009, DOI

P.M. et al.,The GBT project, inTopical Workshop on Electronics for Particle Physics, CERN, 2009, DOI. – 15 –

2009
[33]

et al.,The Versatile Link common project: Feasibility report,J

F.V. et al.,The Versatile Link common project: Feasibility report,J. Instrum.7(2012) C01075

2012
[34]

ISO 11898-1:2015, Road vehicles – Controller area network (CAN) – Part 1: Data link layer and physical signalling

“ISO 11898-1:2015, Road vehicles – Controller area network (CAN) – Part 1: Data link layer and physical signalling.” ISO, 2015

2015
[35]

Nikiel,CANopen & ELMB software for LHC experiment controls as seen in 2022, Tech

P. Nikiel,CANopen & ELMB software for LHC experiment controls as seen in 2022, Tech. Rep. CERN, Geneva (2022)

2022
[36]

Mathe, H.K

S.E. Mathe, H.K. Kondaveeti, S. Vappangi, S.D. Vanambathina and N.K. Kumaravelu,A comprehensive review on applications of Raspberry Pi,Comput. Sci. Rev.52(2024) 100636

2024
[37]

Carvalho, C.L.D

A.A. Carvalho, C.L.D. Machado and F.S. Moraes,Raspberry Pi performance analysis in real-time applications with the RT-Preempt patch, in2019 Latin American Robotics Symposium (LARS), 2019 Brazilian Symposium on Robotics (SBR) and 2019 Workshop on Robotics in Education (WRE), pp...

2019
[38]

ATLAS ITk Grounding - v2.3

H. Grabas, “ATLAS ITk Grounding - v2.3.” Scribd
[39]

Bonacini, K

S. Bonacini, K. Kloukinas and P. Moreira,e-link: A radiation-hard low-power electrical link for chip-to-chip communication, inTopical Workshop on Electronics for Particle Physics, 2009, DOI

2009
[40]

Implementation of the communication and data visualization for the ITk Pixel monitoring chip of the ATLAS experiment at CERN

D. Ecker, “Implementation of the communication and data visualization for the ITk Pixel monitoring chip of the ATLAS experiment at CERN.” Presentation at CERN, 2022

2022
[41]

J. Du, D. Kade, C. Gerdtman, O. Özcan and M. Lindén,The effects of perceived USB-delay for sensor and embedded system development, inProc. 38th Annu. Int. Conf. IEEE Eng. Med. Biol. Soc. (EMBC), pp. 2492–2495, 2016, DOI

2016
[42]

STM32F767ZIT6 - STM32 Dynamic Efficiency MCU, Arm Cortex-M7 core with DSP and FPU

STMicroelectronics, “STM32F767ZIT6 - STM32 Dynamic Efficiency MCU, Arm Cortex-M7 core with DSP and FPU.” STMicroelectronics
[43]

Naik and P

K. Naik and P. Tripathy,Software Testing and Quality Assurance: Theory and Practice, Wiley-Interscience (2008)

2008
[44]

CERN,ATLAS sub-detector Phase-II Upgrade: MOPS-Hub FPGA Firmware specification, Tech. Rep. CERN, Geneva (2024)

2024
[45]

R. Khan, A. Qahmash and M.R. Hussain,Soak Testing of Web Applications Based on Automatic Test Cases,International Journal of Engineering Research and Technology13(2020) 4746

2020
[46]

QA/QC of MOPS-HUB | Document AT2-IP-QA-0053 (v.1)

A. Qamesh, “QA/QC of MOPS-HUB | Document AT2-IP-QA-0053 (v.1).” https://edms.cern.ch
[47]

Walsemann, S

A. Walsemann, S. Kersten, P. Kind, N. Lehmann, S. Scholz, C. Zeitnitz et al.,A CANopen based prototype chip for the Detector Control System of the ATLAS ITk Pixel detector,PoSTWEPP2019 (2020) 013

2020
[48]

Voss,A Comprehensible Guide to Controller Area Network, Copperhill Media Corporation (2008)

W. Voss,A Comprehensible Guide to Controller Area Network, Copperhill Media Corporation (2008)

2008
[49]

Davis and A

R.I. Davis and A. Burns,A survey of hard real-time scheduling for multiprocessor systems,ACM Comput. Surv.43(2011) 35:1

2011
[50]

Dworak, F

A. Dworak, F. Ehm, P. Charrue and W. Sliwinski,The new CERN controls middleware,J. Phys. Conf. Ser.396(2012) 012017. – 16 –

2012

Pith tools

Reviewed May 16, 2026 · model on record in the stance chip above.

[1] [1]

et al.,The ATLAS experiment at the CERN Large Hadron Collider,J

G.A. et al.,The ATLAS experiment at the CERN Large Hadron Collider,J. Instrum.3(2008) S08003

work page 2008

[2] [2]

et al.,High-Luminosity Large Hadron Collider (HL-LHC): Technical design report, Tech

O.A. et al.,High-Luminosity Large Hadron Collider (HL-LHC): Technical design report, Tech. Rep. CERN, Geneva (2020), DOI

work page 2020

[3] [3]

CERN. Geneva. The LHC experiments Committee,Technical design report for the ATLAS Inner Tracker Pixel detector, 2017. 10.17181/CERN.FOZZ.ZP3Q

work page doi:10.17181/cern.fozz.zp3q 2017

[4] [4]

CERN. Geneva. The LHC experiments Committee,Technical design report for the ATLAS Inner Tracker Strip detector, 2017

work page 2017

[5] [5]

Thompson,ATLAS ITk Pixel detector overview, 2025

E.A. Thompson,ATLAS ITk Pixel detector overview, 2025

work page 2025

[6] [6]

Möbius,Pixel detector studies for the ATLAS ITk upgrade for the HL-LHC, Ph.D

S. Möbius,Pixel detector studies for the ATLAS ITk upgrade for the HL-LHC, Ph.D. thesis, Georg-August-University Göttingen, 2023. 10.53846/goediss-9911

work page doi:10.53846/goediss-9911 2023

[7] [7]

Chubinidze,ITk Pixel System Test of the ATLAS Experiment,J

Z. Chubinidze,ITk Pixel System Test of the ATLAS Experiment,J. Instrum.20(2025) C02038

work page 2025

[8] [8]

et al.,The detector control system of the ATLAS experiment,J

A.B.P. et al.,The detector control system of the ATLAS experiment,J. Instrum.3(2008) P05006

work page 2008