-
Notifications
You must be signed in to change notification settings - Fork 44
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
Coverage Demo fails #41
Comments
You need to populate your field correctly - see the demo script or the tests (or even other F2C demos) |
You're saying that it is expected that running the demo launch file does not work out of the box? I saw that in the demo script |
In |
Sorry, took me a bit to get a workspace built with everything. It seems to be working fine for me on
|
Hmm, I tested on main, could you give this a quick test? I probably won't have time today anymore to test on Iron, I can try it tommorrow. P.s: you might also run into an issue with the BT plugins "already loaded", these need to be removed now I guess since they are loaded by default. |
Works fine too (after removing BT plugins from yaml, changing now)
|
Well, thank you for taking the time.... I'll check tomorrow how that could happen... |
^ note I ran those same commands I gave above and added the BT / navigator packages I forgot the first time. But literally copy pasted those commands in the |
Are you sure you tested with navigation2 and opennav_coverage on main? How did you not run into #43? Though, after this change it also seems to work on main, I'll check what's different in my setup |
I think I found the issue, I first built Fields2Cover as described here and then opennav_coverage and for some reason that doesn't work. |
How to reproduce:
ros2 launch opennav_coverage_demo coverage_demo_launch.py
Error:
[component_container_isolated-5] [ERROR] [1709560390.632574795] [coverage_server]: Internal Fields2Cover error: Geometry does not contain point 0
The text was updated successfully, but these errors were encountered: