1. MICE CM January 2009Jean-Sébastien GraulichSlide 1 Detector DAQ Issues o Achievements Since CM23 o Detector DAQ o Trigger o Online Software o Front End Electronics o Schedule Milestones o Summary Jean-Sebastien Graulich, Geneva

2. Achievements since CM22  TOF1 included in the DAQ and in the trigger  New flashADC (500MHz) installed for CKOV  Computer Clock synchronization fixed Not 100% satisfactory: PCs are synchronized to each other but not to the outside world (firewall issue)  Slow progress in including the target DAQ and CAM into the online Data Stream  Progress has been slower than foreseen MICE CM January 2009Jean-Sébastien GraulichSlide 2

3. Detector DAQ Issues  Known issues Limit on the number of particle events From DAQ itselfs ( about 200 Particles/Spill ) Was expected Technical solutions exist From Online Monitoring ( about 40 Particles per Spill ) Not expected Need more investigations Event reconstruction Occasional and marginal mismatch between the number of particle triggers in different VME boards Recently, dramatic mismatch between the number of particle triggers in the two crates for some runs -> Serious Event building problem ! Need more investigations  Interface with EPICS becomes a top priority MICE CM January 2009Jean-Sébastien GraulichSlide 3

4. Detector DAQ Issues  Feed back from user Need better handling of DAQ crashes Need loud, emphatic, and unambiguous indicators that data are or are not being recorded. MICE CM January 2009Jean-Sébastien GraulichSlide 4

5. MICE CM January 2009Jean-Sébastien GraulichSlide 5 Target DAQ issues  Progress slowed down Need consistent integration with the stand alone target DAQ We want a common software basis for file read/write operations  Target DAQ under deep revision

6. Trigger Issues MICE CM January 2009Jean-Sébastien GraulichSlide 6  TOF0 and TOF1 trigger implemented  Particle Trigger selection by hardware There is a plan to implement software selection Not a priority for the moment  Particle Trigger pre-scaling Needed because of limitation on the DAQ input rate Need hardware intervention Not fully satisfactory -> Need investigation  Need decision on the future of GVA1 Should it stay or should it go ? GVA2 and GVA3 are gone already

7. Burst Gate Correlation MICE CM January 2009Jean-Sébastien GraulichSlide 7 GVA1 hit Burst Gate made narrow  No progress achieved since CM22

8. Online Software  Unpacking library needs upgrade New fADC (V1731) for CKOV New version to be distributed next week  Interface with G4MICE First task is to reproduce online histograms (David Adey) See Software session for more details  Know issues Online monitoring GUI tends to get stalled at the end of a run Online monitoring histograms are not labeled according to detector names That is a feature! Need better Online plots for fADC Current plots found not efficient in detecting broken channels Not straight forward task (fluctuating baseline) MICE CM January 2009Jean-Sébastien GraulichSlide 8

9. MICE CM January 2009Jean-Sébastien GraulichSlide 9 Front End Electronics  CKOV New 500 MHz fADC has been installed Performance has to be evaluated and compared to the previous scheme There is no more TDC data for CKOV  TOF TOF TDCs are not properly synchronized. Internal clock has to be distributed. For the moment, we use the common Part. Trigger signal in ch0 of each TDC TOF2: We miss some electronics Shapers/Splitters: In production TDC: One board missing FADC: 3 boards missing  SW (aka Electron Muon Ranger) A technical proposal has been submitted to the Technical board

10. MICE CM January 2009Jean-Sébastien GraulichSlide 10 FEE Issues  Cross Talk Issue Not yet clearly understood New design is under study  FADC firmware upgrade Needed to allow significant reduction of data volume Less samples per Particle event (currently 512 whereas only 60 are necessary Zero suppression (to be tested) Delicate operation  Splitter/Shaper Production Board production is finished in Sofia Discrete components are in hand in Geneva Mounting will start in February  Missing TDC/fADC Shouldbe ordered by Ludovico/Maurizio (funding issues)

11. MICE CM January 2009Jean-Sébastien GraulichSlide 11 Schedule Milestones  From CM22  DAQ review December 2009  Upgrade of fADC firmwareNovember 4  CAM data in Online Data StreamPostponed  DAQ migration to the DAQ/Control networkOctober 30  Target DAQ included in Detector DAQNovember 4  Tracker integrated in DAQ?  Tracker integrated in Online Monitoring?  TOF2 Shaper ProductionStarted – Dec 15  TOF TDC Clock SynchronizationDecember 10  TOF1 in trigger systemDecember 10  Burst Gate Signal in the Trigger SystemDecember 13  Approval of SW/EMR Front End ElectronicsEarly November  Production of SW/EMR Front End Electronics ? June 2009 ?  Installation of the Online Reconstruction FarmNovember-December

12. MICE CM January 2009Jean-Sébastien GraulichSlide 12 Schedule Milestones  New Milestones  Target DAQ included in Detector DAQmid February  DAQ migration to the DAQ/Control networkMarch 06  Installation of the Online Reconstruction FarmMarch 06  Upgrade of fADC firmwareMarch 06  TOF2 Shaper/Splitter ProductionStarted – mid March  CAM data in Online Data Streamend of April  Tracker integrated in DAQ and OLMend of April  TOF TDC Clock Synchronizationend of April  DAQ review May 2009  Burst Gate Signal in the Trigger Systemneed beam  Approval of SW/EMR Front End Electronicsdepends on INFN  Production of SW/EMR Front End ElectronicsSeptember 2009

13. MICE CM January 2009Jean-Sébastien GraulichSlide 13 Summary  TOF1 has been integrated into DAQ, Trigger and OLM  CKOV readout has been upgraded  Many recent milestones have been missed No real show stopper All key issues can be solved before serious things start in May 2009  Serious problem with event building discovered Deserve serious attention First step is to get online diagnostic  Target DAQ will be integrated to Detector DAQ Work still in progress  FEE for SW/EMR and TOF2 are priority tasks  Current DAQ issues can still be solved before Step 2