Skip to content

ROS2: Understand TF tree: camera_optical VS camera_optical/static #4353

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

Open
AmitNativ1984 opened this issue Feb 15, 2022 Discussed in #4352 · 0 comments
Open

ROS2: Understand TF tree: camera_optical VS camera_optical/static #4353

AmitNativ1984 opened this issue Feb 15, 2022 Discussed in #4352 · 0 comments
Labels
bug-report for issues filed as bug reports ros

Comments

@AmitNativ1984
Copy link

Discussed in #4352

Originally posted by AmitNativ1984 February 15, 2022
Problem:
I have created a stereo camera by setting up left and right cameras in the settings file, from which I want to calculate depth.
I use ros2 tf to find the baseline between the left and right cameras.
The camera_info->header.frame_id for left and right cameras, is left_stereo_camera_optical and right_stereo_camera_optical respectively.
However, looking in rviz, I see the relative distance between the optical frames is incorrect. Instead, the frame called left_stereo_camera_optical/static and right_stereo_camera_optical/static are positioned correctly.
This is a problem because camera_info reports the optical frame, rather than optical/static frame, and these are the frames used in tf lookupTransform.

Screenshot from 2022-02-15 15-41-51

Also, the TF tree looks strange. I would expect the optical frame to be the child frame of the odom_local_ned.

frames

I would appreciate some help to understand what's going on.
Thanks!

@jonyMarino jonyMarino added bug-report for issues filed as bug reports ros labels Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-report for issues filed as bug reports ros
Projects
None yet
Development

No branches or pull requests

2 participants