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

tf echo use wrong terminology for source and target frame #226

Closed
Hugal31 opened this issue May 11, 2021 · 2 comments
Closed

tf echo use wrong terminology for source and target frame #226

Hugal31 opened this issue May 11, 2021 · 2 comments

Comments

@Hugal31
Copy link

Hugal31 commented May 11, 2021

Same as with the equivalent issue on tf2:

tf_echo takes two arguments, in order source and target, which gives the transformation from source to target, while the tf and tf2 API always gives the transformation from target to source (to transform coordinates in source frame to coordinates in target frame).

Indeed, it calls TransformListnener::lookupTransform with the wrong argument names: it calls with source_frame, then the target_frame, whereas the function takes target_frame first.

I suggest to rename the two arguments so the API remains compatible.

@tfoote
Copy link
Member

tfoote commented May 14, 2021

Duplicate of #111 and #108

Echo is designed for debugging the publishing of transforms. lookupTransform is for transforming data. The transform from Frame A to B is the inverse of the transform to move data from A to B.

@ros-discourse
Copy link

This issue has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/nomenclature-of-tf-echo-and-tf-listener/36985/7

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

No branches or pull requests

3 participants