-
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: arg to specify start index to start downsampling from #7076
Conversation
Thanks for submitting this pull request! The maintainers of this repository would appreciate if you could update the CHANGELOG.md based on your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @abhishek47kashyap for the PR! Please have a look at the comments
Comments have been addressed, with the main change being argument |
@abhishek47kashyap looks good. Thanks! |
Closes #7049.
The function
PointCloud::FarthestPointDownSample()
is overloaded to accept astart_index
in addition to the existingnum_samples
.Type
Motivation and Context
See ticket linked above.
Checklist:
python util/check_style.py --apply
to apply Open3D code styleto my code.
updated accordingly.
results (e.g. screenshots or numbers) here.
Description
This PR overloads the existing
PointCloud::FarthestPointDownSample()
to acceptsize_t start_index
as the desired index to start farthest point downsampling from. Bothgeometry
andt/geometry
have been updated and checks added to ensurestart_index
is valid. Input argumentsnum_samples
andstart_index
are markedconst
(existingnum_samples
was previously notconst
).Python bindings have been updated with
py::overload_cast
. Docstrings and unit tests have been modified accordingly.Output of unit tests