TriggerDB copy in TriggerTool Trigger Configuration Group reporter: S. M. Li (DESY) Jan. 28th , 2008 DESY ATLAS Group Meeting Zeuthen

Outline What’s TriggerDB? How to copy it? What we have done? What's continue?

What’s triggerDB TriggerDB is the central part of the configuration system. It is used to store and protect all data that are needed to configure the three levels of the ATLAS trigger.

Trigger Tool The TriggerTool is the central tool for the configuration of the Trigger. The TriggerTool GUI(Graphical User Interface) It allows the user to browse the Trigger Database, make new configurations, store these configurations, apply consistency checks and numerous other tasks. The tool is for both the LVL1 and HLT configuration.

Reminder: The Trigger Configuration System LVL1 + HLT has integrated system TriggerDB online running offline shift crew offline user expert TriggerTool DB population scripts R/O interface Configuration System compilers Online: ”Trigger Control Centre” Offline: Tool to browse the TriggerDB TriggerTool: Java Front-End to TriggerDB modification, browsing of TriggerDB TriggerDB relational DB (Oracle and MySQL) complete description of online event selection all versions (archiving) Clients: online: central trigger, L1Muon, L1Calo, all nodes of HLT farm offline: simulation jobs, also from TriggerDB Not shown: Distribution of configuration data to reconstruction and analysis Johannes ATLAS Trigger & Physics week

Ralational Schema of TriggerDB release name LVL1 configuration data, incl.: HW Files Job Options for HLT Algorithms HLT Chain definitions

How to do with it? Add a “DBcopy” button in the TT window(SMT) Connect with DBs(source and destination) Check if the DBs are connected rightly Transfer DB if it’s not existed in the destination DB server. (How to do with it if it’s existed in the destination DB server? ) Results display

Combined_schema.sql is an sql file to store the schema of TriggerDB. Modify and execute it to create the tables in this schema Write select sentences such as: “SELECT * FROM SUPER_MASTER_TABLE WHERE SMT_ID = SET_SMT_ID ” to read out the records of the tables what we want to copy. (fill in one file name querys.sql) Insert the records to the destination DB.

Copy step by step Select the database which we want to copy Click “DBcopy” button in TT GUI Click the button “open destination DB” Fill in the information of destination DB Click “open” to check if the destination DB is connected successfully Click “copy” button to copy DB Result Check

TriggerTool GUI

click

click

Result check Before DB copy After DB copy

Summary and future work TriggerDB could be copied in TriggerTool freely Future work Make the interface more convenience When the DB exists in the destination DB space, we just give up to copy it. Any better way? Update it when there is any good suggestion about this work ……