120 likes | 250 Vues
This document outlines the efforts made and upcoming tasks related to the Data Acquisition (DAQ) and Event Control System (ECS) for the Time Projection Chamber (TPC) commissioning. We have made significant strides in equipment setup, transitioning between sectors, and coordinating with high-level trigger (HLT) systems. Key components such as the LTU proxy and HLT proxy are discussed, along with configurations, event control, and the importance of collaboration for successful test runs and data acquisition. Future plans include installing DATE V5.19 and enhancing interactions with real DCS and HLT proxies.
E N D
DAQ & ECS for TPC commissioning A few statements about what has been done and what is still in front of us F.Carena
DAQ Setup for TPC Commissioning —Sector1 — —Sector2 — lnxpool13 aldaqcon02 aldaqcon03 aldaqpc021 RCU RCU LTU TTCvi, TTCex 6x 6x PC (SLC4): operation PC (SLC4): operation PC: TPC monitoring SIU SIU TTC GbE Switch SXL2 404504407503508506 PX24/CR1 409408512517513509 PX24/CR2 HLT Farm 514 1x DRORC 6x DRORC 6x DRORC 1x DRORC DDG LDC LDC HLT-LDC GPN aldaqpc013 aldaqpc010 aldaqpc011 aldaqpc012 502 GbE Switch (HP) 100 MB/s (to be upgraded) GDCTDSM GDCTDSM Server: DAQ, ECS,MySQL, MOOD Server:SLC3,DHCP, DNS,… Gateway SLC 3.0.6Castor 2.1.0-2DATE 5.16 MySQL 5.0.21-1MOOD 5.0.0.1ECS 2.8 + aldaqpc002 aldaqpc001 /tds1 /tds1 aldaqds002 /mdlocal aldaqds001 pcald25 /local (160GB) TDS aldaqtds03 2x 1.4 TB RAID5+spare, XFS DAQ, ECS for TPC commissioning
Changing from one sector to another • Equipment Ids must be changed • Equipment Ids == data origin (i.e. from which sector) • Table of equipment Ids agreed (TPC, Offline, DAQ, HLT) DAQ, ECS for TPC commissioning
Working with HLT mode A+ • A+ • Data sent to HLT farm (splitters on and ‘forced’) • DAQ does not receive data from HLT (no HLT LDCs) DAQ, ECS for TPC commissioning
LTU-proxy • A component of the ECS/TRIGGER interface • A process running on the VME crate where the TPC trigger partition (LTU, TTCvi, TTCex) is located (lnxpool13) • Is configurable • Two run modes (BC and pulser/edge) • In BC mode allows the selection of the event frequency • SOD and EOD events can be enabled/disabled • Not a debugging tool • Does not offer all the feature of the ‘vmecrate ltu’ interactive program (A.Jusko) • Gives to the ECS the control of the LTU • Connected to the DAQ network (ethernet over fiber) • Under the ECS control, it allows the generation of sequences of events starting with a SOD event and ending with an EOD event DAQ, ECS for TPC commissioning
HLT-proxy • A component of the ECS/HLT interface • Will run on the HLT farm • For the time being we can use for test purposes a dummy version or (better) the HLT-proxy with TaskManager emulation provided by S.Bablok • The HLT-proxy with TaskManager emulation runs on the same machine as the Detector Control Agent DAQ, ECS for TPC commissioning
ECS: TPC Detector Control Agent • Controls standalone runs • Starts / stops DAQ and Trigger (LTU) • Dummy DCS for the time being • Detector always ready • Dummy HLT-proxy or HLT-pxoxy with taskManager emulator provided by S.Bablok • Receive the right sequence of commands • It is a good starting point for the required development DAQ, ECS for TPC commissioning
DCA: before starting a standalone run DAQ, ECS for TPC commissioning
Output messages from HLT-proxy DAQ, ECS for TPC commissioning
DCA: after a standalone run DAQ, ECS for TPC commissioning
To do • DAQ: • Installation of DATE V5.19 (Monday 10 July 2006) • Main difference TDSM (migration of files to CASTOR) • Probably the last version supported on SLC3 • ECS: • Interaction with a real DCS • Interaction with a real HLT-proxy • Implementation of various types of runs • Pedestal runs (in progress) • Implemented in ECS • Roland preparing the required scripts • To be tested this week • Datapath Test runs • Calibration Pulser runs • Physics runs • Require a close collaboration with Luciano, Uli, Roland, …. DAQ, ECS for TPC commissioning
Pedestal runs: ready for testing DAQ, ECS for TPC commissioning