Configuration Database

1
Configuration Database

• Lana Abadie,
• LHCb week, May 25

2
The configuration database

• Storage of all controllable devices with
• their properties
• the links between them
• their hierarchy
• The control system can be bootstrapped from the
  configuration database.

3

• DB Design Methodology (ex the TFC system)
• TFC dataflow

4
X 16
used 1
TFC DATAFLOW
Throttle set of links TFC set of links DAQ set of
links TFC set of links sometimes possible
ODIN_X Readout s.
THOR_00 (TFC) 1616
TTCtx_X transmitter(1614)
X16
TTCocX_Y Opt. couplers(132)
Y14
TTCrxX_Y receiver (132)
TTCrxX_Y_W receiver (132)
W32
Zlt16
SubDet_L0FEX_Y_Z (?1)
X16
Munin0_X 322
SubDet_L1FEX_Y_Z (?5)
DAQ (readout net)
MuninL0_00 1616
MuninL1_00 1616
SubDet can be (VELO, RICH, L0MUON,...)
5

• DB Design Methodology (ex the TFC system)
• TFC dataflow
• TFC system use cases

6
TFC system use cases

• List of possible scenarios (2 examples)
• Find all the connection paths between 2 devices
• Define the routing table of the TFC switch

7
Path concept
T HOR_00

• Example I want to know all the possible
• paths from VELO_L0FE00_00_00 to TFC switch
• (THOR)

0
TTCtx_00
Path (VELO_L0FE00_00_00,0), (TTCrx00_00_00,
0), TFC ? 1st link (TTCrx00_00_00,0) ,
(TTCoc00_00,0),TFC ? 2nd link (TTCoc00_00,0),(TT
Ctx_00,0),TFC ?3rd link (TTCtx_00,0),(THOR_00,0)
?4th link
TTCoc00_00
0
0
0
TTCrx00_00_00
TTCrx00_00_11
0
0
0
VELO_L0FE00_00_00
0
TFC link
8
T HOR_00
TTCtx_00
TTCoc00_00
TTCrx00_00_00
System_L0FE00_00_00
0
System_L0FE00_00_01
9
TFC switch routing table

• Identified by a number
• The way it is stored in the database (cf schema
  below)
• input nbr 5
• output 0 0 0 1 0 0 0 1 0 0 0 0 0 0 1 0

THOR switch
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
connection busy
10

• DB Design Methodology (ex the TFC system)
• TFC dataflow
• TFC system use cases
• Entity relation model Table design

11
Entity relation model
Thor Routing RoutingId switch name Output
word Input nbr
Device Device Name Device type Active
1
N
Table design
Device Device Name (pk) Device type (fk) ref
SwitchType(Switch_type) active
Thor Routing RoutingId (pk) switch_name(fk)
references device_list(devname) Output_ptnb
Inp_ptnb unique(RoutingId, output_port_nb)
1
N
12

• DB Design Methodology (ex the TFC System)
• TFC dataflow
• TFC system use cases
• Entity relation model Table design
• Conf.DB PVSS (Framework)
• Structure of the Conf.DB

13
Structure of the Conf.DB
PVSS System
PVSS Libraires Tools
Conf. DB
PART OF THE FRAMEWORK
fw_recipes
fw_device
fw_com ponents
fw_device_ properties
fw_recipes _properties
PL/SQL scripts
DIM SERVER
device
tfc_path
14

• DB Design Methodology (ex the TFC System)
• TFC dataflow
• TFC system use cases
• Entity relation model Table design
• Conf.DB PVSS
• Structure of the Conf.DB
• Presentation of the demo

15
Presentation of the demo (1/2)
Readout Supervisor 1
TFC Switch
WILL BE SIMULATED BY A TEST BOARD (freja)
VELO FE
ST FE
OT FE
16
Presentation of the demo (2/2)

• Connection to the hardware (from the TFC system)
  via PVSS
• Creation of the different devices (TFC switch,
  read out supervisor...) in PVSS and storage in
  the fw_ tables
• Insert in other tables the different
  connectivities between devices
• Queries to the tables (tfc_path) to get the
  connectivities between the TFC switch and the
  subsystems.
• Links to other existing panels to configure the
  different components with possibile storage in
  the fw_ tables under different versions
• Make the updates in the other tables

17

• DB Design Methodology (ex the TFC system)
• TFC dataflow
• TFC system use cases
• Entity relation model Table design
• Conf.DB PVSS
• Structure of the Conf.DB
• Presentation of the DEMO
• Conclusion

18
Conclusion

• Design of TFC and Read Out Network system tables
  completed
• First prototype built to show possible queries to
  the Conf.DB via PVSS
• Future work
• Design of other subsystem tables (connectivities)
• Optimization of performance
• Design of a generic API

19

• Thank you for your attention
• QUESTIONS ?

20
Extract of the fw_device_properties
How the datapoint called TFCOdin/ODIN_00 is
stored in the Conf.DB ?
One attribute and its value per line are stored