POOL Collections

The POOL Collections packages are developed and used by ATLAS.

POOL collections can be stored in both ROOT and relational formats, through the RootCollections and RelationalCollections packages, respectively. These are implemented using ROOT and CORAL directly, without passing through the POOL RootStorageSvc and RelationalStorageSvc.

The ATLAS TAG database is populated by uploading into Oracle the ROOT event collection files. For more information please refer to the ATLAS CollectionPOOLUtilitiesHowTo.

Useful references:

  • F. Viegas et al., "The ATLAS TAGS database distribution and management", J. Phys. Conf. Ser. 219 072058 (2010) [iop.org]
  • M. Mambelli et al., "Job optimization in ATLAS TAG-based distributed analysis", J. Phys. Conf. Ser. 219 072042 (2010) [iop.org]
  • P. v. Gemmeren et al., "New developments in file-based infrastructure for ATLAS event selection", J. Phys. Conf. Ser. 219 032061 [iop.org]
  • M. Nowak et al., "Explicit state representation and the ATLAS event data model: theory and practice", J. Phys. Conf. Ser. 119 042024 (2008) [iop.org]

-- AndreaValassi - 12-Oct-2010

This topic: Persistency > ObsoleteTopics > OLDPoolCollections
Topic revision: r3 - 2013-10-02 - AndreaValassi
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback