mice cm16 oct 2006jean-sébastien graulichslide 1 detector daq status o since cm15 o detector daq...
TRANSCRIPT
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 1
Detector DAQ StatusDetector 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
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 2
Since CM15Since CM15 Vassil Verguilov Vassil Verguilov
joined the group as PhD student at Univ. Geneva Test beam in FrascatiTest beam in Frascati
Complete success for the DAQ DAQ Software Training started in CERN-ALICE DAQ Software Training started in CERN-ALICE
groupgroup DAQ workshop III took place in DaresburyDAQ workshop III took place in Daresbury
Focused mainly on Control and Monitoring A mailing list for DAQ, Control and Monitoring A mailing list for DAQ, Control and Monitoring
has been set uphas been set [email protected] Don’t hesitate to subscribe
A DAQ Web site is under constructionA DAQ Web site is under construction
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 3
DDAQ SoftwareDDAQ Software Training has started in the CERN-ALICE groupTraining 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 ProcessorThe 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 DATE is running on a MICE PC, sources are
availableavailable Not yet for MICE applications…
As far as we can tell today, DATE complies As far as we can tell today, DATE complies with MICE needswith MICE needs
It has much more functionalities than what MICE needs
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 4
Interface DDAQ / MCMInterface DDAQ / MCM
Decisions taken at DAQ Workshop III: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 !Technical implementation already tested ! To Do: To Do:
Prepare the list of relevant variables -> Analysis working group
Define when each subsystem is faulty -> subsystems
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 5
DataDataFlowFlow
Revised General Revised General ArchitectureArchitecture
Trigger distribution
Tracker EmCal TOF Trigger + Ckovs
GigaBit Switch
Event Builder(GDC)
Online Storage Online
Monitoring Run Control
Remote MassStorage
100 Mb Switch
VME Crates
Optical links
Linux PCs(LDC)
MCMReadout
MCMSubnet
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 6
Test Bench in Test Bench in GenevaGeneva
Frozen since CM15Frozen since CM15 Waiting for DATE
software
Everything in hand nowEverything in hand now V2718 received in Feb. VME crates delivered
Will start as soon as Will start as soon as we are backwe are back
distributionTrigger
Optical link
+ Online Monitoring
TOFTrigger
Ethernet
Linux PCs
Office Switch
Run Control
+ Event Builder
VME Crates
+ Local Storage
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 7
Synchronization Synchronization IssueIssue
3 subsystems have to be synchronized with each 3 subsystems have to be synchronized with each other and with the ISIS Machine Cycle:other and with the ISIS Machine Cycle:
Target RF DAQ
A fixed frequency approach is not optimal: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 An “As Soon As Ready” approach has been proposed in MICE-NOTE-DAQ-147proposed 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
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
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 9
TriggersTriggers
DAQ TriggerDAQ 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 TriggerParticle 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
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 10
DAQ TriggerDAQ Trigger DATE requires dedicated inputs for at DATE requires dedicated inputs for at
least 4 event Types: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)Physics3)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 optionsMore 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
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 11
Particle TriggerParticle Trigger 4 Particle Trigger Conditions for Normal Events4 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 Trigger condition does NOT depend on Beam Momentum !Momentum !
Trigger Condition should be selected on the Run Trigger Condition should be selected on the Run Control GUI before each Start of RunControl GUI before each Start of Run
This feature is not included in DATE but technical solution exists
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 12
Particle TriggerParticle Trigger
Simplest Implementation of the Trigger Simplest Implementation of the Trigger Condition selection using output RegisterCondition selection using output Register
OReg1
OReg2
OReg3
OReg4
Burst
TOF0
TOF1
TOF2
Particle TriggerRequest
FEEBusy
Particle Trigger
Setting OReg selects the trigger conditionSetting OReg selects the trigger condition Not extendable to (much) more conditions !Not extendable to (much) more conditions ! I/O register CAEN V977 has been adoptedI/O register CAEN V977 has been adopted
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 13
FE Electronics: FE Electronics: ReminderReminder
Flash ADC (option for charge measurement in Flash ADC (option for charge measurement in EmCal)EmCal)
Evaluation module received from StruckSIS3320, 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.
Vthr
tthr ~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: Advantage: No signal splitter, no delay cable, no discriminator, no TDC !No signal splitter, no delay cable, no discriminator, no TDC !
It’s commercially available !! It’s commercially available !!
PMT
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 14
Flash ADC test with Flash ADC test with cosmicscosmics
Time (sample #)
Am
plit
ud
e
fit = p4 – p0 (0/(0-)) [ (e-(t-t0)/-e-(t-t0)/0) + (t-t0)/ e-(t-t0)/]
0 =
=t0 =
Shaper Prototype (2ch) produced by Ilko Rusinov (Sofia)
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 15
TriggerPos 2
TriggerPos 1
Flash ADC test with Flash ADC test with cosmicscosmics
Pmt left Pmt right
Shaper
Shaper
ch01
ch02
~22 cm
Test done with TOF Scintillator bar and TOF Pmt (R4998)Test done with TOF Scintillator bar and TOF Pmt (R4998)
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 16
Flash ADC test with cosmicsFlash ADC test with cosmics
= 700 ps
t0;left – t0;right (sample)
~2.5 ns
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 17
Flash ADC TestsFlash ADC Tests
Data from BTF not analyzed yetData from BTF not analyzed yet Problem with the shape of the signal
The formula is valid only for exponential signalProblem with EMcal because of
Long cable Passive splitter Special base (voltage divider) for differential output
Energy resolution not yet evaluatedEnergy resolution not yet evaluated CAEN proposed a cheaper 100 MHz Flash CAEN proposed a cheaper 100 MHz Flash
ADCADC They will provide use with an evaluation module in
November
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 18
FE Electronics TestsFE Electronics Tests
Still pendingStill pending ToT Discriminator (cheap option for TOF) TeV IPM (option for charge measurement in
EmCal and TOF)
… … We are short of man power !We are short of man power !
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 19
Schedule MilestonesSchedule Milestones Complete Flash ADC/BTF Data analysis: Complete Flash ADC/BTF Data analysis: Nov Nov
20062006 DAQ Test bench including Event builder: DAQ Test bench including Event builder: Feb Feb
20072007 Order Hardware for Stage 1: Order Hardware for Stage 1: March March
20072007 Move DDAQ system to RAL: Move DDAQ system to RAL: July 2007July 2007
Item Required AlreadyPurchased
Total Cost (k€)
Already Spent (k€)
6U VME crates + power supply 4+1 4 24.5 19.1
VME-PCI interface 6+1 6 17.5 15.0
Data Collector PC 6+1 4 7.0 4.0
Network switches 2 0 ~12 0.0
Event Builders 2+1 0 ~15 0.0
Local Storage (~8 TB) 1 0 ~15 0.0
Workstations + monitors (control, monitoring, on-line analysis)
7 0 ~15 0.0
Trigger receiver 6+1 7 11.9 11.9
Vme Scaler Unit 1 0 2.1 0.0
Trigger Logic Modules ~100 channels 0 ~10 0.0
Trigger Logic,Cables, Connectors and Adapters
~100 channels 0 6 0.0
Oscilloscope 1 0 30 0.0
TOTAL DAQ + Trigger ~166 k€ 50 k€
MICE CM16 Oct 2006
Jean-Sébastien Graulich Slide 20
SummarySummary
DATE software training has started with DATE software training has started with successsuccess
Interface between DDAQ and MCM is well Interface between DDAQ and MCM is well defineddefined
Trigger scheme is well definedTrigger scheme is well defined FE Electronics tests are lateFE 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 We plan to deploy the DDAQ system here in Mid June 2007Mid June 2007