New DAQ at H8

Speranza FalcianoINFN Rome

H8 Workshop 2-3 April 2001

Outline of the session

• S.Falciano (15’) Testbeam DAQ configuration and status of the hardware

• E.Pasqualucci, F.Petrucci(30’ + 10’)

Status of Readout and DAQ software

• S.Falciano (15’) View on the future : 2002 and beyond

Proposal to use DAQ-1 at H8

• Presented at the Muon SG during December 2000 Muon Week

• Document written by INFN groups and discussed with several people

• Recent investigation with DAQ-1 and TileCal groups to define a possible scenario (hardware, software and milestones) to have a system running for next summer (2nd half of July)

Experimental setup (1)

HodoTracker

BIL/BOS/... Tilted chambers

Endcap

TrackerFixed MDT test site

Experimental setup (2)

• Hodoscope : 6 strips, 10 cm each, 60 x 100 cm2 total size, 6x2x2 channels, CAMAC ADC and TDC

• Tracker ; 96 channels readout by KLOE TDC• Fixed chamber test site : hosts the MDT

chamber under test (e.g. BIL is 1 m x 2.6 m, 288 channels readout by CSM)

• 3 MDT tilted chambers to reproduce ATLAS layout

• Maybe a 2nd tracker installed among the tilted chambers

Summary of requirements• Readout the following detectors:

– A trigger hodoscope– One or two trackers– One MDT chamber (under test)– Three tilted chambers

• CAMAC and VME electronics• MDT ROD not yet final but near-end ROD only• Event size is about 100-1000 32-bit words• Trigger rate is 1-6 kHz• 200 events/spill with RD13

Preliminary considerations

• Verify that we can purchase or get on loan the required hardware to develop the system in due time :

– Share among the partecipating institutes a common budget for H8

– Profit of the hardware already purchased for TDAQ muon application and of what the CERN-DAQ group makes available to us for this exercise

• Verify there is sufficient manpower for software :

– Core group from INFN plus other volonteers and, of course, help from the DAQ-1 group

•

Process Configuration (Monitoring)

disk / NW

CORBO SLINK

IOM: TRGEBIFROB

Event Sampler

Run Control

Transaction Server

Dataflow GUI

LDAQUser Monitoring Task

Monitoring Factory

“Dataflow” PC“Online” PC

= Process

PCI based CORBO Trigger Module

• HW: microEnable + mezzanine: 4 NIM trigger inputs + 4 NIM busy outputs

• subset of VME CORBO functionality: event counting, busy logic & interrupts

• software:– library which is API compatible with VME CORBO library. Unified library.– a driver for handling CORBO PCI interrupts under Linux– test & diagnostic programs – see TN 161

• performance– interrupt handling: ~ 10 us on average but not “hard” realtime (Linux)

• applications– triggering of TRGEBIFROB on a PC, provide burst information

Jorgen PetersenEP/ATD

TRGEBIFROB (preliminary)• TRGEBIFROB on a PC. SLINK input. TRG input

emulated: L2R /ROI/L2A = 100/10/1. No output.• Non-optimised application

TRGEBIFROB on a PC, TRG emulated+SLINK, no output

0

5

10

15

20

25

30

35

0 500 1000 1500 2000 2500

event size (bytes)

time

/ eve

nt (u

s)

Overhead = 10 us,Slope = 109 Mbyte/s,

Event Rate@1kbyte = 51 kHz

Jorgen PetersenEP/ATD

TRGEBIFROB (preliminary)• TRGEBIFROB on a PC. CORBO + SLINK input. 100%

accepts. No output. Application not optimised. • Controlled via LDAQ + Dataflow GUI.

TRGEBIFROB on a PC, TRG CORBO+SLINK, no output

05

1015202530354045

0 500 1000 1500 2000 2500

event size (bytes)

time

/ eve

nt (u

s)

Overhead = 13.6 us,Slope = 73 Mbyte/s,

Event Rate@1 kbyte = 36 kHz

Jorgen PetersenEP/ATD

Output to Network (EB)

• PC Farm in “Lab2”:– 450 MHz PCs– Gigabit Ethernet

• applications:– trigger and input emulated, 1kbyte

fragments, 100% L2A– not optimised

• results (event rate):– with DFM: 7.8 kHz ~ 10 Mbyte/s– without DFM: “TileCal” Mode

12.7 kHz ~ 16 Mbyte/s

ROS / PC Linux(TRGEBIFROB)

DFM

SFI

Jorgen PetersenEP/ATD

Output to disk (local recording)

• PC equipped with SCSI disk @ 17 Mbyte/s

• applications:– CORBO trigger, SLINK input 100%

L2A– not optimised– system controlled by LDAQ

• results (event rate):– 15 kHz ~ disk performance

ROS / PC Linux(TRGEBIFROB)

SCSI Disk

CORBO SLINK

Jorgen PetersenEP/ATD

Event Monitoring

• “Local” monitoring ( I.e. event monitoring on the Dataflow PC)

– CORBO + SLINK input ( 1kbyte fragments), no output, all events accepted

– event rate: 16 kHz (compared to 35 kHz) with a monitoring rate of 8500 events/s

• “Online” monitoring– as above, but with remote PC running the online monitoring – event rate: 30 kHz (compared to 35 kHz) with a monitoring

rate of about 400 events/s– event rate: 34 kHz (compared to 35 kHz) with a monitoring

rate of about 50 events/s

Jorgen PetersenEP/ATD

Selected hardware• VME detector crates (Hodoscope+Tracker, MDTs) :

– 2 RIOs, 2 CORBOs, KLOE TDCs, CAMAC TDCs and ADCs, 2 CSMs, 2 S-links (readout of beam instrumentation and chambers)

– NIM electronics and CAMAC-VME interface (trigger and CAMAC)

• PC replacing ROC :– 1 PC for Event Building, housing 2 PCI/S-link interfaces for

data input, 1 PCI Interrupt generator (u-Enable based)• 2 PCs to distribute :

– the Backend software– the application software (Monitoring)

• Local network : – switched LAN to avoid access from outside which slows

down data acquisition

Shopping list for 2001 Detector crates:• 2 RIOs (crate contrl.) 12 kCHFx2 = 24 kCHF• 2 S-Links 5.3 kCHFx2 = 10.6 kCHF• 2 CORBOs = no cost (?)• 1 CMAC/VME I/F = no cost• 4 CSMs = ?ROS emulator and PCs :• 1 PCI_CORBO = 1700. DM• 2 PCs of industrial type (12 PCI slots) = 8 kCHF• 1 PC (possibly rack mounted) = 2 kCHFInfrastructure :• 1 switch FastEthernet (24 ports) = 3 kCHF• 1 Hub= no cost (?)

Total = 48-50 kCHF + CSMs

Schedule and milestones (1)

• End of March 2001 :– Move CSM readout from Digital CPU to CES RIO2– Being based on TileCal software, workout what is

requested for the the two ROD Crates.– Take a decision on which DAQ version we shall use

(PC or TileCal). Accordingly, purchase the necessary hardware.

• End of April 2001 :– Get at least one ROD Crate working (software plus

hardware) either at CERN (DAQ-1 lab) or in Rome– Get experience with ROC or PC software.

Schedule and milestones (2)

• End of May 2001 : – test full system in a minimal configuration at CERN

(DAQ-1 lab)• June 2001 :

– work on Backend software and user specific software (monitoring, etc.)

• July 2001 : – use the system at H8

• Autumn 2001 :– Foresee the integration of MROD-1 prototype