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

Vector polygon - Collision Monitor is not available for ROS2 humble #4363

Closed
samarth-eic opened this issue May 23, 2024 · 5 comments
Closed

Comments

@samarth-eic
Copy link

While implementing collision monitor for our AMR in ROS2 humble we were able to use collision monitor, but it has a drawback

  1. whenever there is obstacle in front of robot it just stop despite having enough space to change the path and move forward
  2. It stays in stopping condition till the recovery mode is not running. Which is not allowing the robot to move with any of the valid path.
    After reviewing the documentation and other source for solving this we found that vector polygon can help us with these drawbacks, but unfortunately there is not implementation of vector polygon on ROS2 humble. Is there anything which can be done to solve these issue or drawbacks, or is there any plan for giving implementation for humble.
@tonynajjar
Copy link
Contributor

vector polygon

I assume you mean the Velocity polygon added here

Unfortunately it cannot be backported to Humble as per this comment. I haven't tried but I think it wouldn't be so hard for you to backport it in a fork.

@samarth-eic
Copy link
Author

samarth-eic commented May 23, 2024

@tonynajjar Thanks for your time and effort, for which ROS version does velocity polygons are available and also does backport it in a fork will work or not ?

@tonynajjar
Copy link
Contributor

tonynajjar commented May 23, 2024

for which ROS version does velocity polygons are available

https://docs.nav2.org/migration/Iron.html#add-velocitypolygon-in-collision-monitor
Only in Jazzy which is not yet released

backport it in a fork will work or not

Likely to work but you'd need to try to be sure

@MichaelT64
Copy link

Hi,
I had the same problem and made a fork from Main and tried to adopt it for humble with some CPP and Python expression magic: https://github.com/MichaelT64/navigation2/commits/rolling-humble/
The CollisionMonitor works for me, due to lack of time and knowledge I was not able to make deeper tests of the navigation itself for now.
Maybe it helps you.

Michael

@samarth-eic
Copy link
Author

Thanks for your effort, we were still stuck there maybe we can check and let you know :)

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

3 participants