Online Databases

1
Online Databases

• _at_ Commissioning

2
Online Databases

• We will provide Interfaces to the three main
  Logical Databases in the Online System

Conf.
DB
...
...
PVSS
PVSS
PVSS
PVSS
PVSS
Arch.
PVSS
PVSS
PVSS
PVSS
...
...
.
.
Cond.
To Offline
To Offline
DB
3
Dataflow Example
Conf.
DB
Configuration settingsfor a running mode
if Needed for next run settings(Pedestal
Followers)
PVSS
Experimental Equipment
PVSS
PVSS
Arch.
Monitoring data(at regular intervals)
if Archive On
if Passes Conditions filter
.
.
Cond.
To Offline
To Offline
DB
4
Online Database Contents

• Configuration DB contains
• All data needed to configure the HW (or SW) for
  the various running modes
• Ex. HV V0 Settings, Pedestal settings, trigger
  settings, etc.
• PVSS Archive contains
• All monitoring data read from HW for monitoring
  and debugging of the Online System
• Ex. HV Vmon Readings, temperatures, pedestal
  readings, etc.
• Conditions DB contains
• A subset of the monitoring data read from HW if
  it is needed for Event processing (prob. packaged
  differently)
• Ex. HV Vmon Readings if changed by more than n
  Volts
• Some configuration data once it has been used
• Ex. Trigger settings used by a particular run

5
Configuration DB Function

• All Online Components need to be configured
• All Electronics Boards
• Register settings, look-up tables, pedestals,
  constants, etc
• HV, LV Power Supplies
• Voltage settings, alarm limits, etc.
• Trigger Algorithms
• Job options, cuts, etc.
• Etc.
• According to
• Partitioning mode
• Which components
• Affects is particular the TFC and the central DAQ
• Running mode (Physics, Cosmics, Test, etc.) /
  Version
• What data
• The Conf DB will allows us to store/retrieve this
  info

6
The Configuration DB

• The Configuration DB will contain
• All "static" information about the devices(in
  particular for partitioning)
• Connectivity, addresses, etc. (also inventory and
  history)
• Developed within LHCb (supports queries)
• All "dynamic" data needed by the devices (for
  different running modes and different versions)
• Settings (voltages, alarm limits, etc.),
  Calibration constants, Pedestals, FPGA code
  (probably a pointer to it), etc.
• The settings for a particular running mode are
  called a Recipe (partial recipes available)
• The JCOP FW component implements a cache
• Can be used without Oracle for tests
• Can pre-load several recipes before Start of Run

7
Online DB Access

• Configuration DB
• Connectivity
• Filled by us (with help) for central equipment
  (from L0 elect. down)
• Rest filled by sub-detectors (not needed for SD
  configuration)
• PVSS panels or scripts for queries/answers
• And a specialized Graphic visualization/insertion
  tool
• Recipies
• PVSS/FW panels and scripts to save/retrieve data
• Conditions DB (interface to be developed)
• PVSS/FW panel to select
• Which data
• When should it be sent (on change, regular
  intervals, etc.)
• How should it be packaged
• Archive
• PVSS/FW panel to select data (smoothing
  possible)

8
Sub-detector tasks

• All devices (including electronics boards)
• Have to be modeled in PVSS according to
  guidelines (ex. registers have to correspond to
  datapoints) in order to
• Provide access to the Conf. DB
• Select a device/group of devices and saySave as
  Physics recipe.
• Be able to archive the data
• Be able to send the data to the Cond. DB
• Generate alarms, etc.
• We will provide a tool for automatically
  downloading and applying recipes (FSM driven)