Fix CHOMP DistanceFieldManager field generation to properly disable other kinbodies #315
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.
When the CHOMP module computes a distance field attached to a kinbody, it does not internally disable other kinbodies during collision checking (this enables multiple bodies to be included in one field, which you often want). However, the
DistanceFieldManager
assumes that there is one field per kinbody ... but when generating that field, it was not properly disabling other kinbodies. This led to incorrect fields and poor CHOMP performance inprpy
. This PR fixes this bug.