You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current CKFProcessor runs track finding for every seed. This results in a large number of duplicate tracks, particularly in the recoil tracker when using realistic seeding.
Describe the solution you'd like
We would like to implement an ambiguity resolution algorithm (possibly multiple types) to remove duplicate tracks.
Describe alternatives you've considered
Newer versions of ACTS do already have ambiguity resolution algorithms implemented, but tracking is currently based on an older version of ACTS that does not have those algorithms. We could switch to using the newest ACTS version, and use their ambiguity solvers directly. For now, to avoid dealing with the other problems that will likely come from that ACTS switch, and to allow for more flexibility when testing these algorithms, I think implementing them separately in ldmx-sw makes sense.
The text was updated successfully, but these errors were encountered:
The current
CKFProcessor
runs track finding for every seed. This results in a large number of duplicate tracks, particularly in the recoil tracker when using realistic seeding.Describe the solution you'd like
We would like to implement an ambiguity resolution algorithm (possibly multiple types) to remove duplicate tracks.
Describe alternatives you've considered
Newer versions of ACTS do already have ambiguity resolution algorithms implemented, but tracking is currently based on an older version of ACTS that does not have those algorithms. We could switch to using the newest ACTS version, and use their ambiguity solvers directly. For now, to avoid dealing with the other problems that will likely come from that ACTS switch, and to allow for more flexibility when testing these algorithms, I think implementing them separately in ldmx-sw makes sense.
The text was updated successfully, but these errors were encountered: