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
Sorry for asking so many questions but I just find your library fascinating and I am learning and reading your code since the last week. Also thank you for taking your time to answer my questions, I really appreciate it :)
The question I have is about datatypes you are using for the ICP algorithm.
From your code correct me if I am wrong:
You put the reference cloud in a struct called CorrespondenceTable
As such, the reference point cloud is used only to initialize the lookup table and to store the points for later retrieval (there are no conversions during matching).
Be aware that ICP uses the Correspondence class, in which the corresponding points are specified as indexes (associated with the points in the reference point cloud and sensor point cloud).
The main advantage of this approach is that it can be significantly faster than a k-d tree search and requires constant computational resources to perform, because the number of operations is always the same:
On the other hand, when using k-d trees, the computation time varies depending on how many levels the search algorithms needs to go through until it finds the closest point.
Hi Carlos,
Sorry for asking so many questions but I just find your library fascinating and I am learning and reading your code since the last week. Also thank you for taking your time to answer my questions, I really appreciate it :)
The question I have is about datatypes you are using for the ICP algorithm.
From your code correct me if I am wrong:
http://docs.pointclouds.org/1.7.0/_p_c_l_point_cloud2_8h_source.html
The text was updated successfully, but these errors were encountered: