You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As there exists the message sensor_msgs/RegionOfInterest, we should remove our mas_perception_msgs/BoundingBox2D in favor of the built-in option.
This will affect mas_perception_msgs/Plane, and potentially mdr_place_action, since it uses the limits field in mas_perception_msgs/Plane of type mas_perception_msgs/BoundingBox2D.
Since the values from this limits can be calculated from the convex_hull field which contains 3D points, I think it's ok to simply remove limits as the plane may not always be horizontal.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
As there exists the message
sensor_msgs/RegionOfInterest
, we should remove ourmas_perception_msgs/BoundingBox2D
in favor of the built-in option.This will affect
mas_perception_msgs/Plane
, and potentiallymdr_place_action
, since it uses thelimits
field inmas_perception_msgs/Plane
of typemas_perception_msgs/BoundingBox2D
.Since the values from this
limits
can be calculated from theconvex_hull
field which contains 3D points, I think it's ok to simply removelimits
as the plane may not always be horizontal.The text was updated successfully, but these errors were encountered: