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

too high psnr #28

Open
hot-bulgogi opened this issue Oct 28, 2024 · 3 comments
Open

too high psnr #28

hot-bulgogi opened this issue Oct 28, 2024 · 3 comments

Comments

@hot-bulgogi
Copy link

hot-bulgogi commented Oct 28, 2024

I conducted experiments on the flame_steak sequence using 300 frames in --eval mode. Although the paper mentions achieving PSNRs of 33.54/34.30, in my case, I recorded a PSNR of 35.10 in stage 1 and 35.92 in stage 2.

I used CUDA 11.7 with an RTX 3090.

Could it be that the test set was not properly used even though I used the --eval option?

Here are a few possible reasons I am considering:

Should I initialize frame 0 using --eval even for vanilla-3DGS?
Should I remove the test views in COLMAP as well?

@SJoJoK
Copy link
Owner

SJoJoK commented Oct 28, 2024

Regarding your second concern, yes, we also turned on --eval when training 3DGS for frame 0. So I think that's why you get a higher PSNR for subsequent frames.

@hot-bulgogi
Copy link
Author

Thanks a lot! I will try experiment with frame 0 using --eval.

@SJoJoK
Copy link
Owner

SJoJoK commented Oct 28, 2024

Glad to help:)

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