1. ATLAS Data Periods in COMA Elizabeth Gallas - Oxford ATLAS Software and Computing Week CERN – April 4-8, 2011

2. April 2011Elizabeth Gallas - Data Periods2 Outline  Introduction to COMA and Data Periods  Data Period Interfaces  Summary and Conclusions

3. April 2011Elizabeth Gallas - Data Periods3 What is COMA ?  COMA: short name for “COnditions MetadatA”:  Part of general effort to consolidate/relate ATLAS physics metadata and relate it to dataset/processing metadata.  A set of relational database tables in Oracle  March 2011: moved to ATLR (NEW)  COMA Database Content:  Run / Luminosity Block aware database: Online and MC Runs  Contains Runs of analysis interest (not all ATLAS Runs)  Events which are reconstructed, producing TAGs*  Contains selected and derived Run/LB-wise information  Sources:  Automated: Conditions DB, Trigger DB, TAG Catalog, other...  Human interface: Data Periods (NEW)  COMA, TAG and AMI Reports and Interfaces  Relay information to users and systems

4. April 2011Elizabeth Gallas - Data Periods4  Storage: COMA Database Tables A collection of selected and derived Run/LB-wise Conditions Source: mostly Conditions DB, Trigger DB plus other sources  Interfaces: RunBrowser Package (sorry: now in naming transition) General principle is to provides unique interfaces for users with reports complementary to, or distinct from, other interfaces: https://atlas-tagservices.cern.ch/tagservices/RunBrowser/index.html NOTE: AMI / ELSSI also has links to and reports/uses COMA information Components of the COMA Project: New Name COMA_Browser COMA_Report COMA_PeriodReport 1 2 3 Topic

5. April 2011Elizabeth Gallas - Data Periods5 COMA: Recent Changes  COMA moved to main ATLAS Offline database  Supported as a critical service  February 2011  Moved into COMA : ATLAS Data Periods  Early March 2011  All basic functionality for Entry, Reporting, Services  Mid-March 2011

6. April 2011Elizabeth Gallas - Data Periods6 Introduction: ATLAS Data Periods  A Data Period is a set of ATLAS Runs grouped for a purpose  Defined by Data Preparation Coordinators  Used in ATLAS data processing, assessment, and selection …  Each Period uniquely defined with a combination of  Project name (i.e. ‘data10_7TeV’)  Period name (i.e. ‘C1’, ‘C2’, ‘C’, ‘AllYear’ …)  Before 2011, Data Periods were  Described on TWiki page  https://twiki.cern.ch/twiki/bin/view/AtlasProtected/DataPeriods https://twiki.cern.ch/twiki/bin/view/AtlasProtected/DataPeriods  Stored in a file based system  Edited by hand by Data Prep Coordination (experts)  Structure evolved over last year with experience  This experience  valuable to decide/define long term solution  New for 2011: Data Periods stored in the COMA DB  Thanks: Beate (DataPrep Coordinator), AMI team, DB experts.

7. April 2011Elizabeth Gallas - Data Periods7 Data Periods: Links to Reports and Services The links/info below can be found on the revised TWiki page: https://twiki.cern.ch/twiki/bin/view/AtlasProtected/DataPeriods  Interactive USERS  COMA Data Period Documentation Interface  https://atlas-tagservices.cern.ch/RBR/rBR_Period_Report.php https://atlas-tagservices.cern.ch/RBR/rBR_Period_Report.php  Comments: hn-atlas-physicsMetadata@cern.ch.hn-atlas-physicsMetadata@cern.ch  Programmatic USERS For systems needing period info: runQuery, beamspot, Data Quality, …, “Data Period Services” provided via pyAMI:  http://ami.in2p3.fr/opencms/opencms/AMI/www/Client/DataPeriods_pyAMI.pdf http://ami.in2p3.fr/opencms/opencms/AMI/www/Client/DataPeriods_pyAMI.pdf  Comments: AMI / Tag_Collector Team.AMI / Tag_Collector Team  Data Preparation EXPERTS: Entry Interface:  https://ami.in2p3.fr/AMI/servlet/net.hep.atlas.Database.Bookkeeping.AMI.Servlet.Command?linkId=1479 https://ami.in2p3.fr/AMI/servlet/net.hep.atlas.Database.Bookkeeping.AMI.Servlet.Command?linkId=1479  Comments: AMI / Tag_Collector Team.AMI / Tag_Collector Team Next slide

8. April 2011Elizabeth Gallas - Data Periods8 https://atlas-tagservices.cern.ch/RBR/rBR_Period_Report.php Period Documentation Menu Purpose: Generate Period documentation for chosen input criteria The report will include a description of all Periods  By Year  E.G. all ‘2010’  By Project  e.g. ‘data10_7TeV’  By specific Period or Group  Click on the project and then your Period of interest Wildcards can be entered in this optional section, then click on Submit button

9. April 2011Elizabeth Gallas - Data Periods9 Example Report: All 2010 Data Period Descriptions Input criteria: Shown in header -/+ highlighted links: These sections expand to show period members Members of data10_7TeV.VdM are VdM1, VdM2, VdM3 Links to COMA and runQuery multi-Run Reports for that Period

10. April 2011Elizabeth Gallas - Data Periods10 COMA: Documentation and Links  COMA TWiki https://twiki.cern.ch/twiki/bin/view/Atlas/ConditionsMetadata  TAG Services portal (contains links to ELSSI,RunBrowser): https://atlas-tagservices.cern.ch/  RunBrowser Portal: https://atlas-tagservices.cern.ch/tagservices/RunBrowser/index.html  COMA Data Period Documentation Interface  COMA Reports (runBrowserReport)  COMA Browser (runBrowser)

11. April 2011Elizabeth Gallas - Data Periods11 COMA Summary and Future  Data Periods is now incorporated into the COMA DB  Report and Service interfaces available  Requests for enhancements from early users  Futures ideas for Data Period extensions:  Extend data content into other areas:  Data Containers, Official GoodRunLists, …  Reports: Add luminosity, event counts, …by period