Slice Test DAQ

Two Systems Underway

•There are essentially two systems being designed concurrently: Trackfinder test, and EMU slicetest.

•Goals of the two systems initially different but it is clear they have to merge into the same system eventually

•Trackfinder effort being lead by Florida (Acosta et al.) with a little help from Rice

– Song Ming Wang, Holger Stoeck, Bobby Scurlock, Alex Madorsky

•EMU effort (Padley is manager)– Stan Durkin, Vivian O’Dell, Pat Murray, Ron Rechenmacher, Ichiro Suzuki,

Rick Wilkinson

CMS Slice Test DAQ Work at FermilabIn January a group worked together at a US CMS DAQ test stand with Endcap Muon Electronics getting hands on experience and a first pass at a design.

We’ll get together at Fermilab for another two weeks in mid-April

Pat Murray EMU ElectronicsRon Rechenmacher D0 DAQ ExperienceIchiro Suzuki XDAQ & Event BuilderRick Wilkinson C++ & ORCA

Alex Tumanov Just hired by Rice

Hardware Setup at Fermilab

Brought by Pat from OSU, Davis• One VME crate• One DAQ Motherboard• One Dynatem 360• One Cathode Front End Board• Two toaster-shaped PC’s for

Local DAQ control

Ichiro’s Event Builder farm

Local DAQ PC, CFEB

“Toaster” PCCFEB

Dynatem

Draft Configuration

DAQMBCCB

Local DAQ PCPeripheral Crate

Disk

Write toBigPhysmemory

CFEBDDUCCB

FED Crate

XDAQI2O

ORCAreadable

Event Builder

XDAQWIN

Run Control PC

CFEB Control Software• Using Stan’s C++ version with re-

engineering by Rick– Thanks, Stan!– We still need to write a validation suite– Hope to share this package with the UCR

slow control group

• Now usable through an XDAQ interface (Ichiro, Rick)– Every method in Stan’s tests now has a

button in an XdaqWin

• In the Florida CVS repository– Thanks, Ron & Darin!

DAQMB

VMEModule

Crate

CCB

FakeCCB

What We Do with the DDU Output

• We’ll first dump this directly to local disk– Using a simple binary format– May need mass storage?

• Brian Mohr at UCLA is updating his EMU ROOT display to read DDU output

The DDU writes directly to memory of the Local DAQ PC’s.

We’ll also send the data of to the Event Builder…

The Event Builder

• Mostly just the standard XDAQ Event Builder software, built by Steve Murray (CERN), with input/output modifications by Ichiro.

• We need to write code to feed the DDU output streams into the Event Builder,– both from memory and from disk.

• EVB is still slow on Ethernet, but can reach a few MB/s on Myrinet

• Rick is working on putting the DDU data that will come out of the EventBuilder into ORCA, using a framework by Giacomo Bruno (CERN).– Understanding and C++-ifying Ohio State’s data unpacking code– Disk format should be mostly the same as binary dumps

Simulation

• Once the data is into ORCA, we can use it to do cluster-finding, segment-building, tracking, and ntuples/ROOT trees.

• UC Davis group (Tim Cox & Michael Case) plan to run ORCA simulations of the test beam, so the simulation can be compared to the data– Nice usability test for the Detector Description Database

Conclusions

Still some complications we haven’t worried about yet, like trigger input and conditions

But since the UCLA EMU meeting we have moved from just drawing cartoon sketches…

to actually putting the Tinkertoys together.

Still hoping to have things ready to try by May testbeam

• Might be too aggressive a goal, but we’ll try.