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.

Sign up for GitHub

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

Jump to bottom

Why is child_frame_id not set for 'odom_msg' (and 'ground_truth_msg') in stageros.cpp? #57

Open
sayali-purdue opened this issue Sep 23, 2019 · 0 comments
Open

Why is child_frame_id not set for 'odom_msg' (and 'ground_truth_msg') in stageros.cpp? #57

sayali-purdue opened this issue Sep 23, 2019 · 0 comments

Comments

@sayali-purdue
Copy link

sayali-purdue commented Sep 23, 2019 •
edited
Loading

nav_msgs::Odometry defintion states that twist data should be specified in the coordinate frame given by child_frame_id.

'odom_msg' (and 'ground_truth_msg') variable in stageros.cpp is of type nav_msgs::Odometry and contains twist data. Since, child_frame_id is not set, which co-ordinate frame does the twist data belong to? Also, I would like to know why is the ROS datatype definition not followed here.

Looking forward to your response.
@sayali-purdue sayali-purdue changed the title Why is child_frame_id not set for 'odom_msg' in stageros.cpp? Why is child_frame_id not set for 'odom_msg' (and 'ground_truth_msg') in stageros.cpp? Sep 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sayali-purdue