-
Notifications
You must be signed in to change notification settings - Fork 176
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
fix: Fix boundaries navigation #2534
fix: Fix boundaries navigation #2534
Conversation
What if we slightly overstep onto a boundary surface? Then we want to go backwards to get to it, don't we? |
That should still be the case. When we target a boundary the navigator will try to reach it and handle overstepping. But when we look up boundaries after we changed volumes we do not want to look back I think |
This fails the global |
Codecov Report
@@ Coverage Diff @@
## main #2534 +/- ##
=======================================
Coverage 49.64% 49.64%
=======================================
Files 471 471
Lines 26632 26632
Branches 12237 12237
=======================================
Hits 13222 13222
Misses 4742 4742
Partials 8668 8668
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
While debugging #2534 I encountered a few problems with the GX2F test which I try to fix here. - make volume big enough to fit all the surfaces - introduce envelope - remove volume material - lower case variable name
I encountered looping navigation between boundary surfaces as we do the lookup with overstep limit.
I believe we do not want to look for any boundaries that are behind us? But I might overlook something
Pulled this out of #2518
blocked by
Particle
and simulation surface aware #2546