-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add TryAllOverstepNavigator
#2850
feat: Add TryAllOverstepNavigator
#2850
Conversation
📊: Physics performance monitoring for 0c93c4bphysmon summary
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2850 +/- ##
==========================================
+ Coverage 47.43% 47.46% +0.02%
==========================================
Files 510 510
Lines 30053 30198 +145
Branches 14564 14639 +75
==========================================
+ Hits 14257 14332 +75
- Misses 5323 5335 +12
- Partials 10473 10531 +58 ☔ View full report in Codecov by Sentry. |
TryAllOverstepNavigator
5a2ab0a
to
eb74c80
Compare
99b02e3
to
87ea1bc
Compare
87ea1bc
to
c96277c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a comment regarding potential code sharing, I won't insist on any of this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
This PR adds another "try all" navigator which deliberately oversteps and runs intersections backwards. It can be used as a reference to validate other navigators. The idea of intersecting backwards is to have a better approximation with the helix. Instead of using the tangent we will use a ray that goes through the trajectory twice. depends on - acts-project#2846 - acts-project#2849
After acts-project#2849 and acts-project#2850 it is time to update the documentation of our navigators. I also included a line about the `DetectorNavigator`. blocked by - acts-project#2850
This PR adds another "try all" navigator which deliberately oversteps and runs intersections backwards. It can be used as a reference to validate other navigators. The idea of intersecting backwards is to have a better approximation with the helix. Instead of using the tangent we will use a ray that goes through the trajectory twice. depends on - acts-project#2846 - acts-project#2849
After acts-project#2849 and acts-project#2850 it is time to update the documentation of our navigators. I also included a line about the `DetectorNavigator`. blocked by - acts-project#2850
## Issue The test-time for build_debug grew significantly after: - #2849 - #2850 Before: ``` Start 127: Navigator 127/239 Test #127: Navigator ............................ Passed 22.29 sec ``` TryAllNavigator: ``` Start 128: Navigator 128/240 Test #128: Navigator ............................ Passed 1041.82 sec ``` TryAllOverstepNavigator: ``` Start 128: Navigator 128/240 Test #128: Navigator ............................ Passed 3994.42 sec ``` ## Possible Solution This PR reduces the number of tests with the try-all-references from 500 to 10. This results in a test time of around 200 sec. Maybe we should adapt the test in the future to get more tests in a similar time.
This PR adds another "try all" navigator which deliberately oversteps and runs intersections backwards. It can be used as a reference to validate other navigators. The idea of intersecting backwards is to have a better approximation with the helix. Instead of using the tangent we will use a ray that goes through the trajectory twice. depends on - acts-project#2846 - acts-project#2849
After acts-project#2849 and acts-project#2850 it is time to update the documentation of our navigators. I also included a line about the `DetectorNavigator`. blocked by - acts-project#2850
) ## Issue The test-time for build_debug grew significantly after: - acts-project#2849 - acts-project#2850 Before: ``` Start 127: Navigator 127/239 Test acts-project#127: Navigator ............................ Passed 22.29 sec ``` TryAllNavigator: ``` Start 128: Navigator 128/240 Test acts-project#128: Navigator ............................ Passed 1041.82 sec ``` TryAllOverstepNavigator: ``` Start 128: Navigator 128/240 Test acts-project#128: Navigator ............................ Passed 3994.42 sec ``` ## Possible Solution This PR reduces the number of tests with the try-all-references from 500 to 10. This results in a test time of around 200 sec. Maybe we should adapt the test in the future to get more tests in a similar time.
This PR adds another "try all" navigator which deliberately oversteps and runs intersections backwards. It can be used as a reference to validate other navigators.
The idea of intersecting backwards is to have a better approximation with the helix. Instead of using the tangent we will use a ray that goes through the trajectory twice.
depends on
TryAllNavigator
#2849