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

Questions about the 3D match training data #33

Open
shinshiner opened this issue Aug 9, 2020 · 3 comments
Open

Questions about the 3D match training data #33

shinshiner opened this issue Aug 9, 2020 · 3 comments

Comments

@shinshiner
Copy link

Hello, thanks for sharing the well-organized code. I have downloaded the training data of 3dmatch from the link provided in scripts/download_datasets.sh. I found there only 7000+ scene pairs with 0.3 overlap threshold while there are tens of thousands frames in even one sequence of the original 3dmatch dataset. Have you conducted some sampling operations and are these all the training data?

Thanks in advance :)

@chrischoy
Copy link
Owner

The commercial depth sensors generate noisy samples that are not suitable for registration. A typical pipleline first integrate 50-100 frames into one point cloud. We also followed this procedure and created N^2 pairs within one sequence and then removed pairs < 0.3 overlap.

@shinshiner
Copy link
Author

Got it. Thanks for your reply.

@shinshiner
Copy link
Author

BTW, it seems that the judgement of overlap is conducted in point clouds with 0.1 voxel size downsampling while 0.05 for the test data, is that true ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants