CRT Detector Simulation Andrew Olivier 7/25/2018 1 CRT Simulation - - PowerPoint PPT Presentation

CRT Detector Simulation

Andrew Olivier 7/25/2018

1

CRT Simulation Plan

2 Particle Transport

• CRT detected in largeant
• Channel mapping

Detector Simulation

• Timing
• Energy Deposit

MCTruth MCParticle CRT::Trigger Particle Generator AuxDetSimChannel CRT Decoder Trigger ↔ Track Assns artDAQ Trigger ↔ AuxDetSimChannel Assns Geometry Validation

CRT in largeant

• Started handful of 2GeV muons at -5000mm in z
• Correct channel mapping → CRT channels line up with

MCParticles

• ProtoDUNE geometry sorts by y, then z, then x
• Recommend encode detector channel in name

3

Strip Width

Distance [mm] X Y

System to Simulate

• The CRT Self-Triggers
• Reads out ALL channels when one triggers
• Read out ADCs and one timestamp per trigger

PhotoCathode PMT Anodes, PreAmp Fast Shaper Slow Shaper FPGA: OR Readout Logic: 32 us Discriminator: 80 ns 4

Detector Simulation Components

• Timing
• Readout all

channels?

• Data-taking window
• Dead time
• “Traffic Jam”?
• Energy → ADC
• Scintillator

efficiency

• Photocathode
• Amplification
• Shapers?

5

Timing Simulation

• Group hits into 62.5 MHz clock ticks
• Search windows for hits above threshold
• Readout if one channel above threshold
• Keep accepting hits for readout window
• Write data products
• CRT::Trigger represents one readout
• Assns with AuxDetSimChannel for backtracking
• Skip forward by discriminator dead time

6

Energy Simulation Strategies

• Parameterized
• Energy → PE from

calibration

• PE → ADC from

calibration

• Detailed
• Scintillator efficiency: Gaussian
• Photocathode: Poisson
• Amplification: Simulate each

anode?

• Shapers: TODO
• Birks’ Law in AuxDets?
• Noticed G4EmSaturation in optical model
• Prefer to correct as close to Geant as possible

7

Framework Data Format

• CRT::Trigger
• Get all information at
• nce
• Have to associate Track

with entire readout

• Fully encapsulates one

module readout → simpler

• CRT::Hit ↔ Trigger

Associations

• Don’t have to access

Hits

• Can create CRT::Hit ↔

recob::Track Assns

• Have to access Assns →

adds complexity

CRT::Trigger CRT::Hit CRT::Hit CRT::Hit raw::ExternalTrigger A s s n s CRT::Hit Assns CRT::Hit A s s n s CRT::Hit 8

Output: What to Expect

• CRT::Trigger
• Module number = AuxDet ID
• Timestamp
• CRT::Hit
• Channel number = AuxDetSensitive ID
• ADC value
• Assns CRT::Trigger ↔ AuxDetSimChannel
• Backtracking handle if we need it

9

Future Plans

• Energy simulation
• Only use ADC for muon selection?
• Parameterized for now
• Quantitative reason for complex model?
• “Traffic jam” simulation?
• Understand timing better
• Cable lengths
• Read out “empty” Triggers when ADC busy?
• How often are tokens sent out?

10

Backup: Minimize Framework Coupling

• Motivation
• Start testing software during commissioning
• Later: gallery-powered monitoring?
• Implementation
• Data product in separate repository
• Algorithms in separate repository
• Coupled to data product
• Some geometry queries outside of framework?

11

Overview of CRT Hardware

12 From Ed Blucher’s Collaboration Meeting slides

• Left: 2 layers of 32 channels that are offset by ~25mm
• Right: 4 frames with 4 modules each on front and back of cryostat

CRT in the GDML File

• dunetpc

v06_76_00

• Single frame on

front and back of cryostat → Need 4

• Modules’

dimensions look correct

13

Backup: Visualization of CRT

14

• Short red strips are my interpretation of CRT simulation channels
• Want to map channel to position and look energy and timing