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

Storage problem of your paper #37

Closed
wzjwzj00 opened this issue Aug 24, 2022 · 2 comments
Closed

Storage problem of your paper #37

wzjwzj00 opened this issue Aug 24, 2022 · 2 comments

Comments

@wzjwzj00
Copy link

What is included in the storage volume(KB) of different LODs in Table 1 in your paper?Just the octree related data structures saved by the weight file?
Looking forward to your reply!

@wzjwzj00 wzjwzj00 changed the title Storage problem of Storage problem of your paper Aug 24, 2022
@joeylitalien
Copy link
Collaborator

Hi @dhuwzj,

It's been quite a while so we can't exactly recall how this was computed. It is most likely just (# of active feature vectors per LOD) × (feature vector size) × (4 bytes for 64-bit floats) / 1024 (to convert to KB). AFAIK we didn't use half-precision floats for the table to be fair to other techniques. Note that the octree structure incurs an extra storage cost because we need to track of active voxels (i.e., the occupancy bits in Morton order at each level). I doubt this was included in the numbers of Table 1 back then, but this is quite minimal compared to the feature grid so the numbers should roughly stand.

If you want the "true" storage on disk, you can also save each octree level without the decoder network.

@wzjwzj00
Copy link
Author

Thank 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