reconRootData

Introduction

Overview
logical structure
class diagram

Doxygen documentation

Introduction

The reconRootData package defines the Root classes used to store detailed reconstruction data within a Root tree file. If you desire to analyze the reconstruction data in detail, including all of the found tracks from the TkrRecon and the reconstructed energy responses from all CAL logs - then the recon ROOT file is for you.

Overview

Every Recon object contains the following:

Event Id and Run Number
A TkrRecon object - contains the full results of TKR reconstruction
- A TkrGamma object - represents a reconstructed gamma, if any.
  - A list of SSD hits, associated with the Gamma
  - A list of locators, that describes the position and direction of the reconstructed gamma
- A list of Tracks found by the reconstruction
  - A list of SSD hits associated with the track
  - A list of locators that descibe the position and direction of the track
- A list of Silicon Clusters
A CalRecon object - contains the full results of CAL reconstruction
- A list of Logs, with their reconstructed responses
- A list of CAL clusters
  - A list of CAL logs associated with this cluster.

Here is the logical structure of the reconRootData classes:

Fundamentally, the Recon ROOT Tree files contain header information - including the run and event Ids, the data from the TKR reconstruction, and the CAL reconstruction data.

The header information contains most notably the run and event ids.
Recon::getReconFlags( )->getEventId( )
Recon::getReconFlags( )->getRunId( )

The TKR reconstruction includes a list of all found tracks, all silicon clusters, and finally a list of all reconstructed gammas, if any. Each track has a list of silicon hits associated with it, as well as a list of locators. The locator lists are basically position and an associated direction vector at various positions along the track.

The CAL reconstruction data is a list of CAL logs and their reconstructed response. In addition, there is a list of CAL clusters found by the CAL reconstruction, with its own list of CAL logs that are associated with the cluster.

Here is a class diagram.