-
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: Remove target estimation from navigator #2598
refactor: Remove target estimation from navigator #2598
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2598 +/- ##
==========================================
- Coverage 49.53% 49.51% -0.02%
==========================================
Files 472 472
Lines 26732 26684 -48
Branches 12321 12291 -30
==========================================
- Hits 13241 13212 -29
- Misses 4753 4759 +6
+ Partials 8738 8713 -25
... and 10 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn 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.
And the idea is to have this functionality fully contained in the surface aborter?
the code I remove here is trying to estimate the target layer and volume based on an intersection with the target surface. this is done several times during navigation since this estimate could change. I do not think that is it necessary to estimate those and if the user wants to decrease navigation candidates the target layer or volume should be provided directly |
this is addressed in #2625 |
This is very unintuitive and might result in unwanted behavior