Transcript CCS configuration and conditions databse - Indico

CCS database requirements
Evgueni Vlasov, CERN (ITEP, Moscow)
CCS has 2 big different tasks and as consequently
2 different types of databases:
Calibration
Condition
database for configuration of FE,
database for slow control values.
Configuration(Construction?) database will be
used also to define to which crate/slot number
connected given supermodule.
The correspondence tower - CCU number should
be placed somewhere in construction or
configuration database.
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Evgueni Vlasov
1
Construction/ Configuration data
base
The proposal is to use the “physical” addresses for
addressing to calibration data (Supermodule->Tower>Xtal) and not a “electronic” (slot number->ring
number -> CCU number ->…). The transformation to
“logical” addresses can be done easily in CCS
supervisor.
What we need for that is only (Supermodule –
crate/slot) correspondence and (Tower – CCU number)
correspondence. The rest of the addresses are fixed and
can be translated to “electronic” addresses without
using the data base.
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Evgueni Vlasov
2
Calibration data base
This is not a big database.
We have about 1Mbyte calibration coefficients for
barrel at each time. Even we will change all the set of
parameters 3 times per day, about 1Tbyte of data will
be collected during the 1 year of running of LHC.
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Evgueni Vlasov
3
Calibration data base
Organization of tables:
It is clear that using of “device” (chip) as
elementary structure is not a good idea from point
of view of communication with FE (the slowest
possible speed).
It will be more convenient to have the set of the same
parameter as elementary structure (raw of table).
As example all the offsets for one tower (75 values) in
one elementary structure. The most flexible is to have
such structure for 1 Xtal, but it can be too expensive.
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Evgueni Vlasov
4
Conditional data base
Parameter board per tower per SM Tot ECAL barrel Frequency
---------------------------------------------------------------------------------------------------Low voltage LVR
11?
748
26928
5mins
Temperature LVR
3
204
7344
5mins
Temperature VFE
5
340
12240
5mins
Leak. curr.
VFE
25
1700
61200
10mins
Temperature FEC
2
72
5mins
----------------------------------------------------------------------------------------------------Total
44
2994
107784
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Evgueni Vlasov
5
What we need to process this data:
1) To mask bad channels
2) To scale values (calibration coefficients)
3) To do some actions if value is out of limits
4) To store data into the database
Obviously, this is functions of DCS…
The question is: how to proceed this amount of data.
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Evgueni Vlasov
6
Possible structure:
DCS computer
Local DCS
(9000
parameters)
DAQ Linux
Computer 1
Local DCS
(9000
parameters)
DAQ Linux
Computer 2
ECAL OFF-detector Electronics Workshop April 7, Lisbon
Local DCS
(9000
parameters)
DAQ Linux
Computer 2
Evgueni Vlasov
…..
7