-
Notifications
You must be signed in to change notification settings - Fork 150
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
Slow training? #66
Comments
Hi, are you using my latest code and set PipelineParams.debug=False? |
Thanks for the quick response. I am using an old commit 5a80f11. Let me pull the latest code and see what happen then. And my training images is 1080p. I have 30 cameras, and very long sequence video. What do you think is the maximum frames per camera for 4D Gaussians? |
Thanks, I think this old commit can also work. what I want to note is that setting |
I think they are False by default no? For the pc initialization, I was just using 2000 points. Let me dig more. Thanks! |
I also have another question. Would appreciate it if you can answer I currently have a dataset with similar structure with Neu3D data except that it does not use NDC and we have gt calibration for that. So I follow how you read Neu3D data but instead of using readdynerfInfo I modified the readCamerasFromTransforms to append m x n CameraInfo, where m is the num of cameras per frame and n is the number of frames. However, I always find the console return 'Killed' in the data loading stage. So I have to reduce the number of frames to make it work. I cannot even load 1080p * 30 cameras in 100 frames. Have you had this issue? Is it normal? |
Hi, I dont think it's normal. |
Hi,
Thanks for the amazing work.
I have this issue on super slow training speed. I am using a 3080. When the training just start the coarse training can reach ~10 it/s but afterwards it became 1 it/s, which is 10x slower and it took 10 hours for a 30 frame videos.. Any clue why this happens?
The text was updated successfully, but these errors were encountered: