Database for NA61 experiment

1. Nuclear Physics Department Institute of Physics University of Silesia Seweryn Kowalski Database for NA61 experiment 2011-02-15

2. Database status • Database divide into two pieces: • MySQL/ORACLE(test) • DSPACK • Installation inside CERN • lxplus cluster: • na49db.cern.ch • Access only from CERN • Oracle devdb10 KEY1,.., KEYN MySQL/ORACLE FILENAME NA61 SOFT FILENAME DSPACK STRUCTURE DSPACK FILES DSPACK FILE

3. Database status • Possible installation outside CERN • Local installation • installation on CernVM • XML version • Backup MySQL server – Katowice NUPH Cluster • Version in DB: • Possible to set default version • Different version for various structures • Client side • calls from shell scripts, • plug-in system for DSSERVER • $NA49_ROOT/SCRIPTS/src/ KEY1,.., KEYN MySQL/Oracle FILENAME NA61 SOFT DSPACK FILES LXPLUS, LXBATCH NA61PC?? OUTSIDE

4. DB cache area on AFS • New place for .ds files • /afs/cern.ch/na61/DB/ • Cron job – synchronization between na49db and AFS directory (once per day 1:07) • Modification of the hepdb.plugin • Lxplus, lxbatch, na61pc – no local cache files (afs) • Other host: cache file in ./hepdb directory • Plug-in tested and committed to SVN • Backup MySQL DB on h041.nuph.us.edu.pl • Works only with new hepdb.plugin • NA49_DBHOST=h041.nuph.us.edu.pl

5. DB Update • TPC calibration constants for 2009 runs: 7124-20000 • New default KEY10=V09C • VTPC done, MTPC not yet(contact Alexander) • T0 in DB • Data in calibration file, CODE=CA • New structures: • structt0_det {float_tdt0[5]; //T0 for: vt1, vt2, mtl, mtr, gap} • structt0_global {float_tgt0; //global T0} • Geometry • 2009 LHT runs, • Cumulative update for BPD geometry runs: 5650-8946 • Update geometry of the GAP TPC for 2007 runs • https://twiki.cern.ch/twiki/bin/viewauth/NA61/DBUpdateLog

6. Database status - support • DB - information • NA61 TWIKI page – topic Database • Types of the keys for DB • Keys values for runs • Structures in DB • DB Update Log • DB Dump

7. Database dump http://www.nuph.us.edu.pl/~skowalsk/local_user/db/db_dump/ DSPACK DUMP SQL DUMP

8. KEYs values No defaults

9. Problems with KEYs • Experts • Perfect solution – see Antoni M. TWIKI log

10. In the spirit of Software Update • New structure of DB • One DBMS (like MySQL (tested) or Oracle (tested)) • Three different kind of users: • User/ Client (ordinary user) – no knowledge about DB, calibration parameters etc, • Developer/ Experts of some subsystems – knowledge of parameters for subsystems and dependence systems • Database Administrator – knowledge about DB Run Number Global versions (only one default for run) Logical connection of parameters or detector systems Structure1 Structure2 Structure3 STR1 V1 STR1 V2 STR2 V1 STR2 V1 STR3 V1 …

11. In the spirit of Software Update mysql> select * fromProduction; +----------------+----------------+-------------+---------------------+ | RunNumber | RunDate | RunTime | DefaultVersion | +----------------+----------------+-------------+---------------------+ | 8001 | 2009-09-11 | 10:00:00 | V09_01 | | 8002 | 2009-09-11 | 18:00:00 | V09_02 | | 8003 | 2009-03-12 | 10:00:00 | V09_02 | | 8004 | 2009-03-11 | 18:00:00 | V09_01 | +----------------+----------------+-------------+---------------------+ 4 rowsin set (0.00 sec) mysql> select * fromListOfVersions; +------------------+---------------------+-------------------------------+ | GlobalVersion | StructureName | StructureVersion | +------------------+---------------------+-------------------------------+ | V09_01 | GPCCalib | V_GPCCalib_09_02 | | V09_01 | BPDGeometry | V_BPDGEOM_09_02 | | V09_01 | GPCGeometry | V_GPCGEOM_09_01 | | V09_02 | BeamGeometry | V_BEAMGEOM_09_01 | | V09_02 | BPDGeometry | V_BPDGEOM_09_03 | +------------------+-----------------------+-------------------------------+ 5 rowsin set (0.00 sec) mysql> select * fromBPDGeometry; +-------------------+------------------===-----+------------------------------------------+---------------+ | StructureName | StructureVersion | DataFileName | comments | +-------------------+-----------------------------+------------------------------------------+---------------+ | BPDGeometry | V_BPDGEOM_09_01 | BPDGeometry/run111-999.ds | NULL | | BPDGeometry | V_BPDGEOM_09_02 | BPDGeometry/run111-999.root | NULL | | BPDGeometry | V_BPDGEOM_09_03 | BPDGeometry/run888-999.ds | NULL | +-------------------+-----------------------------+------------------------------------------+---------------+ 3 rowsin set (0.00 sec)

12. In the spirit of Software Update • Name convention: • Global: V+2 last digits of year _ 2 digitsi.e. • V09_01, • V09_02 • Structure: V_structure name_2 last digits of year _ 2 digits • V_BDPGEOM_09_01 • V_GPCGEOM_09_01

13. New DB architecture

14. New DB architecture – user privileges DB Administrator Expert - Developer

15. Summary • The DB is updated on user request • Backup DB server • Possible local installation • Installation on ORACLE (development stage) • Possible access from outside • The development DB on Oracle – devdb10 user: NA61_skowalsk • Conversion from MySQL SQL to Oracle SQL for old DB – done • The new DB structure is tested on MySQL system • Ready to install • Necessary modification of plug-in script • Keep data in .ds or .root files

16. Next steps • Near future • Move from the development to the production stage on Oracle • Plug-in modification for Oracle • Collaboration decision on DBMS • Far future (but not so far) • Production stage of new DB • New client for DB • Collaboration commissioning

17. seweryn.kowalski@us.edu.pl Thank you