Skip to content
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

Question about computing overlap ground truth #18

Closed
chienerh opened this issue Feb 15, 2021 · 4 comments
Closed

Question about computing overlap ground truth #18

chienerh opened this issue Feb 15, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@chienerh
Copy link

Hi, thanks for your great work!

I have a question while looking into how you generate the ground truth (demo 4).
In the paper, you mentioned that you use P_1 and P_2 and compute the overlap value with equation 3. And the result of it is figure 2 (a).
However, I am still not quite sure how you compute the overlap value ground truth shown in figure (c).
By looking into the com_overlap_yaw() function, you seem to compare the same point cloud with a different pose.
What confuses me is that reference_range and current_range are using the same point cloud, not P_1 and P_2.

It would be great if you could explain more. Thanks!

@Chen-Xieyuanli
Copy link
Member

Hey @chienerh,

Thank you for the feedback. I will carefully review the code and reply to you soon.

@Chen-Xieyuanli
Copy link
Member

Hey @chienerh,

Thank you so much to point the problem out!

You are right. The old script is wrong, which may be caused when we created the demo.

I've already corrected the function and please have a check here

Thank you again for following our work and help us to improve our code!

Best,
Xieyuanli

@Chen-Xieyuanli Chen-Xieyuanli added the bug Something isn't working label Feb 17, 2021
@chienerh
Copy link
Author

Hi @Chen-Xieyuanli,

Thanks a lot for the quick responding.
The updated code makes sense for me now.
Thanks for your update!

@yiming107
Copy link

Hi @Chen-Xieyuanli, following this issue, I see the com_overlap_yaw() function, when you compute the overlap:
overlap = np.count_nonzero( abs(reference_range[reference_range > 0] - current_range[reference_range > 0]) < 1) / valid_num overlaps.append(overlap)
I understood the idea is to account only valid points, so I assume, we should have current_range[current_range > 0] rather than current_range[reference_range > 0] here? Let me know what do you think, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants