-
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
refactor: Backport navigation rewrite changes #2846
refactor: Backport navigation rewrite changes #2846
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2846 +/- ##
==========================================
- Coverage 47.51% 47.42% -0.09%
==========================================
Files 499 499
Lines 28292 28278 -14
Branches 13832 13831 -1
==========================================
- Hits 13442 13410 -32
- Misses 4970 4989 +19
+ Partials 9880 9879 -1 ☔ View full report in Codecov by Sentry. |
📊: Physics performance monitoring for 8b80a34physmon summary
|
untemplate nav options fix nav failure for endless bounds intersection maybe more
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.
Very nice!
…port-navigation-rewrite-changes
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.
Good to go.
In #2846 I removed a constructor parameter which was used by Athena and maybe other clients. This would classify as a breaking change. To work around that I reintroduced the parameter and marked the constructor as deprecated.
Backporting more changes from acts-project#2625 to main. This is a followup to acts-project#2768 Summary - remove overstepping from steppers - use surface tolerance for geometry lookups - add self consistency navigation test
In acts-project#2846 I removed a constructor parameter which was used by Athena and maybe other clients. This would classify as a breaking change. To work around that I reintroduced the parameter and marked the constructor as deprecated.
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 - #2846 - #2849
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
Backporting more changes from acts-project#2625 to main. This is a followup to acts-project#2768 Summary - remove overstepping from steppers - use surface tolerance for geometry lookups - add self consistency navigation test
In acts-project#2846 I removed a constructor parameter which was used by Athena and maybe other clients. This would classify as a breaking change. To work around that I reintroduced the parameter and marked the constructor as deprecated.
This PR adds a "try all" navigator which can be used as a reference to validate other navigators depends on - acts-project#2846
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
As previously removed by #2846 and then reintroduced in #3223 to keep compatibility, I propose to remove the `overstepLimit` parameter from the `EigenStepper` since it does not have any effect anymore. The propagation still handles overstepping but the hard cutoff parameter is pushed out of the stepper interface. Right now we allow overstepping of any distance. If we need a cutoff value I would suggest putting it into the navigator or propagator.
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
) As previously removed by acts-project#2846 and then reintroduced in acts-project#3223 to keep compatibility, I propose to remove the `overstepLimit` parameter from the `EigenStepper` since it does not have any effect anymore. The propagation still handles overstepping but the hard cutoff parameter is pushed out of the stepper interface. Right now we allow overstepping of any distance. If we need a cutoff value I would suggest putting it into the navigator or propagator.
Backporting more changes from #2625 to main. This is a followup to #2768
Summary