-
Notifications
You must be signed in to change notification settings - Fork 290
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
Boundingbox on Link API #2353
Comments
We already have the ability to get the bounding box, but it's through a component. Documenting this would be a good step as well. |
@azeey, isn't that only available to get the model bounding box, since the Physics plugin set it here? I couldn’t find any source that actually sets a Please let me know if I'm missing something, I hope this could be helpful to others. |
I think the alternative approach would be to update the the physics system populate the bounding box component for links as well? I see the API available in gz-physics, GetLinkBoundingBox |
Yes, I think this would probably be more straightforward. If I understood it correctly, this feature should be available for all currently supported physics engines, right? I initially thought not to update the physics plugin because I did not want to add extra load to a critical plugin if this was not an actual requirement. However, I believe we could do the same as for the model and only update the link entities containing the corresponding components. Maybe I could update #2787 to add this feature to the physics system and update the link API so that it only computes from the SDF if an Please, let me know what would be the best path forward. |
There is an alternative of Gazebo-classic's Link API Boundingbox function for ignition?
API reference page still shows a "TODO"
thanks!
The text was updated successfully, but these errors were encountered: