-
Notifications
You must be signed in to change notification settings - Fork 30
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
AttributeError when calling model.fit() with AdamW optimizer on Apple Silicon #176
Comments
@anton-bogomazov, |
@tilakrayal I was also following this issue and just to be clear you run under apple silicon right ? |
Thank you, @tilakrayal ! |
Hello, @tilakrayal ! |
@anton-bogomazov |
@anton-bogomazov, |
@anton-bogomazov |
This issue is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. |
This issue was closed because it has been inactive for 28 days. Please reopen if you'd like to work on this further. |
For anyone encountering this, this is fixed on |
I think the issue is not fixed, I'm in 2.15 version and I'm not able to train a BERT model using Adamw in my Apple Silicon M1 Max. And the log saying "WARNING:absl:At this time, the v2.11+ optimizer |
System information.
Describe the problem.
Calling model.fit() created with AdamW optimizer leads to an AttributeError. Keras trying to fallback optimizers to their legacy versions on Apple Silicon, but the legacy version of AdamW does not exist.
https://github.com/keras-team/keras/blob/5849a0953a644bd6af51b672b32a235510d4f43d/keras/optimizers/__init__.py#LL300C1-L315C59
Same issue description: https://developer.apple.com/forums/thread/731019
Describe the current behavior.
AttributeError: 'str' object has no attribute 'minimize' while fitting model with AdamW optimizer.
Describe the expected behavior.
Check if legacy version exists for the optimizer; don't fallback if not and use the standard version + print warning.
Contributing.
Standalone code to reproduce the issue.
Source code / logs.
The text was updated successfully, but these errors were encountered: