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

Real Environment Deploy #6

Open
Krasjet-Yu opened this issue Nov 14, 2024 · 1 comment
Open

Real Environment Deploy #6

Krasjet-Yu opened this issue Nov 14, 2024 · 1 comment

Comments

@Krasjet-Yu
Copy link

Hello, I would like to ask what causes the following problems when I am deployed to the real environment? I have checked plane_OccMap and globalMap, where plane_OccMap is -1, 99, 100, what do they mean respectively, while /globalMap is -1 and 100, which causes Centroid to not be found in window. Where do you start with that?

[ INFO] [1731619796.054955314]: The current window has no centroid, expand the exploration window size.
[ WARN] [1731619796.055071958]: [NO CENTROIDS]: There are almost no explorable unknown regions!

@qingchen-bi
Copy link
Member

100 indicates a completely impassable area. -1 represents the unknown area, and the plane_OccMap should have values ranging from 0 to 99, indicating areas where travel is possible. The higher the number, the more dangerous it is. The unknown area that can be explored should be adjacent to the passable area. It is recommended to first review the code for generating the plane_OccMap in the fitplane module to ensure that it is aligned with the topic names for the odometry and the point cloud map, and that the data types are correct. Additionally, adjust the max_angle_, max_flatness_, and w1_ parameters to identify the source of the problem.

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

2 participants