-
Notifications
You must be signed in to change notification settings - Fork 138
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
2D Bounding Box messages from bounding box cameras are not bridged #457
Comments
@ahcorde Is the port to ROS Iron something the Ros_gz team will do or should I do another PR? |
@wittenator, if you want to take care of the forward port I really appreciate it otherwise I will do it this or next week. |
Sure, I don't mind doing that. I'll probably come around to it on Monday tho |
Ahh, do you know when to expect the changes reflected in the binary packages? |
I can make a release today, and changes will be available in the next humble sync. |
The humble release is not urgent for me anymore, I switched to Iron in the meantime^^ I was just curious, but thanks for the info! |
I added a PR to the Iron branch with the cherry-picked changes from the last merged PR in #460 . |
@ahcorde to close after rolling release |
PR was forward ported to Closed. Thank you @wittenator for your contributions. |
Desired behavior
There should be a bridge for the translation of 2D BBox messages coming from bounding box cameras.
Alternatives considered
None
Implementation suggestion
The corresponding ignition messages should be added. I did this in https://github.com/wittenator/ros_gz/tree/humble .
Additional context
This is useful if one wants to replace e.g. an object detection node that runs on CUDA-hardware only with a Gazebo bounding box camera to make the simulation run on any hardware.
The text was updated successfully, but these errors were encountered: