1. 30 Jan 2009Elizabeth Gallas1 Introduction to TAGs Elizabeth Gallas Oxford ATLAS-UK Distributed Computing Tutorial 29-30 January 2009

2. 30 Jan 2009Elizabeth Gallas2 Outline  Introduction: ATLAS TAGs in the ATLAS Computing model TAG Contents TAG Formats  ELSSI – Event Level Selection Service Interface A Web based interface to ATLAS event selection  Hands on tutorial Selecting events of interest, refining selection criteria Extracting that selection Using selection as input to Athena analysis  Important TAG related hyperlinks

3. 30 Jan 2009Elizabeth Gallas3 The TAG Development Group Argonne: David Malon, Jack Cranshaw, Qizhi Zhang, Peter van Gemmeren Glasgow: MikeKenyon, HelenMcGlone, TomDoherty CERN: Florbela Viegas, Trivan Pal Oxford: Elizabeth Gallas Chicago: Marco Mambelli Grenoble: Solveig Albrand Orsay LAL : Julius Hrivnac Sheffield: Tulay Donszelmann (PAT) Thanks to everyone above and to all users with feedback !

4. 30 Jan 2009Elizabeth Gallas4 What’s a “TAG” (in this talk)  ATLAS “TAG” overload: Not an acronym (retrospectively TAGs Are Great !) Not a CVS tag or a release tag or a project tag Not tracked by the ATLAS Tag Collector Not a COOL (Conditions Database) Tag Not a configTag Not a B, flavor, or muon tag  In this talk: ATLAS TAG application is A system supporting Event-level metadata  About 200 indexed variables for each event Stored in a ‘database’ (Oracle or file based)  1 kB/event -> 1 TB/year PURPOSE: Facilitates event selection for analysis

5. 30 Jan 2009Elizabeth Gallas5 ATLAS TAGs in the ATLAS Computing model  Stages of ATLAS reconstruction  RAW data file  ESD (Event Summary Data) ~ 500 kB/event  AOD (Analysis Object Data) ~ 100 kB/event  TAG (not an acronym) ~ 1 kB/event  TAGs Produced in reconstruction Can be re-produced in re-processing Customized TAGs can be defined/produced TAG formats:  File based: AthenaAwareNtuple format (AANT)  Database: available globally through network connection Used by the TAG Browser (ELSSI)

6. 30 Jan 2009Elizabeth Gallas6 TAG related hyperlinks: TWiki with TAG content in ATLAS release: https://twiki.cern.ch/twiki/bin/view/AtlasProtected/ TagForEventSelection https://twiki.cern.ch/twiki/bin/view/AtlasProtected/ TagForEventSelection TWiki for Tutorial: https://twiki.cern.ch/twiki/bin/view/Atlas/EventTag Tutorials https://twiki.cern.ch/twiki/bin/view/Atlas/EventTag Tutorials 4 Tutorial Components  ELSSI (Browser based)  File-based TAGs (Command line based)  JiveXML with TAGs (Atlantis Event Display)  TAG based selection with PAthena on the Grid ELSSI - Event Level Selection Service Interface: https://voatlas18.cern.ch/tagservices/index.htm

7. 30 Jan 2009Elizabeth Gallas7 “TAG content”: Your selection variables  PAT (Physics Analysis Tools) group supports ‘official’ TAG content based on input from physics groups  (YOU !)  ‘TAG Database’ Application includes ~200 variables/event:  Event identification (run, event, lumi block numbers, timestamp, …)  Global quantities (e.g., missing eT)  Trigger decisions at all three levels (now bit encoded)  Numbers of electrons, muons, photons, taus, and jets pT, eta, phi for highest-pT objects  Detector status and quality words  Physics and performance group status words ‘Run Metadata’ at Temporal, Fill, Run, Lumi-block levels references to AOD,ESD,RAW for back-navigation A variety of supporting tools and infrastructure  ELSSI is a web based supporting tool Helps you navigate through “TAG content“ Uses other supporting tools and infrastructure Retrieve results in a number of forms

8. 30 Jan 2009Elizabeth Gallas8 ELSSI: TAG Browser Basics  An interface to the TAG Database Supported browsers: Firefox, Safari (not IE ) Requires Grid Certificate  Allows pre-selection of events for analysis, guiding the user through the selection process User Input Stream Temporal QualityPhysicsTrigger COUNT events SELECT attributes RETRIEVE events

9. 30 Jan 2009Elizabeth Gallas9 ELSSI: Implementation & Features  Running on server at CERN PHP and Javascript on backend  Features: Formulate multi-dimensional queries  At Run/LB and Event level Query caching Event counting Display Results (graphical and tabular form) Retrieve events in ROOT file Register collection in AMI

10. 30 Jan 2009Elizabeth Gallas10 https://voatlas18.cern.ch/tagservices/index.htm ELSSI Gateway Choose FDR2C link

11. 30 Jan 2009Elizabeth Gallas11 Summary  Metadata in a database is a powerful tool A great variety of dynamic selection criteria and reporting become possible  Development is ongoing to improve Interfaces  Functionality  Usability Integrate infrastructure tools  For comments/suggestions: ATLAS Physics Metadata Hypernews

12. 30 Jan 2009Elizabeth Gallas12 Backup Slides

13. 30 Jan 2009Elizabeth Gallas13 Browser front page for FDR2 – ‘Temporal Tab’

14. 30 Jan 2009Elizabeth Gallas14 Browser – ‘Stream Tab’

15. 30 Jan 2009Elizabeth Gallas15 Browser – ‘ Trigger Tab’

16. 30 Jan 2009Elizabeth Gallas16 ‘Physics Attributes Tab’

17. 30 Jan 2009Elizabeth Gallas17 ‘Review Query tab’

18. 30 Jan 2009Elizabeth Gallas18 ‘Perform Query’: Count tab Count events meeting criteria … revise criteria… count again… revise criteria …

19. 30 Jan 2009Elizabeth Gallas19 ‘Perform Query’: Display Results tab  Get an idea of the attribute distributions  Draw histograms – new functionality from Julius (still in development)

20. 30 Jan 2009Elizabeth Gallas20 Retrieve Events  After refining query, generate a ROOT TAG file with selected events

21. 30 Jan 2009Elizabeth Gallas21 Left Frame: about your Session(s)  Save/Share Session(s) Can now save a query session for later use Uses cookies  Browser specific Share saved sessions with others  Selection Summary Displays selection criteria of your session

22. 30 Jan 2009Elizabeth Gallas22 Working on … (1)  Incorporating Detector Status (DQ)  Loading online Runs Even in the absence of TAG production  An ELSSI “skim” button (Skimming Service) using GangaTNT: From your selected TAG events, generate an AOD dataset with only those events Output registered as new dataset Runs GANGA on the server to run the job on behalf of the user  User proxy is delegated to the server  Monitoring loop checks job status and notifies user of job completion / failure  Integrate GangaTNT into GangaGUI.

23. 30 Jan 2009Elizabeth Gallas23 Ganga TNT

24. 30 Jan 2009Elizabeth Gallas24 Working on … (2)  Using TAGs with PAthena: Steps create an event collection (events.root) with ELSSI setup Pathena and the Grid environment use a joboption like the one you'd use to run a local analysis based on TAGs submit the Pathena job use Panda monitoring to check for completion use DQ2 enduser clients (dq2-get) to retrieve the output files  Problem: AOD to AOD (copy) is problematic in some releases

25. 30 Jan 2009Elizabeth Gallas25 TAG job with Pathena Panda TAG DB ELSSI or POOL Collection Utilities ELSSI or POOL Collection Utilities events.root POOL Collection Utilities events.root events1.root Output Dataset DQ2 Catalogues Pathena DQ2 Client jobOption