Skip to content

Latest commit

 

History

History
24 lines (14 loc) · 1.78 KB

README.md

File metadata and controls

24 lines (14 loc) · 1.78 KB

Hit-Finding

A generic hit finding application that currently accepts streams of raw ADC information for multiple channels, and does the following:

  1. Reads in and downsamples the waveform(s) if required.
  2. Does basic pedestal finding and subtraction on the raw waveform.
  3. Applies a simple Finite-Impulse-Response (FIR) filter to the waveform.
  4. The result of passing the raw waveform through the sequence above is passed to the hit_finding() function, which returns a list of hits for each channel.
  5. All of the above is handled by the function find_hits() in the main script. It returns a collection of lists of hits, one for each pseudochannel passed.

Basic Simulation Test

The hit finder is desinged to be pulse shape independent, and is based on the LArSoft DUNE implementation for TPC hit finding. The attempt there was to mimic the hit finding proceudure in the readout subsystem of the DUNE Data Acquisition System (DAQ). The basic simulation test will generate several waveforms of size O(10k) samples, of a 'random-walk' style and pass them through the full sequence above to check hits are being generated.

An example of a raw waveform, it's calculated pedestal, the pedestal subtracted waveform, and it's calculated pedestal are shown here.

This is an image

Data Test

The DAPHNE boards will provide the hits to the DUNE DAQ software. For now, we can process the sample waveforms to do some simple hit finding and use these to pass to the trigger stream in DUNE DAQ offline, for PDS trigger stream testing. Going by the following figure, we still need to introduce the signal_kill and IQ ranges found to estimate the variance which informs the hit finding ADC threshold parameter.

This is an image