-
Notifications
You must be signed in to change notification settings - Fork 74
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
Visualization of the bases selected by super4pcs #24
Comments
Hi, thanks for this very detailed report. Do you have a repo I can access to look at your changes ? |
Hi, |
Thanks, I will try to have a look asap. I'm very busy these days but hopefully I can have a look early next week.
It is a very important feature and we are currently working on it, hopefully we should release a software a GUI to check the algorithm output. I will check your code as well, and see if we can merge it to master.
Extending pairs filtering is easy to do, by implementing a dedicated filter inheriting Note there are already options in the code to set the maximum angular and translation motion (see declaration at
A simple thing you can do is to update the file |
Hello sir,
I am trying to visualize the corresponding bases selected by Super4pcs in input and output PointCloud, for debugging purposes and extending this library for a segmentation network.
I have made following changes in the code:-
base_
andcurrent_congruent_
are the data members that hold the indices of points consisting of the bases in the input and output PointClouds after final iteration, (from here). So I make them public members in the derived class Match4pcsBase(shown here).demos/Super4PCS/super4pcs_test.cc
(shown here).And printing these 3D points to the terminal (shown here).
My question is: Are the bases really non-corresponding in this scenario or I have made some wrong assumptions of the data members storing final bases coordinates. Please let me know how can I access the final bases and possibly change them at the starting point itself.
Thanks
The text was updated successfully, but these errors were encountered: