-
Notifications
You must be signed in to change notification settings - Fork 47
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
Spurious Large Occupied Voxels #6
Comments
I see the same artifacts. Is there any explanation for these? |
I think they are caused by the incremental updates of the grid map, because it is working fine with If this issue is caused by incremental updates, then this problem may also affect nodes using ufomap API. I also can't confirm if this bug affects free and unknown voxels since they are difficult to debug by the human eye. Setting |
Hello,
I've noticed some spurious large occupied voxels that appear and disappear in the ufomap. They appear to be unknown voxels that get inadvertently converted to occupied. Within the first few minutes, I have noticed it a number of times. I am curious if you have observed this as well and perhaps can think of a quick fix. If more data would be helpful, please let me know, I already have uploaded a screen recording and rosbags for a 45 minute dataset to google drive, and it would be easy to share.
Here is the first instance of the issue:
Here is a video showing that the spurious occupied node was converted from unknown to occupied:
https://user-images.githubusercontent.com/33467025/118020657-8f04ac80-b317-11eb-8cc8-0c511fad57cc.mp4
Within the first few minutes, there were more instances of this issue:
This last one was a huge 40m voxel because the robot went outside:
ufo_bug2view2.mp4
The text was updated successfully, but these errors were encountered: