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

Remove pytorch hash table if tcnn implementation is used #2175

Merged
merged 5 commits into from
Jul 6, 2023

Conversation

georghess
Copy link
Contributor

When selecting tcnn implementation for HashEncoding, a PyTorch version was still initialized and held in memory, but never used. Now, the PyTorch hash table is only created when selecting PyTorch implementation, or if tcnn is not available.

Copy link
Contributor

@tancik tancik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing!

@tancik tancik enabled auto-merge (squash) July 6, 2023 17:39
@tancik tancik merged commit 492fa0e into nerfstudio-project:main Jul 6, 2023
4 checks passed
sjuxax added a commit to sjuxax/nerfstudio that referenced this pull request Jul 13, 2023
This allows tcnn models that contained a torch hash_table to load.
In particular, it allows us to load tcnn models prior to PR nerfstudio-project#2175.

cf. nerfstudio-project#2175
tancik added a commit that referenced this pull request Jul 13, 2023
* Try non-strict model loading on RuntimeError. ...

This allows tcnn models that contained a torch hash_table to load.
In particular, it allows us to load tcnn models prior to PR #2175.

cf. #2175

* Only allow non-strict loading when called with defaults.

* Reflow to avoid code duplication; blacken.

---------

Co-authored-by: Matthew Tancik <matt@lumalabs.ai>
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

Successfully merging this pull request may close these issues.

None yet

2 participants