MultiAdaptiveBeamMapping: Better collision model topology (and fix 3instruments_collis.scn) #203
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fredroy
added
pr: fix
pr: status to review
bakpaul
approved these changes
Sep 18, 2025
hugtalbot
added
pr: status ready
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on
The "full deployment" 3instruments_collis.scn was like this:
We can see that some collsion edges are missing.
The problem is that the topology built by the MultiAdaptiveBeamMapping does not contain enough DOFs for the submappings. It was simply using the tool with the most discretization, which is wrong.
So this PR fixes that by computing the worst case (all the tools are deployed fully)
Note that it will induce more collision detection though (as there are more collision edges and points).
And the regressions will need to be re-generated 😿