1 / 14

LHCb Online

LHCb Online. & the Conditions DB. LHCb Online. DCS Devices (HV, LV, GAS, Temperatures, etc.). Detector Channels. Trigger. Front End Electronics. Experiment Control System. Readout Network. Processing/Filtering Farm. Storage. DAQ. External Systems(LHC,Technical Services,Safety,etc).

kin
Download Presentation

LHCb Online

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. LHCb Online & the Conditions DB

  2. LHCb Online DCS Devices (HV, LV, GAS, Temperatures, etc.) Detector Channels Trigger Front End Electronics Experiment Control System Readout Network Processing/Filtering Farm Storage DAQ External Systems(LHC,Technical Services,Safety,etc)

  3. Online Usage of CondDB • Two completely independent users: • As Publisher • The Experiment Control SystemWrites Online Conditions to the DB • As Consumer • The Event Filter Farm AlgorithmsNeed Conditions for their processing/filtering tasks

  4. Online Conditions Sources • DCS • High Voltages, temperatures, pressures, etc. • DAQ & L0 Trigger • Pedestals, thresholds, zero suppression parameters, gains, etc. • DAQ & Trigger setup parameters • EFF (Event Filter Farm) • Pedestals, Thresholds, Gain Calibration, Alignment Constants, etc. • Trigger setup parameters • External Systems • Accelerator data: energy, luminosity, average bunch currents, etc.

  5. Online Conditions Publisher • From the Control System point of view: • Only output • Only one interface: • from the ECS i.e. PVSS • Clients (offline algorithms) determine: • Data organization • Data format: XML (?) • Data update rate • Data could be stored in the Cond DB only if it changed by more than X or every hour • independently of the PVSS read-out rate.

  6. Conditions Data Types • Raw DataValues read directly from hardware (ex.: HV readings, Temperatures, raw alignment data, etc.) • No Versions, no Tags • Processed DataResults of calculations done on raw data (ex.: calibration constants, alignment, etc.) • Automatic Versioning, User Tags • All Online data stored as "Raw Data"

  7. Experimental Equipment Data Handling Architecture • Three Logical Databasesin the Online System Conf. DB ... ... PVSS PVSS PVSS PVSS PVSS Arch. PVSS PVSS PVSS PVSS ... ... . . Cond. To Offline To Offline DB

  8. 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, pedestal readings, etc. • Conditions DB contains: • A subset of the monitoring data read from HW if it is needed for Offline processing • 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

  9. 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

  10. ECS CondDB Architecture • Define filters in PVSS:(per device type/device) • Archive • Condition: • filter expressions • Uses LCG: • COOL • RAL • SEAL • POOL • BOOST • etc. … Control PCPVSS Control PCPVSS Control PCPVSS ~100 ConditionsData Cond. DBServer Cond. DBServer . . Cond. DB

  11. Event Builder Switch SFC SFC SFC CPU CPU CPU . . . CPU CPU CPU . . . . . . . . . CPU CPU CPU Event Filter Farm & CondDB • CPUs run "Offline" Algorithms Online: • Within Gaudi FW(interfaced to PVSS) • Need Conditions: • The Control PCs will get a snapshot of the CondDB (at Start of Run) and distribute to CPUs • A few well-chosen Conditions can be updated while running

  12. CPU CPU CPU CPU CPU CPU CPU CPU CPU Dataflow Example Event Builder Switch Control PCPVSS Control PCPVSS SFC SFC SFC • Special filter for some conditions • Trigger Farm Update CPU CPU CPU . . . CPU CPU CPU t0 . . . . . . . . . Cond. DBServer Cond. DBServer CPU CPU CPU Validity Start = t0+Dt Control PCPVSS Control PCPVSS . . Cond. DB New Condition Update (t0+Dt) At Run Start

  13. Event Builder Switch SFC SFC SFC CPU CPU CPU CPU CPU CPU . . . CPU CPU CPU CPU CPU CPU . . . . . . . . . CPU CPU CPU CPU CPU CPU Control PCPVSS Control PCPVSS Ex: The VeLo Alignment Control PCPVSS Control PCPVSS Cond. DBServer Cond. DBServer Control PCPVSS . . Cond. DB

  14. Online/Offline Synch Offline Cond DB Online Cond DB RichAl RichAlOn VeloAl VeloAlOn RichAlOn RichAl VeloAlOn VeloAl • Synchronized by Oracle Tools

More Related