160 likes | 294 Vues
This document outlines the design and implementation of the LHCb configuration database, which is essential for managing and controlling experimental systems at CERN. The database facilitates the storage and retrieval of information regarding devices, their properties, interconnections, and hierarchical relationships. Key objectives include improving equipment configuration, monitoring, and the overall operation of LHCb experiments. Utilizing technologies like Oracle and Python, this system implements effective database management practices and integrates tools from the Joint Control Project (JCOP) to ensure seamless operation across different components.
E N D
LHCb Online Configuration Database Lana Abadie, CERN PhD student from University Pierre & Marie Curie (Paris VI) , Laboratoire SAMOVAR CHEP04, Interlaken
System overview Operator Experiment Control System (ECS) LHCb configuration database PVSS (SCADA) Experimental Equipment
Objectives & requirements • Store information about all controllable devices • their properties • the links between them • their hierarchy • Keep necessary information for the ECS • to configure equipment • to operate the experiment • to monitor the system • Database design key issues • schema • completeness • performance • maintenance
Timing & Fast Control (TFC) dataflow Information from the schema List of devices Connectivities between devices
Use cases • Collect use cases : Given a VELO card, find a free readout supervisor and determine the routing table of the TFC switch • List the keywords : device type, device, link, path... • Define them: a link is a cable between a device output number and a device input number • Find connections between keywords: a path is a sequence of links
Entity relationship model • Find the type of relation between tables Link +LinkID +Switch Name From +Port Number From +Switch Name To +Port Number To +Type of link Device Type +device type name +nbr of input port +nbr of output port +device description Path +PathID +Link Device +Device Name +Device type +Status 2 1 • Convert them into constraints Link +Switch_LinkID (pk) +Switch_From +Port_nbr_from +Switch_to +Port_nbr_to +link_type (fk) ref Link Type(link nbr) + bidirectional_used + Unique(Switch_From, port_nbr_from) + Unique(Switch_to, port_nbr_to) + Switch_From, Port_nbr_from (fk) ref Port(switch name,nbr,in_or_out=‘out’) + Switch_to, Port_nbr_to (fk) ref Port(switch name,nbr,in_or_out=‘in’) Device +Device Name (pk) +Device type (fk) ref. Device type(devtype) +Status Device Type +devtype name (pk) +nbr of input ports +nbr of output ports +device description Path + PathID (pk) +link1 +link2… only fixed paths
Implementation features • Use of Oracle technology • Use of ProC/C++ to access the database and C/C++ to encapsulate the SQL and PL/SQL statements to communicate with PVSS • Use of JCOP configuration database tool • Implementation of a tool (cdbVis) to edit and navigate through the database in Python • Use of CVS to keep versions of projects and softwares
Integration of theJCOP configuration database tool • Joint Control Project: offers common tools and framework for PVSS • Ensure compatibility between JCOP tables and LHCb tables • Avoiding redundancy in the tables: • JCOP tables contain device properties • LHCb tables store connectivity and hierarchy information • Adaptation of JCOP configuration database panels
Communication : PVSSSystem PVSS Libraires & Tools provided by JCOP Configuration DB fw_recipes fw_device fw_com ponents fw_device_ properties fw_recipes _properties PL/SQL scripts device LHCb tables tfc_path
Navigator editor tool : cdbVis Display the connectivities of a selected device on its inputs and outputs View of a path from the readout supervisor to the Throttle
Ex. of concrete implementation : TFC system
Physics trigger Local trigger (Optional) L0 / L1 L0 / L1 L0 / L1 Clock Clock Clock Clock Readout Supervisor 0 Throttle Switch TFC Switch Readout Supervisor 1 Readout Supervisor 3 Readout Supervisor 2 VELO FE ST FE OT FE RICH FE ECAL FE . . . TFC requirements • select subdetectors and • an activity • get the connectivities • between subdetectors and • TFC switch Readout Supervisor 1 List of activities Physics • List of free readout supervisors • and allocate one TFC Switch • save/load activities into/from • the conf. DB VELO FE ST FE OT FE
Conclusion • Design schema for TFC and DAQ tables completed • Production TFC control system (PVSS) now uses the configuration database Future work • Table Design for LHCb other subdetectors • Extension of the cdbVis functionalities • Design an API to enable clients to interact with the database