Journal article
Using TAGs to speed up the ATLAS analysis process
- Abstract:
- In the ATLAS experiment, Tag Data, or short TAG, are event-level metadata -thumbnail information about events to support efficient identification and selection of events of interest to a given analysis. TAG quantities range from detector status and trigger information to basic physics quantities, e. g. the number of loose electrons candidates and kinematic information for a limited number of these candidates sorted by their transverse momentum. The average TAG size per event is around 1kB, which is a factor 100 smaller than the Analysis Object Data (AOD) used for physics analysis. TAGs are primarily produced from AODs and stored in ROOT files. For easier access and usability TAGs are also stored in a database. Queries to the database can produce again TAG files. In a standard ATLAS analysis job, TAGs can be used to preselect events based on the TAG quantities before accessing the full AOD content. This allows for a significant speed up of the processing time. This paper will discuss the different analysis work flows using TAGs and compare them with other analysis work flows within ATLAS. Further, the performance for preselecting events using either directly AODs or TAG files is measured and compared. Peak performance is estimated on a single machine with local disk access, while more realistic performance is estimated using Grid like data access.
Actions
Access Document
- Files:
-
-
(Preview, pdf, 562.7KB, Terms of use)
-
- Publisher copy:
- 10.1088/1742-6596/331/3/032007
Authors
- Journal:
- Journal of Physics: Conference Series More from this journal
- Volume:
- 331
- Issue:
- PART 3
- Pages:
- 032007-032007
- Publication date:
- 2011-01-01
- DOI:
- EISSN:
-
1742-6596
- ISSN:
-
1742-6588
- Language:
-
English
- UUID:
-
uuid:5e256152-a494-4c65-ad67-6d98e90f5e29
- Local pid:
-
pubs:343162
- Source identifiers:
-
343162
- Deposit date:
-
2012-12-19
Terms of use
- Copyright date:
- 2011
If you are the owner of this record, you can report an update to it here: Report update to this record