Fast tracking mode #1092
Fast tracking mode #1092
Conversation
…ajectory and pulls. It no longer needs to inherit from DTrackingData.
…ny methods to try to handle all sorts of edge conditions. Most of the time only one or two of the same subset of methods actually worked; the rest just wasted cpu cycles for marginal or no additional benefit.
…ever enabled after it was made optional because the hypothesis list is handled at the time-based stage. (2) Use candidates to find estimates for t0. (3) remove code that swims to gather up hits. The hit lists obtained at the candidate stage are sufficient.
…ed object to the list of fitted tracks.
…mmand-line flag. Moved code to copy from wire-based objects to time-based objects into separate method.
… estimates for t0.
…ent lines and fix some typos.
…s doing time-based racking or in the fast tracking mode.
|
Test status for this pull request: SUCCESS Summary: /work/halld/pull_request_test/halld_recon^FastTrackingMode/tests/summary.txt Build log: /work/halld/pull_request_test/halld_recon^FastTrackingMode/make_FastTrackingMode.log |
|
Test status for this pull request: SUCCESS Summary: /work/halld/pull_request_test/halld_recon^FastTrackingMode/tests/summary.txt Build log: /work/halld/pull_request_test/halld_recon^FastTrackingMode/make_FastTrackingMode.log |
This PR introduces a special tracking mode that favors speed over resolution/accuracy. This optional code skips the wire-based+time-based tracking sequence and instead performs a modified wire-based fit that uses an estimate for t0 by matching track candidates to start counter or BCAL hits so that CDC drift times can be used in the kalman filter. Only the proton and pion mass hypotheses are used. To use this mode, set -PTRKFIT:FAST_TRACKING_MODE=1. By default this mode is disabled.