-
Notifications
You must be signed in to change notification settings - Fork 429
Added frame_id to Joint State Broadcaster #1746
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
Conversation
Signed-off-by: Jakub Delicat <delicat.kuba@gmail.com>
Signed-off-by: Jakub Delicat <delicat.kuba@gmail.com>
saikishor
left a comment
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.
@delipl you have access to the URDF model in the joint state broadcaster. Why not use it to get its root link and publish by default, instead of setting a custom frame_id from the user?
AFAIK, the visualization is same irrespective of the type of the frame you choose. Am I right?
Good point. I can change the frame id to the root of the urdf. Edit: |
Sure. But for Jazzy upon we have a URDF Model. May be you can use these changes to open another PR for Humble, but for this one, please use the URDF root link |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1746 +/- ##
==========================================
- Coverage 86.30% 86.29% -0.01%
==========================================
Files 123 123
Lines 11942 11948 +6
Branches 995 996 +1
==========================================
+ Hits 10306 10310 +4
- Misses 1333 1334 +1
- Partials 303 304 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@saikishor what if we merge this as-is as a first version, backport all the way to humble and then modify things to use the URDF instead? Is there any chance you'd want to not use the absolute root of the URDF? |
@bmagyar I checked locally, it is not directly backportable, so I opened a new PR : #1751 cherry-picking @delipl's changes and refining a bit.
I don't think the RViZ2 visualization changes based on the frame_id. I think it only check that it should be a valid frame |
bmagyar
left a comment
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.
Thank you!
|
Is it right that this is not backported and released via Jazzy binaries yet? |
(cherry picked from commit fc576ee)
Added
frame_idparameter to fill thejoint_statesmessage in the Joint State Broadcaster. Thanks to this parameter rviz2 allows to visualize the effort of the joints.