taikan suehara, tb meeting, 5 sep. 2014 page 1 si/sc combined daq taikan suehara (kyushu university,...

Taikan Suehara, TB meeting, 5 Sep. 2014 page 1

Si/Sc combined DAQSi/Sc combined DAQ

Taikan Suehara(Kyushu University, Japan)


1. New lightweight module which can be used with both Si/Sc system (or more) and seamlessly attached to bigger framework pending due to political difficulties

2. Temporal solution with minimal modification of individual frameworks (calicoes/piconf) to be attached to EUDAQ ongoing

How to combineHow to combine


ImageImage

Run control

piconf calicoes/pyrame

Sc hardware Si hardware

Sc data Si data

Event builder

LCIO file(s)

Event display

start/stop

EUDAQ

start/stop

giving up complete integration


1. EUDAQ is not well designed• Not stable – SEGV in many situations

• Somewhat operable with careful use

• Framework and codes for individual hardwares are not well separated

• Adhoc solutions possiblewith hope to improve in future

2. calicoes/piconf are also not well designed to attach to bigger frameworks• It seems they aim to be ‘the bigger framework’

by themselves instead of attaching to another• Need to create hooks to connect

- not smart, but possible

Issues (or complaints)Issues (or complaints)


• Readout-cycle (ROC) control (TB mode)• Event builder and data format• Status & Plan

TopicsTopics


ROC control on TB modeROC control on TB mode

piconf calicoes/pyrame

Sc hardware Si hardware

Sc data Si data

Event builder

CCCnext ROC

Event builderwill control next ROCNeed to modify piconf/CCC


Aims•Assure all data are correctly arrived•Assure ROC # is consistent on the whole system•Common format for Si/Sc cal data•Assure run IDInputs•idea a: common LCIO objects•idea b: raw + converter First to implementpiconf seems to have no output formatter

Event builderEvent builder


EUDAQ structureEUDAQ structure

CaliceProducer

calicoes / piconf

TCP connection


1. Store ‘hit’-like objects• We have ‘CalorimeterHit’ class in LCIO• Need threshold – not always suitable for

low-level analysis (cross talk etc.)

2. Store simple array of raw data planned• More flexibility; hit-like data can be

created from the raw array• Need more steps for high-level analysis• No specific LCIO structure, use

LCGenericObject with attachment class

Data format in LCIOData format in LCIO


LCIO: LCIO: GenericObjectGenericObject

LCIO Event 1 ROC- LCIO collections 1 types of data (SiADC, ScADC, ScTDC etc.)-LCIO objectsLCGenericObject 1 chip of data

LCGenericObject cansave one array(int, float, double)

dataDescriptionin every object can beused for tags, eg.“LDA=1;DIF=2;BX=10;”


Current statusCurrent statusSucceeded to run EUDAQwith CaliceProducer producingdummy data encoded to LCIO objectand save to LCIO file using DataCollector

Ready to attach to calicoes/piconf waiting them to be ready(for a long time!)


EUDAQ part•Writing TCP adapter for calicoes/piconf•Converter from raw to LCIOpiconf part•Debug/test piconf itself (I can help if needed)•TCP output of raw data from piconfm•CCC ROC control function

•Integration and test

Things to doThings to do


• First BT period (Oct.)– Connection to piconf should be established

• Final – 2nd BT period (26 Nov.-)– Full version

• My schedule– Sep. 11-14 at DESY (fixed)– Oct. 11-14 at CERN (almost finalized)– 2.5 weeks at Nov.-Dec. for second BT

(planned but not fixed, adjusting my lecture duty)

ScheduleSchedule

taikan suehara, tb meeting, 5 sep. 2014 page 1 si/sc combined daq taikan suehara (kyushu university,...

Documents