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

frame ranges on custom dataset #134

Open
briancantwe opened this issue May 22, 2024 · 1 comment
Open

frame ranges on custom dataset #134

briancantwe opened this issue May 22, 2024 · 1 comment

Comments

@briancantwe
Copy link

briancantwe commented May 22, 2024

Hello! I'm trying to run custom data through the multiview setup. It all seems to work in that when I have fewer frames in the input directory, it processes quickly, and more frames takes much longer. But there's no real shell output that tells you this. When I check the test renders though, I only get one frame, but it looks pretty good. And if I use export_perframe_3DGS.py, I always seem to get 6 ply files out that seem to be the first 6 frames of the range.

Is there something I'm missing?

Thanks so much!

@Hongyuan-Tao
Copy link

Hi,did you meet some problems when you use multipleviewprogress.sh to make your own dataset.Please make sure that you have named your images as what have been shown in the readme.md.

You say that you only get one frame you check the test renders. To help you handle this problem,I suggest you to Breakpoint debugging on the 641th line of scene/dataset_readers, when your program reaches this line,please pay attention to whether the variable test_cam_infos has a sufficient number of image_paths.

If there are no problems with the above steps,Please give me feedback as soon as possible and I will further discuss this issue with you.

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