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

indoor3D data strcuture #49

Closed
yaping222 opened this issue May 23, 2019 · 3 comments
Closed

indoor3D data strcuture #49

yaping222 opened this issue May 23, 2019 · 3 comments

Comments

@yaping222
Copy link

Dear erikwijmans,

Thank you very much for your great codes!
I have a question about how data is organized in '.h5' files.
I run your code 'python -m pointnet2.train.train_sem_seg', then the data were automatically downloaded and unzipped.
When I open the '.h5' file, the data dimension is (1000, 4096, 9). It seems for every '.h5' file, it has 1000 point clouds. Each point cloud (item?) has 4096 points with xyz and other 6 features.
During the training, the dataloader get 'items' (point clouds) and sample 'num_points' for training.
I get several point clouds (4096,3) and visualize them. It seems each small point cloud was not randomly sampled from a large point cloud. I'm wondering how to well split a large point cloud into small pieces, and each piece has exactly 4096 points.

image
image

@yaping222
Copy link
Author

If I split a point cloud into tiles, I cannot guarantee each tile has exactly 4096 points.
If I just randomly select 4096 points, geometry features are very difficult to be preserved, but here, object geometry is well-preserved.

@erikwijmans
Copy link
Owner

I didn't generate that dataset, but I believe this is script that did: https://github.com/charlesq34/pointnet/blob/master/sem_seg/gen_indoor3d_h5.py

@yaping222
Copy link
Author

Thank you very much for your reply. It is quite helpful.

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