Skip to content
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 the possibility to change the baseframe in the visualizer #93

Merged
merged 3 commits into from
Feb 11, 2025

Conversation

GiulioRomualdi
Copy link
Member

Thanks to this PR the user will be able to change the base on the visualizer. This is useful if someone wants to use signals as a base pose — for instance, waist imu-base orientation.

This is an example of usage

imu_base.mp4

Caution

This PR needs robotology/idyntree#1229

@traversaro
Copy link
Contributor

I am a a bit confused by the video. If I am not wrong, waist_imu_0 is an additional frame, so passing as base_link is not valid. Are you sure that the visualizer works as intended or perhaps it is still using the base_link as base link?

@GiulioRomualdi
Copy link
Member Author

I am a a bit confused by the video. If I am not wrong, waist_imu_0 is an additional frame, so passing as base_link is not valid. Are you sure that the visualizer works as intended or perhaps it is still using the base_link as base link?

Here we can pass whichever frame we want since the fixed transformation between the link and frame is kept in the visualizer and used as additional transformation

else:
base_frame_index = model.getFrameIndex(base_frame)
frame_T_base = model.getFrameTransform(base_frame_index)
frame_T_base = frame_T_base.inverse().asHomogeneousTransform()
self.frame_T_base = frame_T_base.toNumPy()

@traversaro
Copy link
Contributor

I am a a bit confused by the video. If I am not wrong, waist_imu_0 is an additional frame, so passing as base_link is not valid. Are you sure that the visualizer works as intended or perhaps it is still using the base_link as base link?

Here we can pass whichever frame we want since the fixed transformation between the link and frame is kept in the visualizer and used as additional transformation

else:
base_frame_index = model.getFrameIndex(base_frame)
frame_T_base = model.getFrameTransform(base_frame_index)
frame_T_base = frame_T_base.inverse().asHomogeneousTransform()
self.frame_T_base = frame_T_base.toNumPy()

Ah thanks, it was not clear to me!

@traversaro
Copy link
Contributor

This PR needs robotology/idyntree#1229

This is released in iDynTree 13.3.0 .

@GiulioRomualdi GiulioRomualdi merged commit 1353f17 into main Feb 11, 2025
9 checks passed
@GiulioRomualdi GiulioRomualdi deleted the base_pose branch February 11, 2025 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants