feat: Memory dense MeasurementContainer for Examples

[andiwand]

• Implement a MeasurementContainer which packs the numbers densely
• Implement proxy types to read and write from/to the container
• Handle all downstream changes

The motivation for this is to use the memory efficiently and potentially improve track finding performance in the Examples framework.

blocked by

• refactor: Rework projector #3529

[github-actions]

📊: Physics performance monitoring for 7ea7bab

Full contents

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

[andiwand]

This seems to be about 1% faster but that is also very close to the measurement precision

[andiwand]

single ttbar event with PU 200 and Fatras and ODD

main

Number of measurements: 60163
Size of measurements: 22621288

changed

Number of measurements: 60163
Size of measurements: 7696227

22,6 MB -> 7,7 MB ~ factor 3

compared to the track edm

Track State memory statistics (averaged):
other:
               count: 17111.000000
               index:     0.91M
             parPred:     0.78M
             covPred:     4.70M
             parFilt:     0.78M
             covFilt:     4.70M
             parSmth:     0.78M
             covSmth:     4.67M
                meas:     0.00M
          measOffset:     0.07M
             measCov:     0.00M
       measCovOffset:     0.07M
                 jac:     4.70M
         sourceLinks:     0.39M
          projectors:     0.00M
               total:    22.55M
meas:
               count: 16938.00
               index:     0.90M
             parPred:     0.78M
             covPred:     4.65M
             parFilt:     0.78M
             covFilt:     4.65M
             parSmth:     0.76M
             covSmth:     4.58M
                meas:     0.28M
          measOffset:     0.06M
             measCov:     0.70M
       measCovOffset:     0.06M
                 jac:     4.65M
         sourceLinks:     0.78M
          projectors:     0.13M
               total:    23.77M

given

Number of tracks: 1321
Number of track states: 34049

it looks like we have to add them up. also this will not contain any track information but that only scales with 1321 which is not significant here.

~ 50 MB track edm
~ 22,6 MB measurement edm before
~ 7,7 MB measurement edm after

[benjaminhuth]

A few comments, none of them critical. I think just a little bit of documentation would be good.

[benjaminhuth]

Looks good to me!

[sonarqubecloud]

Quality Gate passed

Issues
12 New issues
0 Accepted issues

Measures
0 Security Hotspots
53.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[acts-project-service]

✅ Athena integration test results [8c91d41]

✅ All tests successful

status	job	report
🟢	report_pull_request
🟢	run_art_test: test_data18_13TeV_1000evt
🟢	run_art_test: test_ttbarPU40_reco
🟢	test_ActsDumpGeometryIdentifiers
🟢	test_ActsCheckObjectCountsCachedWorkflow
🟢	test_ActsCheckObjectCountsWorkflow
🟢	test_ActsEFTrackFit
🟢	test_ActsPersistifySeeds
🟢	test_ActsBenchmarkWithSpot
🟢	test_ActsAnalogueClustering
🟢	test_ActsWorkflowHeavyIons
🟢	test_ActsWorkflowFastTracking
🟢	test_ActsWorkflowCached
🟢	test_ActsWorkflow
🟢	test_ActsValidateAmbiguityResolution
🟢	test_ActsValidateResolvedTracks
🟢	test_ActsValidateTracks
🟢	test_ActsValidateActsCoreSpacePoints
🟢	test_ActsValidateActsSpacePoints
🟢	test_ActsValidateSeeds
🟢	test_ActsValidateOrthogonalSeeds
🟢	test_ActsValidateClusters
🟢	test_ActsPersistifyEDM
🟢	test_ActsGSFRefitting
🟢	test_ActsKfRefitting
🟢	test_ActsExtrapolationAlgTest
🟢	test_ActsITkTest
🟢	run_workflow_tests_run4_mc
🟢	run_workflow_tests_run2_mc
🟢	run_workflow_tests_run2_data
🟢	run_workflow_tests_run3_mc
🟢	run_workflow_tests_run3_data
🟢	run_unit_tests