-
Notifications
You must be signed in to change notification settings - Fork 3.5k
LR finder returns None #10557
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
Comments
This issue has been automatically marked as stale because it hasn't had any recent activity. This issue will be closed in 7 days if no further activity occurs. Thank you for your contributions, Pytorch Lightning Team! |
not stale |
This issue has been automatically marked as stale because it hasn't had any recent activity. This issue will be closed in 7 days if no further activity occurs. Thank you for your contributions, Pytorch Lightning Team! |
not stale. |
This issue has been automatically marked as stale because it hasn't had any recent activity. This issue will be closed in 7 days if no further activity occurs. Thank you for your contributions, Pytorch Lightning Team! |
It still persists :( |
This issue has been automatically marked as stale because it hasn't had any recent activity. This issue will be closed in 7 days if no further activity occurs. Thank you for your contributions, Pytorch Lightning Team! |
🐛 Bug: LR finder returns None
Could be come model or LR finder range which yield in returning LR as None which crashes the consecutive
To Reproduce
https://www.kaggle.com/jirkaborovec/titanic-crash-with-lightning-flash
Expected behavior
I see several options:
tune
so it does not interfere with consecutivefit
Additional context
include in Tune redesign #9103
cc @akihironitta @Borda @rohitgr7
The text was updated successfully, but these errors were encountered: