Status & Prospect

1. TB status
– run control
– peripheral/FED crate
– DAQ column
2. HCAL integration prospect
– idem
July 1, 2004 TB2004 DAQ Code Development 2

• a.k.a TrackFinder GUI
• XDAQ v2 framework
• fully operational and tested
RunControl dBase
July 1, 2004
TTC control
PC/FED control
TF control
RU/BU
TB2004 DAQ Code Development 3

• new CCB, new TMB, various firmware upgrades (TMB, DMB, MPC)
• 4 chamber + 1 RPC readout
• single/multiple crate configuration
• updates fed back to DCS (new hardware)
• DCS integration initiated
– communication protocol between DCS and
PC-control
• TMB timing tools, derived from PC-lib
July 1, 2004 TB2004 DAQ Code Development 4

BU: EventBuilder
EVBOut
EmuFED
RU
SpFED
RU
DDU VME (DDU)
• CMS DAQ structure
• XDAQ v2 platform
• EVBOut/BU/RU/EmuFED column fully operational & tested
July 1, 2004 TB2004 DAQ Code Development 5

• EventBuilder
– adaptation by Ichiro Suzuki
– prototype for CMS, used by HCAL too.
• Full EmuDAQ column tested
– No more time for SPFED column integration
• SPFED has still VME-based readout (as opposed to DDU)
• DDU-to-BigPhysArea kernel module issue
– most likely an SMP kernel problem, resulting in BigPhysArea data corruption
• issue solved for EmuFED-standalone and EmuDAQ-column data.
– provisional fix (memory leak in return)
• however, eth_hook still capable of hanging a (random?) process resulting in 100% cpu-usage on one of the 4 CPUs.
July 1, 2004 TB2004 DAQ Code Development 6

• 130Gb of data collected in various
DAQ modes
– raw reader from bigphysarea device
• debugging purposes
– EmuFED-based standalone reader
• debugging purposes
– EventBuilder based
EVB output
• official output
July 1, 2004
• data sample sizes:
– ddudumper (raw reader):
• 64Gb
– hardwareDumper:
• 57.4Gb
– EVBOutput:
• 11Gb
– SPFed data:
• 0.5Gb
TB2004 DAQ Code Development 7

• Continue integration TF+FED event building
– hook-up the SPFED DAQ column (DDU or VME?)
• Integrate with HCAL EventBuilder
– make sure we are still on the same track
• Continue to investigate DDU-to-BigPhysArea
• Fully integrate DCS and PC-control:
– have both use the same library
• prevents out-of-phase and parallel development of software for the same hardware
• allows easier solutions for PC access control
– DCS-control of PC access
• Continue to enhance existing and develop new features for (Emu)
RunControl
– configuration and conditions dBase updates
• Start actively documenting all relevant modules.
– doxygnize the code
July 1, 2004 TB2004 DAQ Code Development 8

• Dynatem-360 replacement?
– API is needed well ahead of time
• significant effect on DCS and PC-control
– HAL based?
• New DDU/DCC
– API is needed, preferably ahead of time
– SP readout through DDU?
July 1, 2004 TB2004 DAQ Code Development 9