Cargando…
Monitoring Quality of ATLAS ITk Strip Sensors through Database
The high-Luminosity LHC upgrade necessitates a complete replacement of the ATLAS Inner Detector with a larger all-silicon tracker. The strip portion of it covers 165 m$^2$ area, afforded by the strip sensors. Following several prototype iterations and a successful pre-production, a full-scale produc...
Autores principales: | , , , , , , , , , , , , , , , , , , , , , , , , , , |
---|---|
Lenguaje: | eng |
Publicado: |
2023
|
Materias: | |
Acceso en línea: | https://dx.doi.org/10.22323/1.420.0058 http://cds.cern.ch/record/2847934 |
Sumario: | The high-Luminosity LHC upgrade necessitates a complete replacement of the ATLAS Inner Detector with a larger all-silicon tracker. The strip portion of it covers 165 m$^2$ area, afforded by the strip sensors. Following several prototype iterations and a successful pre-production, a full-scale production started in 2021, to finish in 2025. It will include about 21,000 wafers and a factor of 5 higher throughput than pre-production, with about 500 sensors produced and tested per month. The transition to production stressed the need to evaluate the results from the Quality Control (QC) and Quality Assurance (QA) tests quickly to meet the monthly delivery schedule. The test data come from 15 collaborating institutes, therefore a highly distributed system with standardized interfaces was required. Specialized software layers of QA and QC Python code were developed against the backend of the ITk database (DB) for this purpose. The developments included particularities and special needs of the Strip Sensors community, such as the large variety of different test devices and test types, the necessary test formats, and different workflows at the test sites. Special attention was paid to techniques facilitating the development and user operations, for example creation of “parallel” sets of dummy DB objects for practice purposes, iterative verification of operability, and the automatic upload of test data. The scalability concerns and automation of the data handling were included in the system architecture from the very inception. The full suite of functionalities include data integrity checks, data processing to extract and evaluate key parameters, cross-test comparisons, and summary reporting for continuous monitoring. We will also describe the lessons learned and the necessary evolution of the system. |
---|