-
Notifications
You must be signed in to change notification settings - Fork 108
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
I need your help #38
Comments
This is basically a matter of visualization. We do not plan a specific trajectory for the connecting journey between two workpaces or rooms in the map (the coverage path planner usually partitions the map or room into several smaller workspaces, and each of the workspaces gets a collison-free planned coverage path trajectory). The goal for moving to the next work area after completing the previous is usually commanded to the navigation package which finds a collision-free path once it is needed. Due to dynamics in larger maps, it does not really make sense that the coverage path planner already plans a long driving path from one work cell to the next in advance, as the dynamic obstacle situation might change severely such that another path would be required. |
Thank you for your answer on how to make the path planning it generates sparse and bypass obstacles |
Excuse me, why does the generated path plan pass through obstacles
![max_deviation_from_track参数为10](https://private-user-images.githubusercontent.com/150759172/351982574-e0a14321-0046-44f6-87c8-ee57741818f5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NjQyMTMsIm5iZiI6MTczOTU2MzkxMywicGF0aCI6Ii8xNTA3NTkxNzIvMzUxOTgyNTc0LWUwYTE0MzIxLTAwNDYtNDRmNi04N2M4LWVlNTc3NDE4MThmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNFQyMDExNTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lODVlYjgzYTZkMzQ3YTVmYmE2ODUxMjliNjQzZjRkNGU4YTk5OWZmNDhmZTRkNGM3ODUxZDA0Y2NmN2Q4MGM0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.N8NwKC3tp2TuIFrmEq4SUy-dTopIE__RA7LeiqTm5Cc)
The text was updated successfully, but these errors were encountered: