Preserve base link in body transform on clone#1540
Open
rschlaikjer wants to merge 1 commit intoproductionfrom
Open
Preserve base link in body transform on clone#1540rschlaikjer wants to merge 1 commit intoproductionfrom
rschlaikjer wants to merge 1 commit intoproductionfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If a kinbody is created via
InitFromKinBodyInfo, and the base link in that body has a non-zero transform, then openrave will correctly track that offset.However, if you then clone that body, the offset is currently lost, resulting in surprising behaviour in clone envs. Similarly, if you init a kinbody from a set of link infos, it doesn't respect base link offset.
Fix cloning and
InitWithInitialLinksto preserve/initialize the base link offset for consistency.Tests:
https://tiny.mujin.co.jp/hra7d
https://tiny.mujin.co.jp/lx3jg