-
Notifications
You must be signed in to change notification settings - Fork 11
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
raise ValueError('Optimizer must have a "lr" attribute.') #133
Comments
There is a PR that should address this issue. See PR #131. I have been quite preoccupied lately, but I can take a look at this PR after work today and do some tests. For now, to test if using this new implementation resolves your issue, try installing it from the PR branch in question:
Note that I have yet to test this implementation fully, but this would be a nice way of doing it. @21-10-4 Would be really helpful if you reported your findings :] |
Thank you very much, I did as you said, but a new problem appeared:
|
@21-10-4 This issue I have seen before. I can make a gist to reproduce the issue and see if we can resolve it. For now, could you test the model wrapper approach instead, as described in the README: IMO, the model wrapper is MUCH more robust for single-GPU applications. Or are you trying to do distributed training? |
@21-10-4 Aaah, scratch that! Now I remember why the first issue was so familiar. TF/Keras changed their Optimizer implementation quite a bit from Basically, do this instead if you wish to use the Optimizer wrapper:
Replace the optimizer above with whichever optimizer you please (e.g., Adam), just remember to use the |
Thank you ~ |
Describe the bug
To Reproduce
code:
Expected behavior
A clear and concise description of what you expected to happen.
Error logs/Screenshots
If applicable, add logs/screenshots to give more information about the issue.
Desktop (please complete the following information):
Distributor ID: CentOS
Description: CentOS Linux release 7.8.2003 (Core)
Release: 7.8.2003
Codename: Core
]
Additional context
error source:
The text was updated successfully, but these errors were encountered: