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

The poor performance of ScanNet #11

Open
kk6398 opened this issue Jan 9, 2025 · 2 comments
Open

The poor performance of ScanNet #11

kk6398 opened this issue Jan 9, 2025 · 2 comments

Comments

@kk6398
Copy link

kk6398 commented Jan 9, 2025

I download and test the performance of scannet_0000. The result is as follow:
image

Is something wrong about scannet_0000? Looking forward your reply.

@Willyzw
Copy link
Owner

Willyzw commented Feb 12, 2025

Hi, thank you for trying out our pipeline! As reported in the paper, our pipeline is capable of achieving higher PSNR performance. Could you confirm if you preprocessed the data using our provided script preprocess_scannet.py? Additionally, it’s very important to crop the border area by using the argument --cropborder 12 as done in our evaluation script run_scannet.py. This removes the black borders resulting from the undistortion process. Let me know if you need further help!

@lanlan96
Copy link

Hi, I come with the same problem. I test the 'scene0169_00' sequence. I follow the processing script and use the script run_scannet.py. The only change is that I change the args.buffer from args.buffer = min(1000, N // 10 + 150) if args.buffer < 0 else args.buffer to args.buffer = min(1000, N // 10 + 600) if args.buffer < 0 else args.buffer since it comes with errors like out of index. The results seem bad. Could you please provide some suggestions?

Image

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