Double matching condition for track finding effieicny

[beomki-yeo]

Based on #692

Double matching condition:

1. The number of measurements from the major particle is larger than a half of the number of the measurements of the found track
2. The number of measurements from the major particle is larger than a half of the number of measurements produced by the particle

We have been only using the first condition. This PR adds the second one.

Relevant ACTS code can be found here: https://github.com/acts-project/acts/blob/f935e2512cc72577eb9aa9934a6f7b52f4c0dd53/Examples/Algorithms/TruthTracking/ActsExamples/TruthTracking/TrackTruthMatcher.cpp#L105

As expected, the efficiency drops but not so much

Before

After

[beomki-yeo]

This is the final PR before creating the tag...

[krasznaa]

Way to scare be in the home stretch... 😟

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[beomki-yeo]

The plot gets more sense now...

single muon events

Before with the bug in division

After fixing the bug

[beomki-yeo]

The recovery at eta~0 makes sense:
As the track is orthogonal to the module, the cluster size (# number of cells) are usually small so the hit count sum frequently gets smaller than the measurements size which makes the value of division zero

[krasznaa]

Fine. Let's make the tag finally.