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

Issues with the pretrained model #8

Open
qsisi opened this issue Aug 23, 2021 · 0 comments
Open

Issues with the pretrained model #8

qsisi opened this issue Aug 23, 2021 · 0 comments

Comments

@qsisi
Copy link

qsisi commented Aug 23, 2021

Hello!

When I load the pretrained models (after GNN fixed) you offered in #3 , I notice that that value of key 'epoch' doesn't correspond with the value of key 'sheduler':

For KPConv-based:
>>>torch.load('indoor.pth')['epoch']
39
>>>torch.load('indoor.pth')['scheduler']
{'gamma': 0.95, 'base_lrs': [0.005], 'last_epoch': 42, '_step_count': 43, 'verbose': False, '_get_lr_called_within_step': False, '_last_lr': [0.0005799111065000276]}

For Mink_based:
>>>torch.load('sparseIndoor.pth')['epoch']
65
>>>torch.load('sparseIndoor.pth')['scheduler']
{'gamma': 0.99, 'base_lrs': [0.05], 'last_epoch': 75, '_step_count': 76, 'verbose': False, '_get_lr_called_within_step': False, '_last_lr': [0.0235293320792825]}

It is a bit confusing for me that the number of epochs doesn't stay the same in 'epoch' and the information recorded in 'scheduler'. So can you give me some hints about it?

Looking forward to your reply, 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

1 participant