Cargando…

The ATLAS EventIndex: data flow and inclusion of other metadata

The ATLAS EventIndex is the catalogue of the event-related metadata for the information collected from the ATLAS detector. The basic unit of this information is the event record, containing the event identification parameters, pointers to the files containing this event as well as trigger decision i...

Descripción completa

Detalles Bibliográficos
Autores principales: Barberis, Dario, Cardenas Zarate, Simon Ernesto, Favareto, Andrea, Fernandez Casani, Alvaro, Gallas, Elizabeth, Garcia Montoro, Carlos, Gonzalez de la Hoz, Santiago, Hrivnac, Julius, Malon, David, Prokoshin, Fedor, Salt, Jose, Sanchez, Javier, Toebbicke, Rainer, Yuan, Ruijun
Lenguaje:eng
Publicado: 2016
Materias:
Acceso en línea:https://dx.doi.org/10.1088/1742-6596/762/1/012028
http://cds.cern.ch/record/2135262
_version_ 1780949939117883392
author Barberis, Dario
Cardenas Zarate, Simon Ernesto
Favareto, Andrea
Fernandez Casani, Alvaro
Gallas, Elizabeth
Garcia Montoro, Carlos
Gonzalez de la Hoz, Santiago
Hrivnac, Julius
Malon, David
Prokoshin, Fedor
Salt, Jose
Sanchez, Javier
Toebbicke, Rainer
Yuan, Ruijun
author_facet Barberis, Dario
Cardenas Zarate, Simon Ernesto
Favareto, Andrea
Fernandez Casani, Alvaro
Gallas, Elizabeth
Garcia Montoro, Carlos
Gonzalez de la Hoz, Santiago
Hrivnac, Julius
Malon, David
Prokoshin, Fedor
Salt, Jose
Sanchez, Javier
Toebbicke, Rainer
Yuan, Ruijun
author_sort Barberis, Dario
collection CERN
description The ATLAS EventIndex is the catalogue of the event-related metadata for the information collected from the ATLAS detector. The basic unit of this information is the event record, containing the event identification parameters, pointers to the files containing this event as well as trigger decision information. The main use case for the EventIndex is event picking, as well as data consistency checks for large production campaigns. The EventIndex employs the Hadoop platform for data storage and handling, as well as a messaging system for the collection of information. The information for the EventIndex is collected both at Tier-0, when the data are first produced, and from the Grid, when various types of derived data are produced. The EventIndex uses various types of auxiliary information from other ATLAS sources for data collection and processing: trigger tables from the condition metadata database (COMA), dataset information from the data catalogue AMI and the Rucio data management system and information on production jobs from the ATLAS production system. The ATLAS production system is also used for the collection of event information from the Grid jobs. EventIndex developments started in 2012 and in the middle of 2015 the system was commissioned and started collecting event metadata, as a part of ATLAS Distributed Computing operations.
id cern-2135262
institution Organización Europea para la Investigación Nuclear
language eng
publishDate 2016
record_format invenio
spelling cern-21352622019-09-30T06:29:59Zdoi:10.1088/1742-6596/762/1/012028http://cds.cern.ch/record/2135262engBarberis, DarioCardenas Zarate, Simon ErnestoFavareto, AndreaFernandez Casani, AlvaroGallas, ElizabethGarcia Montoro, CarlosGonzalez de la Hoz, SantiagoHrivnac, JuliusMalon, DavidProkoshin, FedorSalt, JoseSanchez, JavierToebbicke, RainerYuan, RuijunThe ATLAS EventIndex: data flow and inclusion of other metadataComputing and ComputersThe ATLAS EventIndex is the catalogue of the event-related metadata for the information collected from the ATLAS detector. The basic unit of this information is the event record, containing the event identification parameters, pointers to the files containing this event as well as trigger decision information. The main use case for the EventIndex is event picking, as well as data consistency checks for large production campaigns. The EventIndex employs the Hadoop platform for data storage and handling, as well as a messaging system for the collection of information. The information for the EventIndex is collected both at Tier-0, when the data are first produced, and from the Grid, when various types of derived data are produced. The EventIndex uses various types of auxiliary information from other ATLAS sources for data collection and processing: trigger tables from the condition metadata database (COMA), dataset information from the data catalogue AMI and the Rucio data management system and information on production jobs from the ATLAS production system. The ATLAS production system is also used for the collection of event information from the Grid jobs. EventIndex developments started in 2012 and in the middle of 2015 the system was commissioned and started collecting event metadata, as a part of ATLAS Distributed Computing operations.ATL-SOFT-PROC-2016-003oai:cds.cern.ch:21352622016-03-01
spellingShingle Computing and Computers
Barberis, Dario
Cardenas Zarate, Simon Ernesto
Favareto, Andrea
Fernandez Casani, Alvaro
Gallas, Elizabeth
Garcia Montoro, Carlos
Gonzalez de la Hoz, Santiago
Hrivnac, Julius
Malon, David
Prokoshin, Fedor
Salt, Jose
Sanchez, Javier
Toebbicke, Rainer
Yuan, Ruijun
The ATLAS EventIndex: data flow and inclusion of other metadata
title The ATLAS EventIndex: data flow and inclusion of other metadata
title_full The ATLAS EventIndex: data flow and inclusion of other metadata
title_fullStr The ATLAS EventIndex: data flow and inclusion of other metadata
title_full_unstemmed The ATLAS EventIndex: data flow and inclusion of other metadata
title_short The ATLAS EventIndex: data flow and inclusion of other metadata
title_sort atlas eventindex: data flow and inclusion of other metadata
topic Computing and Computers
url https://dx.doi.org/10.1088/1742-6596/762/1/012028
http://cds.cern.ch/record/2135262
work_keys_str_mv AT barberisdario theatlaseventindexdataflowandinclusionofothermetadata
AT cardenaszaratesimonernesto theatlaseventindexdataflowandinclusionofothermetadata
AT favaretoandrea theatlaseventindexdataflowandinclusionofothermetadata
AT fernandezcasanialvaro theatlaseventindexdataflowandinclusionofothermetadata
AT gallaselizabeth theatlaseventindexdataflowandinclusionofothermetadata
AT garciamontorocarlos theatlaseventindexdataflowandinclusionofothermetadata
AT gonzalezdelahozsantiago theatlaseventindexdataflowandinclusionofothermetadata
AT hrivnacjulius theatlaseventindexdataflowandinclusionofothermetadata
AT malondavid theatlaseventindexdataflowandinclusionofothermetadata
AT prokoshinfedor theatlaseventindexdataflowandinclusionofothermetadata
AT saltjose theatlaseventindexdataflowandinclusionofothermetadata
AT sanchezjavier theatlaseventindexdataflowandinclusionofothermetadata
AT toebbickerainer theatlaseventindexdataflowandinclusionofothermetadata
AT yuanruijun theatlaseventindexdataflowandinclusionofothermetadata
AT barberisdario atlaseventindexdataflowandinclusionofothermetadata
AT cardenaszaratesimonernesto atlaseventindexdataflowandinclusionofothermetadata
AT favaretoandrea atlaseventindexdataflowandinclusionofothermetadata
AT fernandezcasanialvaro atlaseventindexdataflowandinclusionofothermetadata
AT gallaselizabeth atlaseventindexdataflowandinclusionofothermetadata
AT garciamontorocarlos atlaseventindexdataflowandinclusionofothermetadata
AT gonzalezdelahozsantiago atlaseventindexdataflowandinclusionofothermetadata
AT hrivnacjulius atlaseventindexdataflowandinclusionofothermetadata
AT malondavid atlaseventindexdataflowandinclusionofothermetadata
AT prokoshinfedor atlaseventindexdataflowandinclusionofothermetadata
AT saltjose atlaseventindexdataflowandinclusionofothermetadata
AT sanchezjavier atlaseventindexdataflowandinclusionofothermetadata
AT toebbickerainer atlaseventindexdataflowandinclusionofothermetadata
AT yuanruijun atlaseventindexdataflowandinclusionofothermetadata