-
Notifications
You must be signed in to change notification settings - Fork 0
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
Questions about the Sequence of Data Association #3
Comments
Hi @zxd123, It is a little confusing indeed, because we split matching a plane from matching measurement points. The first step gives the linearization point of the plane feature, and the second step gives the "observations of the plane" from older poses, which are used in measurement model. The reasons for this are: the plane calculated from the first step is more stable than using close measurement points, and the reuse of measurement points can be avoided. |
Thank you very much for your reply. Looking forward to the open-source of this project. |
In the paper, it's mentioned that to process the data, one should first identify the plane that corresponds to a given point, and then locate the octree node containing the centroid of that plane to find the associated measurement points. However, could you please elaborate on the initial step? Specifically, once I have a set of measurement points from a frame, how is the corresponding plane for each point determined? 中文: |
和fastlio2 一样 |
好的好的,非常感谢 |
Thanks for sharing the great work!
But, I have a question about your paper. In section IV-D 4), you mentioned that for data association, one needs to first specify a point and a matching plane, and then look for the leaf node in the octree which contains the centroid of the plane to determine the matching relationship with the data point. However, I'm a bit confused about the sequence of this process. If we don't look for the leaf node in the octree, how can we know which plane the data point matches with?
Looking forward to your answer, thank you very much.
The text was updated successfully, but these errors were encountered: