1 hlt – ecs, dcs and daq interfaces sebastian bablok uib
Post on 21-Dec-2015
223 views
TRANSCRIPT
1
HLT – ECS, DCS and DAQ interfaces
Sebastian Bablok
UiB
Control of HLT by the Experiment Control System (ECS) for
initialisation and runtime operations
Interface:represented as well defined states and transitions
managed by Finite State Machines (FSM)
ECS controls the HLT via HLT proxy
implemented in SMI++ (external communication via DIM)
internal communication is using interface library of TaskManager control system
HLT - ECS Interface
HLT - ECS Interface
HLT proxy states and transitions:subdivided into two type of states
“stable” states (OFF, INITIALIZED, CONFIGURED, READY, RUNNING, ERROR): transitions only via well defined commands
intermediate states (RAMPING_UP_&_INITIALIZING, CONFIGURING, ENGAGING, DISENGAGING, RAMPING_DOWN):
longer procedure of transition – implicit transition, when procedure is finished
Implementation:SMI++ (common among all ALICE systems)
single instance
not partitioned
HLT proxy is only active during (de-) initialisation- and configuration phase, in RUNNING state the cluster processes event data autonomously
internal communication: interface library of TaskManager (TM) control systemHLT proxy contacts to multiple master TMs of the cluster (majority vote – fault tolerance, avoiding single-point-of-failure)
master TMs are networked with all slave TMs
slave TMs control the PubSub system (RORC publisher and others)
HLT proxy - States
ERROR OFF
RAMPING_UP_&_INITIALIZING<< intermediate state>>
RAMPING_DOWN<< intermediate state>>
INITIALIZED
CONFIGURED
READY
RUNNINGRUNNING
CONFIGURING<< intermediate state>>
ENGAGING<< intermediate state>>
DISENGAGING<< intermediate state>>
initialize
implicit transtion
shutdownreset
shutdown
configure
reset
engage
disengage
start
stop
implicit transtion
implicit transtion
implicit transtion
implicit transtion
HLT proxy states
6
Status
• HLT proxy implemented
• Communication with ECS tested
• Communication with TaskManager implemented but not yet tested
7
HLT- DCS interface
• HLT is a consumer and a producer of data to be provided/archived by DCS
HLT & Databases
• The HLT will have contact to different databases, which are for different purposes as well as under different administration.
• For now, it is foreseen to have contact to three different DBs:– Configuration
DB (DCS)
– PVSS archive (DCS) andCondition DB
– Calibration DB (Detector Specific)
9
HLT integration into DCS
• Online Calibration Modules (one per detector)
10
HLT- DCS data source model
11
HLT- DCS data flow
12
HLT - DCS interface
13
Status
• Conceptual design done
• Implementation will start this week in collaboration with the DCS group
14
HLT- DAQ interfaces
• Hardware interfaces– HRORC with DIU/SIU
– See hardware talks
• Software interfaces– Output data format
HLT- DAQ output data format
HLT – output to DAQ
DAQ handles HLT output like data
from any other detector
(except for the trigger decision)
Output data format:trigger decision:
list of DDLs to read (detector DDLs and HLT DDLs)
Event Summary Data (ESD) in case of an accept
candidate ID (ID from used trigger class)
preprocessed event data [optional]:(partially) reconstructed event
compressed raw data
preprocessed detector specific data (e.g. Photon Spectrometer pulse shape analysis)
Start-Of-Data (SOD) and End-Of-Data (EOD)
16
Status
• Implemented