-
Notifications
You must be signed in to change notification settings - Fork 24
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
Question about triplane prediction & optimization #29
Comments
Hi! The density grid is for occupancy-based pruning, which is not part of the gradient graph by design. Since you are using triplanes with a resolution of 64, it could be possible that there's not enough capacity to capture the full details of the target. |
Hi @Lakonik - thanks for the helpful reply to my question! It seems like occupancy-based pruning is designed primarily for the discrete NeRF problem where you have some finite set of scenes and you can maintain a grid state for each (the I'm wondering: what is your suggested approach for raymarching in a setting where the number of NeRFs is infinite? For example, a setting where we predict a triplane nerf from an image like LRM. Should the |
|
Thank you so much for an awesome code library!
I am trying to train a neural network to predict triplane codes from a reference image view of an object. I am using your triplane-nerf library for the rendering and it works pretty well but I am seeing some odd pixelation & artifacts even after training to convergence. Below is a very brief code description of the optimization procedure that I follow during training. The parameters of
decoder
andpredictor_net
are optimized. Am I doing anything wrong here? I've included a visualization of the predicted (rendered) image vs. target image at the bottom of this message.I noticed that the output
density_bitfield
from nerf.get_density does not have grad. Don't we need gradients to flow through the density MLP in order to facilitate proper training? Is there a way to do this with grad?prediction vs. target:
The text was updated successfully, but these errors were encountered: