Testing framework and monitoring system for the ATLAS EventIndex

The ATLAS EventIndex is a global catalogue of the events collected, processed or generated by the ATLAS experiment. The system was upgraded in advance of LHC Run 3, with a migration of the Run 1 and Run 2 data from HDFS MapFiles to HBase tables with a Phoenix interface. Two frameworks for testing functionality and performance of the new system have been developed. There are two types of tests running. First, the functional test that must check the correct functioning of the import chain. These tests run event picking over a random set of recently imported data to see if the data have been imported correctly, and can be accessed by both the CLI and the PanDA client. The second, the performance test, generates event lookup queries on sets of the EventIndex data and measures the response times. These tests enable studies of the response time dependence on the amount of requested data, and data sample type and size. Both types of tests run regularly on the existing system. The results of the regular tests as well as the statuses of the main EventIndex subsystems (services health, loaders status, filesystem usage, etc.) are sent to InfluxDB in JSON format via HTTP requests and are displayed on Grafana monitoring dashboards. In case (part of) the system misbehaves or becomes unresponsive, alarms are raised by the monitoring system

Functional Analysis of DNMT3A DNA Methyltransferase Mutations Reported in Patients with Acute Myeloid Leukemia

In mammals, DNA methylation is necessary for the maintenance of genomic stability, gene expression regulation, and other processes. During malignant diseases progression, changes in both DNA methylation patterns and DNA methyltransferase (MTase) genes are observed. Human de novo MTase DNMT3A is most frequently mutated in acute myeloid leukemia (AML) with a striking prevalence of R882H mutation, which has been extensively studied. Here, we investigate the functional role of the missense mutations (S714C, R635W, R736H, R771L, P777R, and F752V) found in the catalytic domain of DNMT3A in AML patients. These were accordingly mutated in the murine Dnmt3a catalytic domain (S124C, R45W, R146H, R181L, P187R, and F162V) and in addition, one-site CpG-containing DNA substrates were used as a model system. The 3-15-fold decrease (S124C and P187R) or complete loss (F162V, R45W, and R146H) of Dnmt3a-CD methylation activity was observed. Remarkably, Pro 187 and Arg 146 are not located at or near the Dnmt3a functional motives. Regulatory protein Dnmt3L did not enhance the methylation activity of R45W, R146H, P187R, and F162V mutants. The key steps of the Dnmt3a-mediated methylation mechanism, including DNA binding and transient covalent intermediate formation, were examined. There was a complete loss of DNA-binding affinity for R45W located in the AdoMet binding region and for R146H. Dnmt3a mutants studied in vitro suggest functional impairment of DNMT3A during pathogenesis

The ATLAS EventIndex: a BigData catalogue for all ATLAS experiment events

The ATLAS EventIndex system comprises the catalogue of all events collected, processed or generated by the ATLAS experiment at the CERN LHC accelerator, and all associated software tools to collect, store and query this information. ATLAS records several billion particle interactions every year of operation, processes them for analysis and generates even larger simulated data samples; a global catalogue is needed to keep track of the location of each event record and be able to search and retrieve specific events for in-depth investigations. Each EventIndex record includes summary information on the event itself and the pointers to the files containing the full event. Most components of the EventIndex system are implemented using BigData open-source tools. This paper describes the architectural choices and their evolution in time, as well as the past, current and foreseen future implementations of all EventIndex components.Comment: 21 page

Deployment and Operation of the ATLAS EventIndex for LHC Run 3

The ATLAS Eventlndex is the global catalogue of all ATLAS real and simulated events. During the LHC long shutdown between Run 2 (20152018) and Run 3 (2022-2025) all its components were substantially revised and a new system was deployed for the start of Run 3 in Spring 2022. The new core storage system, based on HBase tables with a SQL interface provided by Phoenix, allows much faster data ingestion rates and scales much better than the old one to the data rates expected for the end of Run 3 and beyond. All user interfaces were also revised and a new command-line interface and web services were also deployed. The new system was initially populated with all existing data relative to Run 1 and Run 2 datasets, and then put online to receive Run 3 data in real time. After extensive testing, the old system, which ran in parallel to the new one for a few months, was finally switched off in October 2022. This paper describes the new system, the move of all existing data from the old to the new storage schemas and the operational experience gathered so far

DIRECTION OF PROPERTIES INCREASING OF CANTOR HEA

В настоящей статье выполнен обзор публикаций отечественных и зарубежных авторов по двум направлениям улучшения свойств сплава: CoCrFeNiMn легированием, выделениями и термообработкой, и использованием фазовых диаграмм Calphad. По первому направлению проанализирована роль легирования B, Vi, Al, V, Si, Nb; нановыделениями, различными режимами термической и деформационной обработки. Сделан вывод о необходимости проведения экспериментов по легированию ВЭС Zr и Nb, хорошо зарекомендовавших себя в упрочнении сталей. Показано, что создание и модифицирование свойств пятикомпонентных ВЭС возможно при использовании компьютерных программ Calphad, разработанных для расчета диаграмм состояния.This article reviews the publications of domestic and foreign authors in two areas of improving the properties of alloy: CoCrFeNiMn alloying, precipitation and heat treatment and the use of Calphad phase diagrams. In the first direction, the role of doping with B, Vi, Al, V, Si, Nb is analyzed; nanoprecipitations, various modes of thermal and deformation processing. It is concluded that it is necessary to conduct experiments on the alloying of HEA with Zr and Nb, which have proven themselves well in hardening steels. The creation and modification of the properties of fivecomponent wind farms is possible using the Calphad computer programs developed for calculating state diagrams.Работа выполнена при поддержке гранта РНФ 23-49-00015

Characteristics of jets from the decay of stopped exotic particles in the ATLAS detector

The supersymmetry theory predicts the existence of sparticles that decay some later time after they were produced. To better understand the properties of these, the study of jet substructure variables within jets created during simulated long-lived gluino decays was conducted. Three Monte-Carlo simulated decays for different gluino and neutralino masses and one cosmic run (taken during 2016) were used in the analysis . To obtain the signals from gluinos it is necessary to take into account many backgrounds and carefully separate those. The distributions of jet variables such as energy, transverse momentum, jet’s location within the ATLAS detector define the features of any signal and allow to choose selection criteria. Those variables and correlation between them were studied in this work

Performance testing framework for the ATLAS EventIndex

The ATLAS EventIndex is going to be upgraded in advance of LHC Run 3. A framework for testing the performance of both the existing system and the new system has been developed. It generates various queries (event lookup, trigger searches, etc.) on sets of the EventIndex data and measures the response times. Studies of the response time dependence on the amount of requested data, and data sample type and size, can be performed. Performance tests run regularly on the existing EventIndex and will run on the new system when ready. The results of the regular tests are displayed on the monitoring dashboards, and they can raise alarms in case (part of) the system misbehaves or becomes unresponsive

Performance testing framework for the ATLAS EventIndex

The ATLAS EventIndex is going to be upgraded in advance of LHC Run 3. A framework for testing the performance of both the existing system and the new system has been developed. It generates various queries (event lookup, trigger searches, etc.) on sets of the EventIndex data and measures the response times. Studies of the response time dependence on the amount of requested data, and data sample type and size, can be performed. Performance tests run regularly on the existing EventIndex and will run on the new system when ready. The results of the regular tests are displayed on the monitoring dashboards, and they can raise alarms in case (part of) the system misbehaves or becomes unresponsive

Testing framework and monitoring system for the ATLAS EventIndex

The ATLAS EventIndex is a global catalogue of the events collected, processed or generated by the ATLAS experiment. The system was upgraded in advance of LHC Run 3, with a migration of the Run 1 and Run 2 data from HDFS MapFiles to HBase tables with a Phoenix interface. The frameworks for testing functionality and performance of the new system have been developed. There are two types of tests running. First, the functional test that must check the correct functioning of the import chain. These tests run event picking over a random set of recently imported data to see if the data have been imported correctly, and can be accessed by both the CLI and the PanDA client. The second, the performance test, generates event lookup queries on sets of the EventIndex data and measures the response times. These tests enable studies of the response time dependence on the amount of requested data, and data sample type and size. Both types of tests run regularly on the existing system. The results of the regular tests as well as the statuses of the main EventIndex sub-systems (services health, loaders status, filesystem usage, etc.) are sent to InfluxDB in JSON format via HTTP requests and are displayed on Grafana monitoring dashboards. In case (part of) the system misbehaves or becomes unresponsive, alarms are raised by the monitoring system