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

How to preprocess the scene dataset #15

Open
HaolinLiu97 opened this issue Aug 9, 2021 · 4 comments
Open

How to preprocess the scene dataset #15

HaolinLiu97 opened this issue Aug 9, 2021 · 4 comments

Comments

@HaolinLiu97
Copy link

I try to use the preprocessing script boundary sample to compute distance field for the scannet scene, which should be quiet similar to the Gibson dataset. However, I found that some distance field is not correctly computed after visualization (Actually most of the distance field is not computed corrected, for example, query points behind the walls will have weirdly very small distance field). I assume this is caused by reason that libigl is not able to compute the signed distance field on open surface. Therefore, I wonder how the author preprocess the scene data, will be preprocessing script for scene data released in the future?
Thank you in advances!

@ZhengdiYu
Copy link

Could you share some of your visualization?

I have also tried to train on a single frame of ScanNet. And The reconstruction results seemed not bad. How did you inspect if the dfs are correct or not?

@HaolinLiu97
Copy link
Author

@jchibane Sorry for the late reply, but I eventually figure it out it would be more suitable to compute the distance field using igl.point_mesh_squared_distance for open mesh. The sign_distance function still seems to have some problem with open mesh, but I guess it will not affect the training very much for small deviation from the actual distance field.

@jchibane
Copy link
Owner

Hey,
yes, you need to compute unsigned distance fields - the sign you get can not be reliable in case of open surfaces.
Maybe having a look into the pull request would be helpful to you.

Best,
Julian

@ZhengdiYu
Copy link

@jchibane Sorry for the late reply, but I eventually figure it out it would be more suitable to compute the distance field using igl.point_mesh_squared_distance for open mesh. The sign_distance function still seems to have some problem with open mesh, but I guess it will not affect the training very much for small deviation from the actual distance field.

Thank you for your reply, but why is it available for cars' open surface?

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

3 participants