Abstract <p>The ATLAS EventIndex is a catalog of all recorded and simulated ATLAS events, one of four main experiments at the LHC accelerator at CERN. The Event Picking Service is one of the components of the ATLAS Event Index. It is used when a user wants to collect interesting events from a huge amount of ATLAS data and reprocess them. The process of retrieving an event can be split into separate tasks. The set of tasks may differ for different event types. Some tasks use external services, which can take a long time to receive results. An error may occur as a result of completing the task. Some of these errors can be corrected automatically by the service, but some require administrator intervention. Failed tasks must be restarted from the specified step after the problem is manually corrected by the administrator. This is critical if the error occurs after a long-running task has been completed. All of the above leads to the fact that the Event Picking Service must be flexible and be able to be customized for a specific situation. This paper is dedicated to describing how elasticity is achieved in the Event Picking Service and how it improves during operation.</p>

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

Flexibility Extension of the Event Picking Service for the ATLAS Experiment

  • E. Alexandrov,
  • I. Alexandrov,
  • D. Barberis,
  • A. Yakovlev

摘要

Abstract

The ATLAS EventIndex is a catalog of all recorded and simulated ATLAS events, one of four main experiments at the LHC accelerator at CERN. The Event Picking Service is one of the components of the ATLAS Event Index. It is used when a user wants to collect interesting events from a huge amount of ATLAS data and reprocess them. The process of retrieving an event can be split into separate tasks. The set of tasks may differ for different event types. Some tasks use external services, which can take a long time to receive results. An error may occur as a result of completing the task. Some of these errors can be corrected automatically by the service, but some require administrator intervention. Failed tasks must be restarted from the specified step after the problem is manually corrected by the administrator. This is critical if the error occurs after a long-running task has been completed. All of the above leads to the fact that the Event Picking Service must be flexible and be able to be customized for a specific situation. This paper is dedicated to describing how elasticity is achieved in the Event Picking Service and how it improves during operation.