1 / 26

Configuration Database tutorial

Configuration Database tutorial. Lana Abadie September 21 st 2005. Insert configuration data into the DB Retrieving data from the DB at starting Saving data at the end of a run (better value ). The Conf DB (reminder). LHCb specific Connectivity. JCOP

asis
Download Presentation

Configuration Database tutorial

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Configuration Databasetutorial Lana Abadie September 21st 2005

  2. Insert configuration data into the DB Retrieving data from the DB at starting Saving data at the end of a run (better value ) The Conf DB (reminder) • LHCb specific • Connectivity JCOP - Configuration of devices for a particular running mode - Common to the 4 experiments

  3. JCOP tool / LHCb specific tool A run is characterized by : • An activity or mode (physics, alignment, cosmics) • A partition (part of detector which can run independently and concurrently) LHCb specific tool: What devices are involved in the partition? How to access them from the DAQ, ECS and TFC? JCOP tool: What settings to load into my devices for the selected activity such as physics, cosmics ?

  4. EX: calibration run for VELO (JCOP tool) TFC calibration run VELO subsystem calibration run VELO FEs DAQ Farm ECS PVSS Load parameter values to configure VELO devices, Farm nodes and TFC devices for a calibration run

  5. EX: calibration run for VELOLHCb tool TFC VELO subsystem Calibration run VELO FEs DAQ ECS PVSS Which devices are involved in the partition? Here VELO Get connectivity between the VELO and TFC to send the clock. Get connectivity between VELO and DAQ to configure the network (data path)

  6. JCOP tool

  7. Recipe concept • Recipe : device configuration. Snapshot of a set of DPEs (parameters) and their values which change with the running mode. • The parameters which are read back from devices can’t be part of a recipe

  8. Views • Hardware View : a module in terms of devices. Ex: a CAEN is composed of crateswhich have a certain number of boards and each board has a certain number of channels • Logical view: your system in term of logical nodes. Ex: OT has 4 stations which are divided in 10 sectors each • FSM View : your system in terms of monitoring Ex: PC 1 monitors the Muon station 1 and 2…

  9. JCOP Tools Features : • Save and load recipes for a set of devices (hierarchy) into/from the confDB (available end of this month) • Save and load a recipe for a device type into/from the confDB (available end of this month) • Save and load the logical, hardware and FSM views into/from the confDB ( FSM and logical not implemented yet ) • Recipe cache : possibility to work without connecting to the confDB (see next slide)

  10. Recipe cache JCOP tool provides a recipe cache: • You can save, edit and load recipes locally without using a DB. Useful for • Testing devices configuration: if your recipe is correct or not • Preparing the configuration of your devices for the next running mode . • Once you are satisfied with your recipes, save it into the DB.

  11. JCOP Tool : in practice • Install PVSS and the Framework component (provided by JCOP) • Use the Device & Editor Navigator provided by the Framework to design your hardware and logical views: • Prepare your recipe • What are the devices which need to be saved ? (part of the same recipe) • What are the device parameters which really depend on the configuration mode? • Give an explicit and meaningful tag and related to the running mode (Easier for you to retrieve)

  12. JCOP Tool : in practice

  13. PVSS courses provided by the JCOP group to learn PVSS Future : tutorial on how to use the JCOP ConfDB tool JCOP courses

  14. LHCb specific part

  15. Connectivity • Description of the physical links between devices on its output and its input using the system dataflow • Useful to determine • Exactly the data path • Destination/routing tables • Config files (e.g. DHCP) • What devices need to be configured given a partition • How to interconnect all the subsystems with TFC, ECS and DAQ

  16. Save the connectivity We store the connectivity for each subsystem: • between the FE boards and the TFC • between the FE boards and the DAQ • between the FE boards and the ECS The FEs names should be the same for the whole System (link between JCOP and LHCb part) To save your own connectivity within your subsystem, use the ConfDBAPI library (we can help you)

  17. Database tools Implementation details : see here for more details • Using the PVSSand the confDBAPIlibrary: • Using CDBVis (python tool) • Building your own application using the confDBAPI library (C,C++ and python) Basic steps (order to respect): • Connect to the database. • Insert all the device types used in the connectivity of your system • Insert all the devices used in the connectivity of your system • Insert all the link types used in your system • Insert all the links

  18. Using the confDBAPIlibrary with PVSS • install the Instant Oracle client (see the instructions) • Get the confDBAPI library for PVSS and save it in the bin folder of your PVSS project. • In your config file, add CtrlDLL = “PVSSConfDBAPI.dll“ after [ui] and after [ctrl]. • For a simple panel with sample script, see doc on the web

  19. Tell 1 Repeater board ARX long kapton tail long kapton tail long kapton tail Analogue repeaters 1 ARX Analogue repeaters 2 Short kapton tail ARX 3 Analogue repeaters 1 4 Analogue repeaters ARX 2 3 Low voltage regulators 4 A sensor List of device types : beetle, sensor, analogue repeaters, ARX List of devices : beetle_01,…,sensor_01,… List of link types : data signal, (voltage signal,…) A beetle Data signal ARX Analog receiver

  20. Tell 1 Repeater board ARX long kapton tail Analogue repeaters 1 ARX Analogue repeaters 2 Short kapton tail ARX 3 Analogue repeaters 1 4 Analogue repeaters ARX 2 3 Low voltage regulators 4 A sensor List of links: (sensor01,analogue_repeater_board01,1,1,Data) …. A beetle Data signal ARX Analog receiver

  21. CDbVis (not released yet by Thomas Johansen) • Python tool (work under Linux and Windows) • Nice view of the content of the database • Check consistency (error when inserting connectivity between devices) • Not all the features are implemented yet: • You can view the connectivity and get some information about the devices • But you can’t insert anything

  22. Visualization Tool SELECTION VISUALIZATION INFORMATION

  23. Component View TFC Switch Transmitter (opt) Coupler (opt)

  24. JCOP part : conclusion • JCOP ConfDB framework : ready to use by the end of this month • Possibility to save and load recipes in/from DB and recipe cache for one or a set of devices. • Play with it • If any problem contact us

  25. LHCb specific part: conclusions • Prototype exists and ready to use • Try using the confDBAPI with PVSS • Need to finish the implementation of CDBVis • Need to implement update functions for the ConfDBAPI library • If you need information which can’t be get using the given function, tell us

  26. Next steps for the subsystem • Get familiar with PVSS and framework tools. • Prepare your views (hardware, logical and FSM) • Use the recipe cache to save, load and test your recipes. Then using the database: • Save your recipes in the database

More Related