1. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 1 Detector DAQ Status o Since CM15 o Detector DAQ software o Interface DDAQ / Mice Control & Monitoring o Triggers o Front End Electronics o Schedule Milestones o Summary Jean-Sebastien Graulich, Geneva

2. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 2 Since CM15  Vassil Verguilov joined the group as PhD student at Univ. Geneva  Test beam in Frascati Complete success for the DAQ  DAQ Software Training started in CERN-ALICE group  DAQ workshop III took place in Daresbury Focused mainly on Control and Monitoring  A mailing list for DAQ, Control and Monitoring has been set up mice-dcm@mice.iit.edumice-dcm@mice.iit.edu Don’t hesitate to subscribe  A DAQ Web site is under construction

3. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 3 DDAQ Software  Training has started in the CERN-ALICE group The ALICE DAQ software framework, DATE, will provide us with the necessary EventBuilder tool: Subevents collected by different processors have to be synchronized and put together before storage We are working on special readout for the data generated by ALICE Central Trigger Processor The technique we develop there can be applied for MICE DDAQ / MCM Interface -> Efficient Training Contact with ALICE Team is excellent  DATE is running on a MICE PC, sources are available Not yet for MICE applications…  As far as we can tell today, DATE complies with MICE needs It has much more functionalities than what MICE needs

4. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 4 Interface DDAQ / MCM  Decisions taken at DAQ Workshop III: A list of selected physical variables will be included in the online data stream from MCM (Mice Control & Monitoring) This data will be collected asynchronously during the run, written in a local file which is appended to the data file at the end of the run The same data will be also logged in the MCM archived Run start and Run stop will be logged in the MCM archive The Run will be stopped automatically in case one subsystem (Beam, RF, PID, etc.) goes into a fault status or in case of connection problem  Technical implementation already tested !  To Do: Prepare the list of relevant variables -> Analysis working group Define when each subsystem is faulty -> subsystems

5. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 5 DataFlow Revised General Architecture Trigger distribution Tracker EmCal TOF Trigger + Ckovs GigaBit Switch Event Builder (GDC) OnlineStorage Online Monitoring Run Control Remote Mass Storage 100 Mb Switch VME Crates Optical links Linux PCs (LDC) MCM Readout MCM Subnet

6. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 6 Test Bench in Geneva  Frozen since CM15 Waiting for DATE software  Everything in hand now V2718 received in Feb. VME crates delivered  Will start as soon as we are back distribution Trigger Optical link + Online Monitoring TOF Trigger Ethernet Linux PCs Office Switch Run Control + Event Builder VME Crates + Local Storage

7. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 7 Synchronization Issue  3 subsystems have to be synchronized with each other and with the ISIS Machine Cycle: Target RF DAQ  A fixed frequency approach is not optimal: Busy/Recovery time might not be constant (certainly the case for DDAQ)  An “As Soon As Ready” approach has been proposed in MICE-NOTE-DAQ-147 Each system provides a veto signal which is set when the system is not ready to receive a trigger The first MS after all veto’s are dropped generates the different triggers

8. MICE Veto Target Veto RF Veto DAQ Veto MS Target Request RF Request Target Trigger Protons on target RF Trigger RF Power DT Gate DAQ Trigger Target Delay RF Delay DT Delay 20 ms Extraction

9. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 9 Triggers  DAQ Trigger Triggers the readout of the Front End Electronics output buffer memory Should arrive at the end of the Spill, after the last event of the Spill Distributed to all VME crates  Particle Trigger Triggers the digitization of the signals arriving at the Front End Electronics Should arrive a few ns around the signal (before in case of the SIS 3320) Distributed to all FEE boards We expect about 600 Particle triggers for 1 DAQ trigger

10. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 10 DAQ Trigger  DATE requires dedicated inputs for at least 4 event Types: 1)Start of Spill: A signal sent to the DAQ slightly before the beginning of the Spill in order to make sure that all the processes are ready to receive data 2)Physics 3)End of Spill: A signal sent to the DAQ when the readout is finished which allow checking that all the processes have correctly performed the readout 4) Calibration  More inputs allows more options E.g. Calibration events can be pulser or pedestal or cosmics, etc. Dedicated input allows dedicated readout and/or event building and/or tagging with event attribute

11. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 11 Particle Trigger  4 Particle Trigger Conditions for Normal Events Burst: All ISIS bunch crossing with the target within the DT-Gate can produce a particle trigger, providing that the FEE is not busy Beam: Burst  TOF0 Timing given by Burst Upstream: Beam  TOF1 Timing given by TOF1 Traversing: Upstream  TOF2 Timing given by TOF1 TOFn is defined by a twofold (Left x Right) coincidence of the OR of the 12 (8) slabs of a single layer  Trigger condition does NOT depend on Beam Momentum !  Trigger Condition should be selected on the Run Control GUI before each Start of Run This feature is not included in DATE but technical solution exists

12. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 12 Particle Trigger  Simplest Implementation of the Trigger Condition selection using output Register OReg1 OReg2 OReg3 OReg4 Burst TOF0 TOF1 TOF2 Particle Trigger Request FEE Busy Particle Trigger  Setting OReg selects the trigger condition  Not extendable to (much) more conditions !  I/O register CAEN V977 has been adopted

13. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 13 FE Electronics: Reminder  Flash ADC (option for charge measurement in EmCal) Evaluation module received from Struck SIS3320, 200 MHz, 12 bits, 32 MB Event Buffer Readout OK, tested at BTF, Frascati Testing energy and time resolution after shaper 2 ns rise time Shaper + Invert. V thr t thr ~30 ns rise time If we can fit the rising edge, time resolution can be much better than the 5 ns of the sampling rate.  Advantage: No signal splitter, no delay cable, no discriminator, no TDC ! It’s commercially available !! It’s commercially available !! PMT

14. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 14 Flash ADC test with cosmics Time (sample #) Amplitude fit = p4 – p0 (  0 / (  0 -  ) ) [ ( e -(t-t 0 )/  -e -(t-t 0 )/  0 ) + (t-t0) /  e -(t-t 0 )/  ] 0 =0 =  = = t0 =t0 = Shaper Prototype (2ch) produced by Ilko Rusinov (Sofia)

15. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 15 Trigger Pos 2 Trigger Pos 1 Flash ADC test with cosmics Pmt leftPmt right Shaper ch01 ch02 ~22 cm Test done with TOF Scintillator bar and TOF Pmt (R4998)

16. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 16 Flash ADC test with cosmics = 700 ps t 0;left – t 0;right (sample) ~2.5 ns

17. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 17 Flash ADC Tests  Data from BTF not analyzed yet Problem with the shape of the signal The formula is valid only for exponential signal Problem with EMcal because of Long cable Passive splitter Special base (voltage divider) for differential output  Energy resolution not yet evaluated  CAEN proposed a cheaper 100 MHz Flash ADC They will provide use with an evaluation module in November

18. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 18 FE Electronics Tests  Still pending ToT Discriminator (cheap option for TOF) TeV IPM (option for charge measurement in EmCal and TOF) … We are short of man power !

19. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 19 Schedule Milestones  Complete Flash ADC/BTF Data analysis: Nov 2006  DAQ Test bench including Event builder: Feb 2007  Order Hardware for Stage 1: March 2007  Move DDAQ system to RAL: July 2007 ItemRequiredAlready Purchased Total Cost (k€) Already Spent (k€) 6U VME crates + power supply4+1424.519.1 VME-PCI interface6+1617.515.0 Data Collector PC6+147.04.0 Network switches20~120.0 Event Builders2+10~150.0 Local Storage (~8 TB)10~150.0 Workstations + monitors (control, monitoring, on-line analysis) 70~150.0 Trigger receiver6+1711.9 Vme Scaler Unit102.10.0 Trigger Logic Modules~100 channels0~100.0 Trigger Logic, Cables, Connectors and Adapters ~100 channels060.0 Oscilloscope10300.0 TOTAL DAQ + Trigger~166 k€50 k€

20. MICE CM16 Oct 2006Jean-Sébastien GraulichSlide 20 Summary  DATE software training has started with success  Interface between DDAQ and MCM is well defined  Trigger scheme is well defined  FE Electronics tests are late Flash ADC is OK in Principle BUT Energy resolution has to be evaluated Other options won’t be tested unless we find more man power  We plan to deploy the DDAQ system here in Mid June 2007