1. DCDB A. Sandoval TPC meeting, Tanka Village 16 May 2004

2. Contents News from the DCDB team in Warsaw News from the DCDB team in Warsaw News from the GSI DCDB News from the GSI DCDB News from the TPC use of the DCDB News from the TPC use of the DCDB News from ALICE Physics Data Challenge News from ALICE Physics Data Challenge

3. the DCDB components User Dictionary Wizard SQL Satellite DCDB Satellite DCDB Rabbit (DMS server) Test Setup With LabView LabView Server Warsaw Heidelberg GSI Heidelberg Frankfurt GSI Web

4. News from Warsaw new database version released v1.30, done to include the ALICE ID and improve functionality new database version released v1.30, done to include the ALICE ID and improve functionality moved all satellite DCDB to v1.30 moved all satellite DCDB to v1.30 created central DCDB created central DCDB started central satellite DCDB updates started central satellite DCDB updates released new version of Rabbit (User Application), improving Rabbit DCDB connection thanks to problems in Heidelberg and GSI, now solved. released new version of Rabbit (User Application), improving Rabbit DCDB connection thanks to problems in Heidelberg and GSI, now solved. introduced ServoTech module (cable database) introduced ServoTech module (cable database) developing more powerful search and histograming capabilities developing more powerful search and histograming capabilities development of MCDF (Monitoring of Components and Data Flow) to be released soon. Inventory tool development of MCDF (Monitoring of Components and Data Flow) to be released soon. Inventory tool

5. ALICE ID An unique ALICE identifier is generated automatically by the DCDB when a new component is entered. An unique ALICE identifier is generated automatically by the DCDB when a new component is entered. tools for bar-code generation, printing and reading have been developed tools for bar-code generation, printing and reading have been developed type of bar-code reader to be defined (same as ATLAS) type of bar-code reader to be defined (same as ATLAS)

9. Lab A Lab CLab D Lab B Lab D MCDF problem description Problems Problems –Flow of components Components flow from one manufacturer or laboratory to another Components flow from one manufacturer or laboratory to another We should know present location of each component We should know present location of each component –To achieve this, we must enforce users to enter proper location information into the database immediately after the location changes –Data flow Component’s data is entered/modified in more than one place Component’s data is entered/modified in more than one place –When component flows from one lab to another, its data should usually also be transferred from one satellite database to another –The data of the same component must not be edited in more than one database at the same time

10. News from GSI New version of the database, DCS 1.30 installed using Oracle 9i (test setup, as GSI is moving to Oracle 10) New version of the database, DCS 1.30 installed using Oracle 9i (test setup, as GSI is moving to Oracle 10) Initial problems of lack of space solved, 70 GB available Initial problems of lack of space solved, 70 GB available Corresponding versions of Rabbit and Labserver being updated by Kilian and Warsaw Corresponding versions of Rabbit and Labserver being updated by Kilian and Warsaw

11. News from the TPC OROC and IROC test data compiled by Chilo has been downloaded to the central DCDB at CERN: OROC and IROC test data compiled by Chilo has been downloaded to the central DCDB at CERN: http://dcdb.appll.cern.ch:8080/rabbit http://dcdb.appll.cern.ch:8080/rabbithttp://dcdb.appll.cern.ch:8080/rabbithttp://dcdb.appll.cern.ch:8080/rabbit login: guest passwd:guest login: guest passwd:guest some screen shots follow some screen shots follow

12. TPC dictionaries

15. TPC ROC data in the DCDB

16. OROC data imported in DCDB

17. OROC02 test measurements

18. Chamber gain

19. Long Term Test

20. Pulse height spectrum taken every 15 min

22. Next for TPC Complete and certify IROC and OROC data Complete and certify IROC and OROC data FEC testing will go to the DCDB, Rainer will use the developments of the TRD ROC testing at Heidelberg (LabView -> DCDB) FEC testing will go to the DCDB, Rainer will use the developments of the TRD ROC testing at Heidelberg (LabView -> DCDB) RCUs and back-boards, Luciano will provide list of parameters to store and I will set up the database for it. RCUs and back-boards, Luciano will provide list of parameters to store and I will set up the database for it.

23. Status of the ALICE Physics Data Challenge 2004 Currently running Phase 1: Currently running Phase 1: –Reminder – production of underlying Pb+Pb MC events using Hijing –20,000 events generated for 5 impact parameter bins each In ~10 days will start with Phase 2: In ~10 days will start with Phase 2: –Reminder – mixing of the underlying events with physics signal events and their reconstruction Jets with and without quenching Jets with and without quenching hadronic Ds hadronic Ds semi-electronic Ds, Bs and electronic J/Psi and Upsilons semi-electronic Ds, Bs and electronic J/Psi and Upsilons single muons and di-muons from Coctail single muons and di-muons from Coctail afterwards Phase 3: afterwards Phase 3: –Remainder- physics analysis

24. ~40K jobs executed at 12 major and 6 other production sites (including Itaniums) ~40K jobs executed at 12 major and 6 other production sites (including Itaniums) ~25 TB of data transferred to CERN (CASTOR) ~25 TB of data transferred to CERN (CASTOR) ~ 1 million files ~ 1 million files Current production statistics