A separate class for each track finding algorithm
Different algorithms for track finding (for the moment highestCharge
, pads
and bestChi2
) are at the moment all in the Tracking
class. They should be moved each to their own class, maybe all subclass of a single TrackFinding
class. The actual track finding should be a function findBestTrack
in the class. The class should take somewhere a RechitEvent
as input.
Specific parameters for the algorithm should be added to the geometry xml file. A new tag called <tracking>
should be defined to select the tracking algorithm name (that already exists) and its parameters. The parameters should be automatically added to a configuration map in the TrackFinding
subclass or in the SetupGeometry
class.
Adding new algorithms (using new parameter names in the geometry file as well) should be made easy enough and require minimal modifications to SetupGeometry
. If modifications to CMakeLists.txt
are required, they should be documented.
This likely requires the Tracking
class to be better structured (referred to in issue #38).
Addressed in !14 (merged) .