You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pointQueue is cleared. But it is only cleared if it is bigger than a specified value. This seems weird. Should we clear every new iteration. This can result in an incomplete cluster being merged with another very far away. The centroid can be miles away from any of its points in this case. Seems weird but I might be wrong
The text was updated successfully, but these errors were encountered:
Well, as I mentioned in the README and just re-adapted the dbscan project from the dbscan-octrees repository, so I did not implement the logic in that module.
Regarding your question, I am really open to contributions and improvements, if you think there is a potential bug I encourage you to open a PR so we can compare the clustering process before - after the fixed bug and merge any patch if need it.
I am not totally familiar with the algorithm so I might be missunderstanding but comparing with the paper and logically I see a potential issue.
In this line: https://github.com/danielTobon43/DBScan-PCL-Optimized/blob/master/dbscan/src/dbScan.cpp#L214
The
pointQueue
is cleared. But it is only cleared if it is bigger than a specified value. This seems weird. Should we clear every new iteration. This can result in an incomplete cluster being merged with another very far away. The centroid can be miles away from any of its points in this case. Seems weird but I might be wrongThe text was updated successfully, but these errors were encountered: