1. Normal text - click to edit HLT – Interfaces (ECS, DCS, Offline) (Alice week – HLT workshop 06-03-2007) S. Bablok (IFT, University of Bergen)

2. Normal text - click to edit TOC HLT interfaces HLT  ECS HLT  DCS HLT  OFFLINE HLT calibration (Use Case) additional slides

3. Normal text - click to edit HLT interfaces ECS: –Controls the HLT via well defined states (SMI) –Provides general experiment settings (type of collision, run number, …) DCS: –Provides HLT with current Detector parameters (voltages, temperature, …)  Pendolino –Provides DCS processed data from HLT (TPC drift velocity, …)  FED portal (Front-End-Device portal) OFFLINE: –Interface to fetch data from the OCDB (OFFLINE  HLT) –Provides OFFLINE with calculated calibration data (HLT  OFFLINE)

4. Normal text - click to edit OFFLINE DCS Task Manager Archive DB PVSS FES MySQL DCS portal Shuttle Pendolino ECS- proxy Data flow in HLT spec Datasink (Subscriber) Pendolino-PubSub DIM- Subscriber PubSub intern extern DA HLT OFFLINE Storage OCDB (Conditions) ALiEn Taxi local Cache (HCDB) Taxi-HCDB ECS AliRoot CDB access Detector responsibility Framework components Interface

5. Normal text - click to edit HLT  ECS interface State transition commands from ECS –INITIALIZE, CONFIGURE(+PARAMS), ENAGE,START,… –Mapping to TaskManager states CONFIGURE parameters: –HLT_MODE: the mode, in which the HLT shall run (A, B or C) –BEAM_TYPE: (pp (proton-proton) or AA (heavy ion)) –RUN_NUMBER: the run number for the current run –DATA_FORMAT_VERSION: the expected output data format version –HLT_TRIGGER_CODE: ID defining the current HLT Trigger classes –CTP_TRIGGER_CLASS: the trigger classes in the Central Trigger Processor –HLT_IN_DDL_LIST: list of DDL cables on which the HLT can expect event data in the coming run. The structure will look like the following: :, :,... –HLT_OUT_DDL_LIST: list of DDLs, on which the HLT can send data to DAQ

6. Normal text - click to edit OFF INITIALIZING > DEINITIALIZING > INITIALIZED CONFIGURED READY RUNNING CONFIGURING > ENGAGING > DISENGAGING > INITIALIZE implicit transtion SHUTDOWN CONFIGURE + params RESET ENGANGE DISENGAGE START STOP implicit transtion COMPLETING implicit transtion slaves_dead / off INITIALIZING > DEINITIALIZING > processes_ dead local_ready ready running/busy CONFIGURING > ENGAGING > DISENGAGING > start_slaves implicit transtion kill_slaves start + params stop connect disconnect start_run stop_run implicit transtion COMPLETING implicit transtion

7. Normal text - click to edit HLT  DCS interface FED portal: –Dim Channels (Services published on the HLT side) –Implements partially the Fed Api –Subscriber component –PVSS panels on DCS side integrate data in DCS system Pendolino: –Contacts the DCS Amanda server –Fetches current running conditions –Publisher component –Three Pendolinos, each with a different frequency (fast, medium, slow)

8. Normal text - click to edit DCS HLT components to interface DCS Pendolino- PubSub (Data processor) Interface (PubSub -Pendolino [AliRoot]) Detector responsibility Framework components Interface Pendolino DCS portal (Dim Subscriber) Interface (PubSub –FED API [ DIM ]) FED API Archive DB PVSS

9. Normal text - click to edit HLT  DCS dataflow Purpose: –Storing of DCS related data in the DCS Archive DB (HLT-cluster monitoring [HLT]; TPC drift velocity, …. [detector specific]) HLT side: –One node providing a special PubSub framework component implementing (partly) the FED API (DCS portal node) DCS side: –Different PVSS panels: A dedicated panel for HLT cluster monitoring Integration of detector specific processed data in the PVSS panels of the according detector

10. Normal text - click to edit HLT  DCS dataflow Purpose: –Storing of DCS related data in the DCS Archive DB (HLT-cluster monitoring [HLT]; TPC drift velocity, …. [detector specific]) HLT Cluster has a dedicated DCS portal node –DCS portal acts as DIM server –DIM channels to detectors PVSS panels and HLT PVSS panels (DIM client) –implements a FedServer (DIM server) [partly] "ConfigureFeeCom" command channel (setting log level) Service channels (Single and Grouped service channels, Message channel, ACK channel) –all located in one DIM-DNS domain 2 DCS PCs for HLT PVSS panels –worker node: PVSS panels to receive the monitored cluster data this node will also connect to Pendolino (vice versa connection, see below) –operator node: PVSS to watch the data (counting room and outer world) HLT cluster intern data is transported via PubSub system

11. Normal text - click to edit HLT  DCS dataflow (Hardware + Software components) DIM-DNS domain DCS HLT - cluster HLT HLT-DCS portal TPC TRDHLT Pub-Sub connections The connections inside the cluster are based on the Pub- Sub framework.... 2 HLT- DCS Nodes (located in DCS counting room): - worker node: PVSS panels to receive the monitored data; - operator node: PVSS panels to watch the data (remotely: counting room and outer world) Services of one detector are offered in Single and/or Grouped Service channel and can be requested by the PVSS of the according detector via DIM. Common Detector – DCS integration (over PVSS) Online Calib.... Cluster monitoring FEDServer (Dim) FEDClient (PVSS) Ordinary detector DCS nodes, connecting to the HLT portal in addition to their normal tasks.

12. Normal text - click to edit DCS  HLT dataflow HLT needs DCS data (temperature, current configuration, …): Online analysis Calibration data processing The required data can be acquired from the DCS Archive DB: retrieval via AMANDA Pendolino request data in regular time intervals about three Pendolinos with different frequencies are foreseen (three different frequencies – requesting different type of data) HLT intern data is distributed via PubSub framework

13. Normal text - click to edit DCS  HLT dataflow (Hardware + Software components) DCS HLT - cluster HLT HLT-DCS portal HLT- wn Pub-Sub connections The connections inside the cluster are based on the Pub- Sub framework.... worker node (wn), where AMANDA server for HLT is running Request of data via AMANDA (PVSS DataManager) Archive AMANDA – Pendolinos Pendolino Request Data response

14. Normal text - click to edit DCS  HLT dataflow Pendolino details: Three different frequencies: –fast Pendolino: 10 sec - 1 min –normal Pendolino: 1 min - 5 min –slow Pendolino: over 5 min Response time: –~13000 values per second –e.g. If Pendolino needs data for N channels, for a period of X seconds and the channels change at a rate of Y Hz (with Y smaller than 1 Hz !), it will take: (N*X*Y) / 13000 seconds to read back the data. (given by Peter Chochula) Remark: –The requested values can be up to 2 min old. (This is the time, that can pass until the data is shifted from the DCS PVSS to the DCS Archive DB)

15. Normal text - click to edit DCS data  HLT Remarks: Amanda Pendolino can only be used to request data included in the DCS Archive DB Requests of values with higher frequency than ~0.1 Hz need a different connection requests only data from current run; older data can be requested from the OCDB (OFFLINE interface, see below) Requests for huge amount of data should be requested via the FES of DCS (additional portal, will be similar to OFFLINE FES)

16. Normal text - click to edit HLT  OFFLINE interface Taxi portal –Requests OCDB and caches content locally (HCDB) –Provides calibration objects to Detector Algorithms (DA) inside the HLT –HCDB accessible via AliRoot CDB access classes Shuttle portal –Provides calibration data to OFFLINE (OCDB) –Data exchanged via FileExchangeServer (FES,FXS) –Meta data stored in MySQL DB –Fetched by OFFLINE at end of the run

17. Normal text - click to edit HLT  OFFLINE interface Taxi portal: DA 1. Taxi0 HCDB0 portal-taxi0 DA_HCDB 1. Taxi1 HCDB1 portal-taxi1 ECS- proxy OCDB current run number triggers update ECS AliRoot CDB access classes DA AliRoot CDB access classes

18. Normal text - click to edit HLT  OFFLINE interface How to access data from HCDB: string hcdbURL = “ ”; string calibObj = “ ”; Int_t runNumber = ; AliCDBManager *man = AliCDBManager::Instance(); AliCDBStorage *hcdb = man->GetStorage(hcdbURL.c_str()); hcdb->QueryCDB(runNumber); Int_t latestVersion = hcdb->GetLatestVersion( calibObj.c_str(), runNumber); AliCDBEntry *calibObject = hcdb->Get(calibObj.c_str(), runNumber, latestVersion);... // and that’s it!! AliCDBEntry represents calibration objects

19. Normal text - click to edit OFFLINE HLT  OFFLINE interface Shuttle portal: OCDB DA FESMySQL portal-shuttle0 (Subscriber) Shuttle FES1MySQL1 portal-shuttle1 (Subscriber) DA

20. Normal text - click to edit HLT  OFFLINE interface Shuttle portal: Field nameDescriptionProviderType runthe run numberHLT (framework)INT detectorthe detector name HLT (DA = Detector Algorithm) CHAR(3) fileIdfile identifier HLT (DA (checked by framework) VARCHAR (128) DDLnumbersDDL numbers, where data is originated fromHLT (DA, framework?)CHAR(64) filePathFull path to access file on FESHLT (framework) VARCHAR (256) time_createdtimestamp, when file has been copied to FESHLT (framework)DOUBLE time_processedtimestamp, when OFFLINE has processed the fileOFFLINEDOUBLE time_deletedtimestamp, when HLT has deleted the file from FESHLT (framework)DOUBLE sizesize of fileHLT (framework)INT fileChecksumchecksum of fileHLT (framework)CHAR(64)

21. Normal text - click to edit Information on the web http://wiki.kip.uni-heidelberg.de/ti/HLT/index.php/ECS-interface http://wiki.kip.uni-heidelberg.de/ti/HLT/index.php/Specification-HLT2OFFLINE-interface http://wiki.kip.uni-heidelberg.de/ti/HLT/index.php/UseCase-Calibration-HLT http://wiki.kip.uni-heidelberg.de/ti/HLT/index.php/Data_path_from_DCS_to_the_HLT http://wiki.kip.uni-heidelberg.de/ti/HLT/index.php/Integrating_HLT_data_in_the_DCS_system http://aliceinfo.cern.ch/Offline/Activities/ConditionDB.html

22. Normal text - click to edit Additional slides

23. Normal text - click to edit OFFLINE DCS Shuttle Processed events Processed data Calibration data Control (run number, …) FEE Event data Processed calibration data HLT - Interfaces HLT cluster OCDB (Conditions) FEP DCS- portal DDL Taxi portal HLT- proxy OFFLINE- Shuttle ECS DAQ Pendolino PVSS Archive DB DCS values

24. Normal text - click to edit HLT condition dataflow / Use Case Framework for data exchange –Initial Settings (before Start-of-Run (SoR)) ECS  HLT (over SMI: run number, beam type, mode, etc) OFFLINE  HLT (run and experiment conditions from OCDB; local cache  HCDB) –During run (after SoR) DCS  HLT (current environment/condition values via Amanda Pendolino) HLT  DCS (processed data via DIM-PVSS; e.g. drift velocity) Processed data back to DAQ (also for certain period after End-of-Run) –After run (after End-of-Run (EoR)) HLT  OFFLINE (OFFLINE Shuttle requests data via MySQL DB and File Exchange Server (FES))

25. Normal text - click to edit Timing diagram ECS DAQ DCS HLT Pre-Proc SHUTTLE EoR SoR Init OFFLINE......................................

26. Normal text - click to edit HLT dataflow / Remarks Goal: framework components shall be independent of data –definition can be changed later without change of model design & framework implementation –usage of already proven technologies (AMANDA, PVSS, DIM, AliRoot, PubSub framework) Detectors / Detector algorithms can define the required data later on –BUT: they have to make sure, that their requested data is available in the connected systems (OCDB, DCS Archive, event data stream (from FEE)) –Limit their requests to the actual required amount of data (Performance)