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

Issues with the Stanford demo #32

Closed
amineremache opened this issue Apr 6, 2020 · 2 comments
Closed

Issues with the Stanford demo #32

amineremache opened this issue Apr 6, 2020 · 2 comments

Comments

@amineremache
Copy link

Hello,
I tried to run the Stanford demo, and I got multiple issues:
1- When you run the python -m demo.stanford command for the first time (you don't have the .ply file yet) it should run the download function since the file_name doesn't match with any local file.
image
But then, you get this error:
image
Because the defined file_name in the start of the demo file doesn't match the name of the file on the server-side if you follow the static part of the link (conferenceRoom_1.ply vs 1.ply).
image

image

2- When you change the name on the code to 1.ply, it downloads the file, but from what I understood, it is not the good file.
Because then I got this error:
image

Which is caused by this line:
image

And when you see the structure of the data here:
image

It really has no "label" property, and I think the file is from ScanNet because when you visualize it you get this:
image

Sorry if this is not the proper way to write an issue, it is my first one, and I tried to be the most explicit I could.

@ghost
Copy link

ghost commented May 27, 2020

Hi,

That's because 1.ply is from Scannet dataset & doesn't have the label attribute. What you need is a test file from S3DIS dataset.

Another hack would be to just pass torch.ones(SHAPE) as labels variable in stanford.py, it will run.

@amineremache
Copy link
Author

Hi,

That's because 1.ply is from Scannet dataset & doesn't have the label attribute. What you need is a test file from S3DIS dataset.

Another hack would be to just pass torch.ones(SHAPE) as labels variable in stanford.py, it will run.

Yeah, I was ( still ? xD ) a "noob" back then, it was my first few days with this code base, but things are good now, thanks for your answer.

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

1 participant