refactor!: Template on track container frontend `TrackContainer`
blocked by
- https://github.com/acts-project/acts/pull/3192
📊: Physics performance monitoring for 1bbfb643f2f2d11cea1439bbd3f7f97d5bb9d8d4
physmon summary
- ✅ Particles fatras
- ✅ Particles geant4
- ✅ Particles ttbar
- ✅ Vertices ttbar
- ✅ Truth tracking (KF)
- ✅ Truth tracking (GSF)
- ✅ Truth tracking (GX2F)
- ✅ CKF | trackfinding | single muon | truth smeared seeding
- ✅ Track Summary CKF | trackfinding | single muon | truth smeared seeding
- ✅ Seeding trackfinding | single muon | truth estimated seeding
- ✅ CKF | trackfinding | single muon | truth estimated seeding
- ✅ Track Summary CKF | trackfinding | single muon | truth estimated seeding
- ✅ Seeding trackfinding | single muon | default seeding
- ✅ CKF | trackfinding | single muon | default seeding
- ✅ Track Summary CKF | trackfinding | single muon | default seeding
- ✅ Seeding trackfinding | single muon | orthogonal seeding
- ✅ CKF | trackfinding | single muon | orthogonal seeding
- ✅ Track Summary CKF | trackfinding | single muon | orthogonal seeding
- ✅ Seeding trackfinding | 4 muon x 50 vertices | default seeding
- ✅ CKF | trackfinding | 4 muon x 50 vertices | default seeding
- ✅ Track Summary CKF | trackfinding | 4 muon x 50 vertices | default seeding
- ✅ Ambisolver | trackfinding | 4 muon x 50 vertices | default seeding
- ✅ IVF notime | trackfinding | 4 muon x 50 vertices | default seeding
- ✅ AMVF gauss notime | trackfinding | 4 muon x 50 vertices | default seeding
- ✅ AMVF grid time | trackfinding | 4 muon x 50 vertices | default seeding
- ✅ Seeding trackfinding | ttbar with 200 pileup | default seeding
- ✅ CKF | trackfinding | ttbar with 200 pileup | default seeding
- ✅ Track Summary CKF | trackfinding | ttbar with 200 pileup | default seeding
- ✅ Ambisolver | trackfinding | ttbar with 200 pileup | default seeding
- ✅ AMVF gauss notime | trackfinding | ttbar with 200 pileup | default seeding
- ✅ AMVF grid time | trackfinding | ttbar with 200 pileup | default seeding
My primary reason was to break the template param dependency chain a bit. For example the fitters / finder / ambi res should not have to carry through the holder type and the mutability flag.
Concepts would be great here I think! In principle the user should be able to create their own high level track container and proxy objects. Not sure if this is useful but I think the decoupling would be nice.
I think this one is actually not critical at all for v36 btw. I am happy to push this a bit further if we cannot make it until we want to cut the major release.
Yes I think that would make it solid. Will do
This still has some CI failures, and unfortunately also picked up conflicts now. Can you fix them @andiwand ?
:white_check_mark: Athena integration test results [1e855a2fdf06ab7834d83b08eb08869dd011ae1a]
:white_check_mark: All tests successful
Quality Gate passed
Issues
6 New issues
0 Accepted issues
Measures
0 Security Hotspots
88.9% Coverage on New Code
0.0% Duplication on New Code