-
Notifications
You must be signed in to change notification settings - Fork 34
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
Skip waypoints if occupied #68
Comments
No, but there are options to specify rows to use - so you could replan excluding it and any completed rows -- so in spirit but not as a "here's a parameter to do it". Nor do I think that it would work ... super duper well. That would be a good feature, but I don't think its a trivial change. We should probably discuss design and options. |
Excluding a complete row is a bit excessive and impacts the coverage quite a lot. Alright, already good to know that it's not possible, I'll come back with a design proposal when I come back to this. I think this feature will be widely requested |
This is mostly a F2C thing: its really more meant for static fields that you know about the obstacles in to begin with. However, adding another module that uses some F2C and some custom (like the Row Coverage server) that does more active choices would be welcome here :-) But, maybe you have thoughts about how more can be used that I didn't think of |
I plan on using opennav_coverage in the future but haven't yet so I can't answer this question myself: Is there any functionality to skip waypoints if they are occupied (for too long). If not then this is an issue to implement that (opt-in).
The text was updated successfully, but these errors were encountered: