-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
FarthestPointDownSample: starting with an index other than 0 #7049
Comments
You could swap the point at index 0 with the point of your desired index and then call FarthestPointDownSample. Does this work for you? |
That is indeed how I'm doing it right now |
Would maintainers be in favor of providing the option to start from a specified index other than 0? I can take a shot at this then and open a PR |
Can you explain how you use the feature? I just want to understand the use case better |
Use caseI've got several camera poses (200+) looking at the same region/scene from different viewpoints. For every camera pose, I want to find Admittedly, I'm not directly operating on a point cloud for this use case, but since I'm working with point clouds as part of the project anyway and therefore am already using Open3D, I thought I would create a "point cloud" out of the camera positions and use an Open3D functionality if available. I came across tools like fpsample but I'm not keen on bringing in a new dependency just for this one thing. |
Looks like a really good example where setting the start index is needed. Looking forward to the PR! |
Checklist
main
branch).My Question
Looking at the implementation of
PointCloud::FarthestPointDownSample()
(linked down below for convenience), the downsampling always starts frompoints_[0]
becausefarthest_index
is initialized as0
.Open3D/cpp/open3d/geometry/PointCloud.cpp
Lines 509 to 542 in fcc396e
However, how could I start the downsampling from another index?
I could copy the implementation and modify the initial value of
farthest_index
to my desired index, but I wanted to ask if something already exists for this.The text was updated successfully, but these errors were encountered: