Update to seed finder distance parameter

[bschmookler]

Briefly, what does this PR introduce?

This updates the parameter which defines the max distance in r between middle and top SP in a given seed. This removes some minor inefficiencies for |z| > ~50mm at certain eta values, as discussed here. Since the beam diamond extends out to 80-100mm, this allows efficient seed finding over the whole range.

Results for single negative muons generated at with p = [0.5,20]GeV/c and (vx,vy,vz) = (0,0,50mm)

Before:

After:

The results look similar for particles generated at vz = 75mm.

For particles generated at (vx,vy,vz) = (0,0,0), for example, there is no observed difference in the solved tracks (i.e. tracks after the ambiguity solver). The number of found seeds and unsolved tracks increases as expected.

What kind of change does this PR introduce?

• Bug fix (issue #__)
• New feature (issue #__)
• Documentation update
• Other: Update to seed finder configuration

Please check if this PR fulfills the following:

• Tests for the changes have been added
• Documentation has been added / updated
• Changes have been communicated to collaborators @Jeet-bhai

Does this PR introduce breaking changes? What changes might users need to make to their code?

No

Does this PR change default behavior?

Yes, small improvement to tracking efficiency

[github-actions]

Capybara summary for PR 1586

• rec_dis_10x100_minQ2=0_craterlake
• rec_dis_10x100_minQ2=1000_craterlake_tracking_only
• rec_dis_18x275_minQ2=0_craterlake
• rec_dis_18x275_minQ2=1000_craterlake
• rec_dis_5x41_minQ2=0_craterlake
• rec_e_1GeV_20GeV_craterlake
• rec_pi_1GeV_20GeV_craterlake
  ^{_{Last updated 2024-08-22T16:38-04:00 9dd34f6}}

[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