Triggering and physics context Pierre Lasorak 1 Outline A - - PowerPoint PPT Presentation

triggering and physics context
SMART_READER_LITE
LIVE PREVIEW

Triggering and physics context Pierre Lasorak 1 Outline A - - PowerPoint PPT Presentation

Triggering and physics context Pierre Lasorak 1 Outline A framework for testing the triggers New geometries Conclusion Pierre Lasorak 2 12/04/2019 What we want to achieve Design choice we make in the trigger positive


slide-1
SLIDE 1

Triggering and physics context

1

Pierre Lasorak

slide-2
SLIDE 2

Pierre Lasorak 12/04/2019

Outline

  • A framework for testing the triggers
  • New geometries
  • Conclusion

2

slide-3
SLIDE 3

Pierre Lasorak 12/04/2019

What we want to achieve

  • Design choice we make in the trigger → positive impact on physics
  • In effect, this also includes detector designs (c.f. PDS, long drift…)
  • Backgrounds
  • Positive impacts should to be mitigated by overall data rate, both instantaneous and over

longer periods of time

  • JKlein’s data rates (for 10kT SP)

3

slide-4
SLIDE 4

Pierre Lasorak 12/04/2019

Where we want to go

  • Need an integrated tool that calculate rate / efficiency, for all the physics we are

interested in.

  • Many are now designing new algorithms in different parts of the chain that can affect the

whole trigger decision. Should be able to compare standard “candles” and be able to get efficiency and rates simply.

  • A few standard candles that I can think of:
  • 10 MeV KE isotropic electrons 10 cm away from the APA
  • 10 MeV KE isotropic electrons 10 cm away from the CPA
  • 1 GeV KE isotropic muons / electrons
  • Single protons events
  • Marley, beam, cosmic, background events
  • We would still miss any very pathological behaviours… but hard to simulate!
  • ProtoDUNE data

4

slide-5
SLIDE 5

Pierre Lasorak 12/04/2019

What we should check

5

1 − 0.8 − 0.6 − 0.4 − 0.2 − 0.2 0.4 0.6 0.8 1 Proj Y 3.5 4 4.5 5 5.5 6 6.5 7 7.5 NHit 1 − 0.5 − 0.5 1 Proj X 0.2 0.4 0.6 0.8 1 1.2 Clustering efficiency 1 − 0.5 − 0.5 1 Proj Z 0.2 0.4 0.6 0.8 1 1.2 Clustering efficiency

gaushit trigprim15 trigprim18 trigprim20

  • For each of the standard candles, one should check…
  • Hit finding:
  • Number of hits (rate)
  • ADC amplitude of the hits
  • Duration of the hits
  • Hit efficiency (I have this number of IDE, do I create a hit?)
  • Influence of the noise
  • Noise rate
  • Clustering / Triggering:
  • Efficiency
  • Background (noise?) rate
  • Understanding inefficiencies and differences
  • Very much trigger simulation… Not so much on the DAQ and

data flow

  • Study of compression VS noise?
  • … any other?
slide-6
SLIDE 6

Pierre Lasorak 12/04/2019

Proposal

  • Inspired by Phil’s code for hit finding templated tool in LArSoft, I started to write something similar for clustering /

triggering

  • Creates new LArSoft objects (TPC/PDS clusters) via a templated Clustering algorithm:
  • Agnostic of what hit you are using: after deconvolution or simple trigger primitive; collection / induction.
  • User can change the algorithm
  • Simulate the trigger with the triggering algorithm that gets feed vector of TPC/PDS clusters
  • User can change the algorithm
  • Does Cluster → (Op)Hit → MCParticles (→ MCTruth) associations
  • User should specify which hit are in his clusters
  • Can then be fed into an “universal” art analyser that does all the plots I was talking about earlier
  • User doesn’t need to do any work
  • Now all of DAQ can be simulated within LArSoft, rather than “cooking up” some side algorithm and have to code

the efficiency etc…

  • Also simpler to run on the grid
  • We should provide the generator FCL to run the full chain

6

slide-7
SLIDE 7

Pierre Lasorak 12/04/2019

Background / Noise

  • Noise and background treatment is a big part of triggers.
  • Should be able to check the robustness of the trigger against these 2.
  • Example: neutron rate vs the water shielding.

7

slide-8
SLIDE 8

Pierre Lasorak 12/04/2019

The problem with the 1x2x6 geometry

  • The background TF is thinking of way to get neutrons simulation right.
  • Several simulations constrains (memory, time) forbid us to simulate a full 10kT module → all what we have

shown is simulated in the 1x2x6 (smaller instrumented detector volume)

  • That’s fine for small events that have size < 1x2x6:
  • Noise estimation
  • TPC analyses
  • Event << APA (such as most of the radiological backgrounds)
  • Complexities arise when the events are bigger:
  • Neutron: Propagate long distance in the LAr (more than the 1x2x6)
  • Light: Even a small Marley event can light up big proportion of the 1x2x6 (we only consider the 2 central APA

interactions when we do triggering studies because the cluster extend to the full 1x2x6)

  • Same problems arise for other external backgrounds (cosmics?)
  • How do we scale the rate for a 10kT module?
  • “Truth studies” enough?

8

slide-9
SLIDE 9

Pierre Lasorak 12/04/2019

New geometry proposal

9

  • Discussed this is quite a lot of details at Sussex / Background TF.
  • We believe the best way forward is to instrument part of the 10kT to

run simulations (Tyler’s idea).

  • We think that solves most of our problems:
  • Neutrons / cosmic rates
  • Edge effect in photons simulations
slide-10
SLIDE 10

Pierre Lasorak 12/04/2019

Conclusion

  • Proposed a new framework for trigger algorithm

development

  • Proposed new geometries implementation in LArSoft
  • Problem with current geometries for background

10