1 / 8

GIF + + DAQ

GIF + + DAQ. 11/07/2013. requests. 2 trigger systems : RPC or TGC or (TGC and RPC) 3 or 4 experiments at the same time (one is main user : decide of the trigger system) Each DAQ has is own rate, independent of the others Events are tagged in order to be reconstructed. Event Tag.

clem
Télécharger la présentation

GIF + + DAQ

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GIF ++ DAQ 11/07/2013

  2. requests • 2 trigger systems : RPC or TGC or (TGC and RPC) • 3 or 4 experiments at the same time (one is main user : decide of the trigger system) • Each DAQ has is own rate, independent of the others • Events are tagged in order to be reconstructed

  3. Event Tag Detector 1 Detector 2 Detector 3 Detector 4 TRIGGER DAQ: RPC and/or TGC Trigger DAQ 1 DAQ 2 DAQ 3 DAQ 4 BUSY Xy trigger data Event builder Event builder Event builder Event builder Event Trigger x,y Detector1 xy Event Trigger x,y Detector2 xy Event Trigger x,y Detector3 xy Event Trigger x,y Detector4 xy

  4. VETO system Dual Timer CAEN N93B VME / SRS crate • start Trigger from TGC/RPC Delay few ns t= ∞ • stop out Coincidence unit I/O module in Trigger after veto out in

  5. Veto timeline diagram Dual Timer 1st trigger 2nd trigger Trigger TGC/RPC Coincidence DAQ reads modules I/O output Trigger after veto

  6. How it works ? • Logic signal from the dual timer is on (switch on by a I/O signal at the beginning of the run) • A trigger signal from TGC/RPC arrives • A logic “AND” between the dual timer and the trigger signal generates a “veto trigger”. This signal is send to the DAQ as the trigger signal. In the same time, the TGC/RPC trigger stop the dual timer. • If a new TGC/RPC signal arrives and the dual timer signal is off, no coincidence. • Once the DAQ finished its restart the dual timer with a I/O module

  7. Status TGC • A trigger system is working in israel : 2 small TGC + front end + DAQ  trigger signal and position information • A fake DUT (TGC) installed between the 2 TGCs with its own DAQ (VME system) triggered by the 2 TGCs DUT VME DAQ trigger VME DAQ TGC

  8. conclusion • The DAQ design is evolving but the basis exists • A small mockup exists and works WHAT NEEDS TO BE DEFINED : • Which kind of trigger do we need : clever (NIM signal + type of trigger) or simple trigger (NIM signal). Need to be written down and accepted by the users • Event tagging with TTCvi? • Where do we plan to develop the DAQ system? It starts to be important in term of materials and other materials is needed (SRS/VMM DAQ)

More Related