Class CosmicTrackBuilder

Inheritance Relationships

Base Type

Class Documentation

class CosmicTrackBuilder : public larflow::reco::TrackClusterBuilder

Build cosmic tracks by connecting track clusters end-to-end.

Built on the class TrackClusterBuider, which treats the connection of track clusters in a graph-traversal manner.

This is dedicated to reconstructing cosmic muon tracks. It doesn’t aim so much for accuracy, but by trying to look for segments which are plausibly attached to the edge of the detector. This allows it to be used to veto candidate vertices as likely cosmic.

Public Functions

CosmicTrackBuilder()
virtual ~CosmicTrackBuilder()
void process(larcv::IOManager &iolcv, larlite::storage_manager &ioll)

Process the event data in the IO managers.

The data expected in the IO managers are:

    • larflowcluster of track clusters
    • corresponding principle components for the track clusters
    • keypoints stored in the form of larflow3dhit(s)

The output will be a container of larlite::track instances.

    • larlite::tracks of muons that touch the space charge boundary
  • and are shifted in ‘x’ to be on the boudnary. [default tree name: boundarycosmic]
    • larlite::tracks of muons that tourch the space charge boundary [defaul: boundarycosmicnoshift ]
    • larlite::tracks of contained muons [ default: containedcosmic ]

Parameters
  • iolcv: LArCV IO manager where we get event data
  • ioll: larlite IO manager where we get data and store outputs

void do_boundary_analysis(bool doit)

set flag that if true, runs the boundary analysis

Protected Functions

void _boundary_analysis_wflash(larlite::storage_manager &ioll)

boundary analysis of tracks found, using flash

[deprecated]

Parameters
  • ioll: larlite IO manager

void _boundary_analysis_noflash(larlite::storage_manager &ioll)

boundary analysis of reconstructed tracks

we try 3 types of shifts to the boundary in order to estimate a t0 of the track we use the boundary shifts to:

  1. proposed t0 is compared to the flash times of opflashes, to look for possible matches
  2. tag track as boundary muon, if both ends are near a boundary (through-going muon)

Parameters
  • ioll: IO manager to store output tracks

Protected Attributes

bool _do_boundary_analysis

if true, split found tracks into boundary and contained tracks