1. Taikan Suehara, TB meeting, 5 Sep. 2014 page 1 Si/Sc combined DAQ Taikan Suehara (Kyushu University, Japan)

2. Taikan Suehara, TB meeting, 5 Sep. 2014 page 2 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 combine

3. Taikan Suehara, TB meeting, 5 Sep. 2014 page 3Image Run control piconf calicoes/pyrame Sc hardwareSi hardware Sc dataSi data Event builder LCIO file(s) Event display start/stop EUDAQ start/stop giving up complete integration

4. Taikan Suehara, TB meeting, 5 Sep. 2014 page 4 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 possible with 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)

5. Taikan Suehara, TB meeting, 5 Sep. 2014 page 5 Readout-cycle (ROC) control (TB mode) Event builder and data format Status & PlanTopics

6. Taikan Suehara, TB meeting, 5 Sep. 2014 page 6 ROC control on TB mode piconf calicoes/pyrame Sc hardwareSi hardware Sc dataSi data Event builder CCC next ROC Event builder will control next ROC Need to modify piconf/CCC

7. Taikan Suehara, TB meeting, 5 Sep. 2014 page 7 Aims Assure all data are correctly arrived Assure ROC # is consistent on the whole system Common format for Si/Sc cal data Assure run ID Inputs idea a: common LCIO objects idea b: raw + converter  First to implement piconf seems to have no output formatter Event builder

8. Taikan Suehara, TB meeting, 5 Sep. 2014 page 8 EUDAQ structure Calice Producer calicoes / piconf TCP connection

9. Taikan Suehara, TB meeting, 5 Sep. 2014 page 9 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 LCIO

10. Taikan Suehara, TB meeting, 5 Sep. 2014 page 10 LCIO: GenericObject LCIO Event  1 ROC - LCIO collections  1 types of data (SiADC, ScADC, ScTDC etc.) -LCIO objects LCGenericObject  1 chip of data LCGenericObject can save one array (int, float, double) dataDescription in every object can be used for tags, eg. “LDA=1;DIF=2;BX=10;”

11. Taikan Suehara, TB meeting, 5 Sep. 2014 page 11 Current status Succeeded to run EUDAQ with CaliceProducer producing dummy data encoded to LCIO object and save to LCIO file using DataCollector Ready to attach to calicoes/piconf  waiting them to be ready (for a long time!)

12. Taikan Suehara, TB meeting, 5 Sep. 2014 page 12 EUDAQ part Writing TCP adapter for calicoes/piconf Converter from raw to LCIO piconf 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 do

13. Taikan Suehara, TB meeting, 5 Sep. 2014 page 13 First BT period (Oct.) –Connection to piconf should be established Final – 2 nd 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)Schedule