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 main reason is that this would require to modify the successor list on which we rely to assign each octant the points it contains.
I currently also assume that the points vector does not change, since I store only the indices to the points in the vector. Adding points should be easy to implement, since it might only involve reshuffling the successor list. However, removing points is a different story.
It involves definitely some work, but should be possible to implement. I refrained from implementing it, since doing it in a consistent and nice way needs some non-trivial design decisions, which would break the original design substantially. For me it was always fine to just rebuild the tree as the construction is negligible in my applications where I searched for each points neighbors.
For example, provide some functions to add, remove or update points and recalculate the octree's childs.
The text was updated successfully, but these errors were encountered: