overview of minerva daq
play

Overview of MINERvA DAQ Clarence Wret ArgonCube 2x2 Electronics - PowerPoint PPT Presentation

Overview of MINERvA DAQ Clarence Wret ArgonCube 2x2 Electronics & Readout Integratjon meetjng 4 September 2019 Overview MINERvA planes are to be used in the ArgonCube 2x2 demonstrator, aka proto DUNE-ND Upstream rock muon


  1. Overview of MINERvA DAQ Clarence Wret ArgonCube 2x2 Electronics & Readout Integratjon meetjng 4 September 2019

  2. Overview ● MINERvA planes are to be used in the ArgonCube 2x2 demonstrator, aka “proto DUNE-ND” ● Upstream rock muon veto ● Downstream tracking, ECal and HCal – Not too dissimilar from DUNE ND, where we’ll have ArgonCube → HPTPC/MPD (Ar gas) → 3DST (plastjc scintjllator) ● Proto DUNE-ND is a good place to study track matching, containment, effjciencies etc ● Patrick Koller’s studies (Bern) ● Steve Manly’s presentatjon (Rochester) Clarence Wret 2

  3. Proto DUNE-ND design Actjve tracker Geometry 12 modules From From used for the = 24 planes HCal Patrick Patrick (48cm) downstream 20 modules = 40 planes tracker studies (90.8cm) by Patrick ECal 10 modules = 20 planes (44cm) Add in upstream tracker From Steve Clarence Wret 3

  4. MINERvA detector Keep some of these Keep these ● For our purposes, all the MINERvA DAQ is handled by 2 VME crates, and all the readout is the same – Nuclear targets and veto wall has difgerent design, but we’re not using those for 2x2 ● Detector arxiv link Clarence Wret 4

  5. DAQ overview ● Custom DAQ designed by MINERvA collaborators, many at FNAL: arxiv link – Gabe Perdue, Linda Bagby, Chris Gingu, Paul Rubinov, amongst others – (I am nowhere near as expert as they are!) Readout node Per FE Per CROC-E computer (CAEN A2818 FE 1 FEB 1 CROC-E 1 Per FEB PCI) FE 2 FEB 2 CROC-E 2 … … … 6 TriP-t Per VME Up to 4 Up to 15 Up to 8 chips Per (only VME crate Per 6 readout used up (CAEN Per 4 CROC-E TriP-t node to 10) V2718) 1 PMT Daisy (R7600 chained 64 ch.) CROC MINERvA Interface Timing Module Module (MvTM) Clock, CROC = Chain ReadOut Controller (CRIM) tjming, FE = Front End channel trigger FEB = Front End Board Clarence Wret 5

  6. Pictures PMT box/housing FEB MINERvA connector planes PMT Clarence Wret 6

  7. Pictures Rack view Side view Top view Chain of ~10 VME 0 FEBs in one FE Rack down One here FEB CRIM CROC-E VME 1 Four chains of PMT FEBs per FE MvTM Side view box Power Readout FEB voltage nodes MINERvA supply planes (FESB, 48V) MINERvA had 15 CROC-Es (8 on VME 0, 7 on VME 1) (15 CROC-E) x (4 chains per CROC-E) x (10 FEBs per FE chain) x (1 PMT per FEB) = 600 PMTs supported 507 actually installed and running For prototype have a total of 10+20+24=54 modules: need at least 7 CROC-E Plenty of spare CROC-Es, FEBs and PMTs for prototype Clarence Wret 7

  8. Run Control and Slow Control ● Custom in-house ● Run Control: straight-forward python GUI – Requires wxPython (GUI) and pySerial (reads RS- 232 port) – Essentjally sshs onto DAQ machine, controls run through tunnel ● Slow control: straight-forward GUI – Can fjnd hardware for each VME, control VMEs, CROC-Es, CRIMs, load up new confjguratjons, etc Clarence Wret 8

  9. DAQ work todo ● Can add/remove channels to slow control and DAQ – Update the confjguratjon fjles to have i VME crates, j CROC-E and k FEBs – Have done this at MINERvA and Lab F test-bench – This is what we would do for 2x2 ArgonCube test ● I see litule point in re-engineering the DAQ hardware, fjrmware, sofuware; objectjons? – Rate should be fjne: MINERvA operated in Medium Energy era with modifjcatjons to DAQ that we will use ● The challenge is interface the system with ArtDAQ – MINERvA DAQ puts data into “frames”: ArtDAQ needs to know the frame structure – Replace ET* *Event Transfer, JLab software. Used to move data from readout node (1 per VME) to master node Clarence Wret 9

  10. Thanks Clarence Wret 10

Recommend


More recommend