Transcript Use of the DCDB by the TPC and TRD

DCDB
A. Sandoval
TPC meeting, Tanka Village 16 May 2004
Contents
• News from the DCDB team in Warsaw
• News from the GSI DCDB
• News from the TPC use of the DCDB
• News from ALICE Physics Data Challenge
the DCDB components
User
User
Web
Web
Dictionary
Wizard
User
Web
Web
Rabbit
(DMS server)
User
Web
Test Setup
With LabView
Heidelberg
LabView
Server
SQL
Heidelberg
Frankfurt
GSI
Satellite
DCDB
Warsaw
Satellite
DCDB
GSI
News from Warsaw
• new database version released v1.30, done to include the
•
•
•
•
•
•
•
ALICE ID and improve functionality
moved all satellite DCDB to v1.30
created central DCDB
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.
introduced ServoTech module (cable database)
developing more powerful search and histograming
capabilities
development of MCDF (Monitoring of Components and Data
Flow) to be released soon. Inventory tool
ALICE ID
• 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
type of bar-code reader to be defined (same as
ATLAS)
MCDF problem description
• Problems
– Flow of components
• Components flow from one
•
manufacturer or laboratory to another
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
Lab A
Lab B
Lab D
– Data flow
• 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
Lab C
Lab D
News from GSI
• 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
• Corresponding versions of Rabbit and
Labserver being updated by Kilian and
Warsaw
News from the TPC
• OROC and IROC test data compiled by
Chilo has been downloaded to the central
DCDB at CERN:
http://dcdb.appll.cern.ch:8080/rabbit
login: guest
passwd:guest
• some screen shots follow
TPC dictionaries
TPC dictionaries
TPC dictionaries
TPC ROC data in the DCDB
OROC data imported in DCDB
OROC02 test measurements
Chamber gain
Long Term Test
Pulse height spectrum taken every
15 min
Next for TPC
• 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)
• RCUs and back-boards, Luciano will
provide list of parameters to store and I
will set up the database for it.
Status of the ALICE Physics Data
Challenge 2004
• 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:
– Reminder – mixing of the underlying events with physics
signal events and their reconstruction
•
•
•
•
Jets with and without quenching
hadronic Ds
semi-electronic Ds, Bs and electronic J/Psi and Upsilons
single muons and di-muons from Coctail
• afterwards Phase 3:
– Remainder- physics analysis
Current production statistics
• ~40K jobs executed at 12 major and 6 other
•
•
production sites (including Itaniums)
~25 TB of data transferred to CERN (CASTOR)
~ 1 million files