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

lr_scheduler has no state_dict #217

Closed
georgeyiasemis opened this issue Jul 13, 2022 · 0 comments · Fixed by #218
Closed

lr_scheduler has no state_dict #217

georgeyiasemis opened this issue Jul 13, 2022 · 0 comments · Fixed by #218
Assignees
Labels
bug Something isn't working

Comments

@georgeyiasemis
Copy link
Contributor

Describe the bug
'LR scheduler has no state_dict' error appears when training, so it's not checkpointed.

To Reproduce
Any training script.

Expected behavior
LR scheduler state_dict to be checkpointed and for the error todisappear.

@georgeyiasemis georgeyiasemis added the bug Something isn't working label Jul 13, 2022
@georgeyiasemis georgeyiasemis self-assigned this Jul 13, 2022
@georgeyiasemis georgeyiasemis linked a pull request Jul 13, 2022 that will close this issue
georgeyiasemis added a commit that referenced this issue Jul 13, 2022
HasStateDict type changed to include torch.optim.lr_scheduler._LRScheduler which was missing before, causing the checkpointer to not save/load the state_dict of LRSchedulers.
georgeyiasemis added a commit that referenced this issue Jul 31, 2022
HasStateDict type changed to include torch.optim.lr_scheduler._LRScheduler which was missing before, causing the checkpointer to not save/load the state_dict of LRSchedulers.
georgeyiasemis added a commit that referenced this issue Jul 31, 2022
HasStateDict type changed to include torch.optim.lr_scheduler._LRScheduler which was missing before, causing the checkpointer to not save/load the state_dict of LRSchedulers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant