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

Incompatibility between messages for different ROS distros #54

Closed
silasalves opened this issue Jan 15, 2021 · 2 comments
Closed

Incompatibility between messages for different ROS distros #54

silasalves opened this issue Jan 15, 2021 · 2 comments

Comments

@silasalves
Copy link

I noticed that some messages (in my case, Detection2D) is different on ROS Melodic and Noetic:

Melodic Noetic
std_msgs/Header header
vision_msgs/ObjectHypothesisWithPose[] results
vision_msgs/BoundingBox2D bbox
sensor_msgs/Image source_img


std_msgs/Header header
vision_msgs/ObjectHypothesisWithPose[] results
vision_msgs/BoundingBox2D bbox
sensor_msgs/Image source_img
bool is_tracking
string tracking_id

Is there a reason for omitting is_tracking and tracking_id on Melodic? I installed the package using APT, but I could also clone this repo in my workspace in case I need the tracking messages in the future.

@Kukanani
Copy link
Collaborator

is_tracking and tracking_id were added after melodic was released, and we have a general rule in the ROS community to not change message definitions after a distro release, because this causes md5 compatibility issues (the message has to be rebuilt everywhere). Therefore, the fields were added in noetic but not earlier versions.

Please note that the tracking fields are going away or being renamed in newer versions of this package (#50)

@silasalves
Copy link
Author

Thanks a lot for the heads-up!

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

2 participants