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

How to calculate total model parameter of Co-SLAM? #51

Open
saulgooodman opened this issue Jul 3, 2024 · 6 comments
Open

How to calculate total model parameter of Co-SLAM? #51

saulgooodman opened this issue Jul 3, 2024 · 6 comments

Comments

@saulgooodman
Copy link

Hello, I tried to calculate the total parameter of Co-SLAM by calculating all the parameters in decoder, but I found the result is much smaller than the data in the paper. I thought it was because I didn't take the learnable parameters outside the decoder into consideration. I'd like to ask how you calculate all the parameter in Co-SLAM. Thanks a lot!

@HengyiWang
Copy link
Owner

Hi @saulgooodman, you can either use torchsummary or calculate the total amount of params of encodings based on hash table size. For all default settings reported in our paper, we use hash size 13.

@saulgooodman
Copy link
Author

Thank you for your reply. I would like to confirm again, all the parameters include network parameters + parameters for multi-resolution hash grid + parameters for camera pose, right?

@HengyiWang
Copy link
Owner

As far as I remember, we did not count the parameters for camera pose in the paper. But, yes, definitely decoder + hash grid. For example, let us say if your hash size is 10, then the total params for your hash grid should be something around 16 * 2^10 *2. where 16 is #resolution, and 2 is feature dim.

@FDF521X
Copy link

FDF521X commented Oct 21, 2024

Why did you use hash=16 for experiments, but hash=13 for calculating the parameter count?

@HengyiWang
Copy link
Owner

Sorry, I do not get what you mean. For Tab.1, all results are generated using hash=13. And 16 in my previous reply corresponds to the num of resolutions since we use a multi-resolution hash grid as in instant-ngp.

@FDF521X
Copy link

FDF521X commented Oct 24, 2024

Sorry, I do not get what you mean. For Tab.1, all results are generated using hash=13. And 16 in my previous reply corresponds to the num of resolutions since we use a multi-resolution hash grid as in instant-ngp.

I apologize for not being clear. I noticed that in your provided code, the hashsize for the replica scenario was set to 16, so I thought this was your default configuration.

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

3 participants