DAQ & ECS for TPC commissioning

A few statements about what has been done and what is still in front of us

F.Carena

6 July 2006 DAQ, ECS for TPC commissioning 2

DAQ Setup for TPC Commissioning

TDS

LDC

GbE Switch (HP)

LDC6x DRORC 6x DRORC

PX24/CR2

PC (SLC4):operation

PC (SLC4):operation

HLT-LDC1x DRORC

PX24/CR1

RCUSIU

SXL2

GDCTDSM

Server:DAQ, ECS,

MySQL, MOODGateway

aldaqtds032x 1.4 TB RAID5+spare, XFS

aldaqcon02RCU

SIU6x 6x

DDG1x DRORC

Server:SLC3,DHCP,

DNS,…

pcald25/local (160GB)

aldaqds001

aldaqds002

/mdlocal

aldaqpc001

aldaqpc013

aldaqpc010

aldaqpc012aldaqpc011

SLC 3.0.6Castor 2.1.0-2DATE 5.16 MySQL 5.0.21-1MOOD 5.0.0.1ECS 2.8 +

100 MB/s (to be upgraded)

409408512517513509

404504407503508506

/tds1

514

PC:TPC monitoring

aldaqpc021

GDCTDSM

aldaqpc002

aldaqcon03

/tds

1

LTUTTCvi, TTCex

lnxpool13

TTC

GbE Switch

GPN

HLT Farm

— Sector1 —

— Sector2 —

6 July 2006 DAQ, ECS for TPC commissioning 3

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)

6 July 2006 DAQ, ECS for TPC commissioning 4

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)

6 July 2006 DAQ, ECS for TPC commissioning 5

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

6 July 2006 DAQ, ECS for TPC commissioning 6

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

6 July 2006 DAQ, ECS for TPC commissioning 7

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

6 July 2006 DAQ, ECS for TPC commissioning 8

DCA: before starting a standalone run

6 July 2006 DAQ, ECS for TPC commissioning 9

Output messages from HLT-proxy

6 July 2006 DAQ, ECS for TPC commissioning 10

DCA: after a standalone run

6 July 2006 DAQ, ECS for TPC commissioning 11

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, ….

6 July 2006 DAQ, ECS for TPC commissioning 12

Pedestal runs: ready for testing