Changes for unified configuration of VeloClusterTrackingSIMD
Closes Rec#299 (closed)
@ahennequ Is there any situation when one wants to have a different algorithm for hits and tracks? This MR would make it harder to do so (but avoid mistakes with the much more common case).
Needs: Alignment!238 (merged) and MooreAnalysis!76 (merged)
Merge request reports
Activity
added RTA label
@ahennequ Is there any situation when one wants to have a different algorithm for hits and tracks? This MR would make it harder to do so (but avoid mistakes with the much more common case).
I don't think so. Enforcing that the hits and tracks come from the same algorithm is a good thing.
- Resolved by Rosen Matev
@msaur This can be tested
assigned to @msaur
added ci-test-triggered label
mentioned in issue Rec#299 (closed)
- [2022-03-14 13:38] Validation started with lhcb-master-mr#3971
- [2022-03-15 13:59] Validation started with lhcb-master-mr#3987
- [2022-03-16 09:03] Validation started with lhcb-master-mr#3994
Edited by Software for LHCbmentioned in merge request MooreAnalysis!76 (merged)
mentioned in merge request Alignment!238 (merged)
- [2022-03-16 16:16] Validation started with lhcb-master-mr#3998
- [2022-03-16 16:28] Validation started with lhcb-master-mr#4001
Edited by Software for LHCbassigned to @rmatev
mentioned in commit 5bf9c955
added Tracking enhancement labels
removed enhancement label
added cleanup label
mentioned in issue #411 (closed)