1. 1 Configuration Database David Forrest University of Glasgow MICO Meeting 13/10/2008 d.forrest@physics.gla.ac.uk

2. 2 What We Want & Don’t Want The configuration database DOES store information to reconstruct the following: - Geography of experiment - Cabling information for detectors - Calibration information for detectors …for every run. But DOES NOT store: - Control and monitoring parameters: temperatures, currents and such, already dealt with by DAQ. (JSG)

3. 3 What Can We Do With It A version 0 of the Configuration Database is currently implemented @ RAL We are working now on communication between the Database and G4MICE - You could reconstruct a real experiment in G4MICE - You could store a monte carlo simulation’s configuration in the DB Associated with each run: - You could have several calibrations stored in database for one detector (and by default use the latest one) - You could have second corrected geometries, cablings if errors were found What would you like to do with it? What do you want to STORE And what do you want to DO

4. 4 A Walkthrough of What We Have So Far (don’t be put off)

5. 5 In Words We have a set of ‘configurations’ stored in the database. These consist of all geographical, cabling and calibration information. A run has at least one of these configurations. - So when we do a run, we can store all information regarding config, calib + area. Can you see where in the DB you would go for information you need? If not, is that information there? If it’s not there let me know now

6. 6 Help There is an upper limit on the performance of the database – this is set by the amount of feedback and information I receive to feed into a good design, and good performance I could really use some feedback on the important things to store (imagine they are member variables of a class, or global variables of a piece of code) for calibration and cabling from people who know about detectors You don’t need to know anything about databases, that’s my job. But if you know about your detector, help me out. (Previous calls CM20, CM21, and database is being implemented now)

7. 7 Questions Can you see where in the DB you would go for information you need? If not, is that information there? If it’s not there let me know now What do you want to STORE? And what do you want to DO? Answers to any or all of these questions would be wonderful, from as wide an audience of participants as possible (not just coordinators).

8. 8 Appendix: DB Primer