-
-
Notifications
You must be signed in to change notification settings - Fork 26.5k
Fix AttributeError use_fallback_lbfgs_solve for newton-cholesky when fitting with max_iter=0 #26653
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
Merged
jeremiedbb
merged 7 commits into
scikit-learn:main
from
ogrisel:fix-attributeerror-newtonsolver
Jun 26, 2023
Merged
Fix AttributeError use_fallback_lbfgs_solve for newton-cholesky when fitting with max_iter=0 #26653
jeremiedbb
merged 7 commits into
scikit-learn:main
from
ogrisel:fix-attributeerror-newtonsolver
Jun 26, 2023
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…fitting with max_iter=0
Member
Author
|
/cc @lorentzenchr. |
Co-authored-by: Christian Lorentzen <lorentzen.ch@gmail.com>
ogrisel
commented
Jun 22, 2023
lorentzenchr
approved these changes
Jun 23, 2023
jeremiedbb
approved these changes
Jun 26, 2023
Member
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jeremiedbb
added a commit
to jeremiedbb/scikit-learn
that referenced
this pull request
Jun 29, 2023
…fitting with max_iter=0 (scikit-learn#26653) Co-authored-by: Christian Lorentzen <lorentzen.ch@gmail.com> Co-authored-by: Jérémie du Boisberranger <34657725+jeremiedbb@users.noreply.github.com>
jeremiedbb
added a commit
that referenced
this pull request
Jun 29, 2023
…fitting with max_iter=0 (#26653) Co-authored-by: Christian Lorentzen <lorentzen.ch@gmail.com> Co-authored-by: Jérémie du Boisberranger <34657725+jeremiedbb@users.noreply.github.com>
punndcoder28
pushed a commit
to punndcoder28/scikit-learn
that referenced
this pull request
Jul 29, 2023
…fitting with max_iter=0 (scikit-learn#26653) Co-authored-by: Christian Lorentzen <lorentzen.ch@gmail.com> Co-authored-by: Jérémie du Boisberranger <34657725+jeremiedbb@users.noreply.github.com>
REDVM
pushed a commit
to REDVM/scikit-learn
that referenced
this pull request
Nov 16, 2023
…fitting with max_iter=0 (scikit-learn#26653) Co-authored-by: Christian Lorentzen <lorentzen.ch@gmail.com> Co-authored-by: Jérémie du Boisberranger <34657725+jeremiedbb@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
module:linear_model
To backport
PR merged in master that need a backport to a release branch defined based on the milestone.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As found when trying to run
benchopton LogisticRegression with thenewton-choleskysolver.When writing the non-regression test, I found that both sag/saga and LBFGS also had problems with
max_iter=0but of a different nature (more minor as they would not raise an exception). See theXXXcomments for details.I plan to tackled those in dedicated follow-up PRs.
I think we should backport this fix to 1.3.0 (or 1.3.1 if the merge arrives too late).