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
Bad quality on custom unbounded inward dataset #43
Comments
i have the same problem , dvgo can get great PSNR like 30,and can get prefect picture , but when it come to a novel view, result is very poor,PSNR is about 7 |
Hi @sunset1995 @desaixie, I am facing a similar issue as above when trying to train the DVGO model with ScanNet dataset. Do you have any advise or suggestions about the above mentioned problem? Would really appreciate any help. Thanks, |
@yashbhalgat @liyujiejiejie @desaixie any solution now? I face the same question. |
@yashbhalgat @desaixie @adkAurora @sunset1995 I believe this problems have been solved in our paper s3im. You can try it😊 dvgo_replica_scan1_rgb.mp4 |
@Madaoer Impressive results. Great to see a paper that solves this problem exactly! |
I am trying to use DVGO to reconstruct synthetic 3D scenes from the Replica dataset. I gathered an inward facing trajectory of images and poses (generated by pose_spherical with 20 theta angles * 3 phi angles * 3 heights = 180 poses). Since I generate poses first and then use habitat-sim to get the camera view at the poses, I don't have to run colmap. The following is the visualization of camera poses using
tools/vis_train.py
.I use the config
default_ubn_inward_facing.py
withnerfpp
dataset. After training, if I use the same training trajectory for testing, DVGO would perfectly render the views. This validates that my image-to-pose mapping is correct. However, if I use an adjested, still inward-facing trajectory for testing, there are distortions as shown bellow (first is rendered by DVGO, second is the ground truth from habitat-sim, they don't have the exact same pose, but show roughly the same view).My questions:
The text was updated successfully, but these errors were encountered: