-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add link offset to simulation #83
Merged
Merged
Changes from 20 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
7838ffa
add offset to collision
claireyywang 88fb4ab
correct collision_TEST, add offset to link
claireyywang 0ab41ec
update link pose in model
claireyywang ab93383
add all entity offset poses to frame data in kinematicsfeatures
claireyywang bca3199
add offset pose to frame
claireyywang aa0763a
testing world pose function (#80)
claireyywang d25c7ea
remove tf, use pose instead; add unit tests for GetWorldPose
claireyywang 173ca25
Merge branch 'claire/add-tf' into claire/add-pose-offset-tpeplugin
claireyywang 8d55f60
use semanticPose in SDFfeatures
claireyywang 9101bd2
include closing bracket
claireyywang f0dcf08
remove unused include statements
claireyywang 7b4254a
Merge branch 'claire/add-tf' into claire/add-pose-offset-tpeplugin
claireyywang d2a5ff5
add worldpose tests
claireyywang 9b09f0a
add link to free group
claireyywang 17ed808
add link and debug msg
claireyywang ce88d35
Merge branch 'ign-physics2' into claire/add-pose-offset-tpeplugin
claireyywang 9d4cfdc
correct framedata of model and link pose
claireyywang 633b7e2
correct test cases
claireyywang 469ae16
clean up debug msgs
claireyywang 27e368e
more clean up
claireyywang 03f78ee
add more tests
claireyywang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
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.
do we need to do something to fix the linear and angular vel?
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.
My understanding is that linear and angular velocity are tied to
model
instead oflink
, and this test case started checking the velocity oflink
after I corrected the implementation offramedata
, which is why I removed it. Before it worked because when callinglink->FrameDataRelativeToWorld()
, it was getting the velocity of the link's parent model.If we do want to add velocity for links, then that would be a different feature which allows links to move by itself.
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.
oh I see, that makes sense. Just checking, if we assume the link does not move within a model, should it inherit the parent model's velocities in world frame?
In any case, I'm not sure if there's a use case for querying a link's world velocities. We can address this when the need comes.
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.
If the link doesn't move within model, its
WorldPose
is then updated as model'sWorldPose
gets updated (since its offset will remain the same), so we probably don't have to keep track of link velocities in world frame.However, if we want the link to move within model, then we'll have to compute the link velocities with the offset. And yes, I agree that we can add this if the need comes.