-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MLPEstimator do not report the proper n_iter_
after successive call of fit
#24764
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
max_iter
MLPRegressor
and MLPClassifier
does not respect max_iter
with warm_start=True
Note that LBFGS solver works as expected. |
OK, the reason is that the |
MLPRegressor
and MLPClassifier
does not respect max_iter
with warm_start=True
n_iter_
after successive call of fit
Need to check if this is a bug or a feature cf. #16812 |
EDIT: actually, thinking more about that I agree that it should be 20 in total (we are not doing incremental learning here) |
Just to confirmed that this is a bug because the above test would work with |
Describe the bug
It seems that
MLPRegressor
andMLPClassifier
does not take into accountmax_iter
withwarm_start
.Steps/Code to Reproduce
You can also try
MLPClassifier
which leads to over iterating.Expected Results
n_iter_ <= 20
Actual Results
Versions
The text was updated successfully, but these errors were encountered: