Physics Reconstruction Documentation

Basic Recipe

This is the basic recipe for reconstructing HPS data:

1.  EVIO data files are read in and converted to LCIO events.
2. The HPS Java reconstruction is run to add physics object collections to the events.
3. The events are written to an LCIO file containing results of the recon.
4. The recon LCIO file can be converted to ROOT DST Data Format.

Oftentimes, steps 1-3 are performed in the same job (process) for efficiency using the EvioToLcio command line utility.

Overview

The HPS physics reconstruction is implemented in the HPS Java project as a chain of org.lcsim Drivers which process LCIO Data Format events that are accessed using the EventHeader API.  The driver list is described in an lcsim xml steering file which is configured by the lcsim job manager.  

The EVIO Data Format is converted into LCIO by an LCSimEventBuilder such as LCSimEngRunEventBuilder.  The EvioToLcio command line tool reads EvioEvents with an EvioReader and then uses an event builder to create LCIO events representing the raw data.  The driver chain is then run to perform the physics reconstruction which will add additional object collections to the event.  The combined events with the data and recon collections are written out to an LCIO file.  The LCIO output can be converted to ROOT DST Data Format for ROOT compatibility, or it may be loaded back into HPS Java for analysis. 

Reconstruction Drivers 

The reconstruction Driver chain is defined in production steering files such as EngineeringRun2015FullRecon.lcsim, which are kept in this SVN folder and typically accessed as a class resource from a jar file.

Data Collections

Java Packages

The  HPS Java Documentation can be used to browse the packages and classes used for physics reconstruction.

HPS Java Reconstruction Packages

LCSim Packages

These lcsim packages are used extensively within the HPS Java reconstruction code.

Data Conversion

SVT data banks are handled by an SvtEvioReader and converted into RawTrackerHit and GenericObject collections.

Various modes of EVIO ECal data are converted using the EcalEvioReader.

The following collections are added to the event by the ECal reader.

• EcalReadoutHits
• FADCGenericHits
• EcalReadoutExtraDataRelations
• EcalReadoutExtraData 

The default builder will also convert and write DAQ config   information, EPICS data, and scaler bank data into the output LCSim events, if these banks are present in the EVIO data.

Track Reconstruction

These are the steps in the HPS Java track reconstruction:

1. RawTrackerHitFitterDriver converts SVT raw data into fitted hits collection by fitting ADC vs time signals.
2. DataTrackerHitDriver creates stereo hit pairs from the fitted strip hits.
3. HelicalTrackHitDriver creates 3D hits (clusters) from input stereo hits.
4. TrackerReconDriver runs track finding on the 3D hit collection.
   1. Track finding is run multiple times with different tracking strategy files, creating a track collection for each strategy.
5. The MergeTrackCollections Driver is used to merge the multiple track collections into a single output collection.
6. The GBLRefitterDriver refits the tracks using GBL.
7. TrackDataDriver adds a Generic Object collection containing additional information about the track for persistency.

The tracking packages in lcsim form the basis for HPS's tracking algorithms through usage and extension.  Seed Tracker is used for track finding using a set of input tracking strategies.  The track fit from lcsim is further refined using a Java implementation (port) of the GBL C++ algorithm.

ECal Reconstruction

These are the basic steps of the ECal reconstruction:

1. EcalRawConverterDriver converts RawTrackerHit input collection into CalorimeterHit collection using the EcalRawConverter.
2. ReconClusterDriver uses the ReconClusterer to create calorimeter Cluster collection from input hits collection.
3. CopyClusterCollectionDriver copies the clusters (with raw energies) to a different collection with a corrected energy.

The copied collection will be updated with corrected energies in the next step which creates recon particles.

Reconstructed Particles

The ReconParticleDriver creates ReconstructedParticle objects representing the final state particles from the event reconstruction.  These are tracks with matching clusters (when applicable).  It also performs vertex reconstruction and creates a number of candidate particle collections.

The ReconParticleDriver is sub-classed by the actual HpsReconParticleDriver from the steering which adds Moller candidate collections.