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

Training freezes and gets stuck #6

Open
henrypearce4D opened this issue Jun 25, 2024 · 7 comments
Open

Training freezes and gets stuck #6

henrypearce4D opened this issue Jun 25, 2024 · 7 comments

Comments

@henrypearce4D
Copy link

Training freezes and gets stuck, happens at low iterations


Reading camera 176/176 [25/06 11:43:34]
Generating random point cloud (100000)... [25/06 11:43:34]
Loading Training Cameras [25/06 11:43:35]
Loading Test Cameras [25/06 11:44:43]
Number of points at initialisation :  100000 [25/06 11:44:52]
Training progress:   3%|█▎                                         | 900/30000 [00:30<05:29, 88.41it/s, Loss=0.4608608]
@mbernier-arcturus
Copy link

Check your GPU memory, in some cases during training it goes haywire and GPU memory bust. I got this error while trying different combinations of parameters.

@shakibakh
Copy link
Collaborator

Can you please specify the setup and the shape you are trying to run and also your environment?
The code is only tested on Ubuntu, the specifics are now updated in README.

@henrypearce4D
Copy link
Author

Can you please specify the setup and the shape you are trying to run and also your environment? The code is only tested on Ubuntu, the specifics are now updated in README.

Hi, this is my conda env running on windows 10 cuda toolkit 11.8

channels:
  - pytorch
  - conda-forge
  - defaults
dependencies:
  - cudatoolkit=11.6
  - plyfile
  - python=3.8
  - pip=22.3.1
  - pytorch=1.12.1
  - torchaudio=0.12.1
  - torchvision=0.13.1
  - tqdm
  - packaging
  - pip:
    - submodules/diff-gaussian-rasterization
    - submodules/simple-knn```

@NeutrinoLiu
Copy link

NeutrinoLiu commented Jul 18, 2024

one reason might be the relocation stage, it takes long time if there are a lot of "dead gaussian" in the scene (i suppose, not sure). I recommend lower the max_cap from 1M to some lower values. for me i just use 100K for simple scene. that might help.

@ekhaliul
Copy link

ekhaliul commented Aug 2, 2024

I had a similar issue and this fix resolved it for me.

@henrypearce4D
Copy link
Author

I had a similar issue and this fix resolved it for me.

Thanks for the suggestion, I already switched to using the implementation in nerfstudio

@henrypearce4D
Copy link
Author

hi all, revisiting this it does look related to the max cap value.

I'm using 190 images at 4112 x 3008 res on -r 2 with --data_device cpu flag.

If I increase the --cap_max 1000000 to anything over that then limits are being reached.

In task manager you can see that the GPU memory is still maxing even though im using the data device cpu flag, is this because I'm using the -r flag but not actually using downscaled images?
image

compared to postshot mcmc, I can set that at 3m max cap and use a downscaled res of 75% so seams more optimised

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

5 participants