DOC clarify that Lasso.path() defaults to Elastic Net path #33049
+11
−1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reference Issues/PRs
Fixes #17181
What does this implement/fix?
This PR clarifies the documentation for
Lasso.path()to address theconfusion around the default
l1_ratio=0.5parameter.Problem
The
Lasso.path()method is inherited fromElasticNetand defaults tol1_ratio=0.5. This is inconsistent with theLassoestimator itself,which optimizes with an implicit
l1_ratio=1.0(pure L1 penalty).Changes
.. note::in theLassoclass docstring explaining thatpath()is inherited fromElasticNetwithl1_ratio=0.5defaultlasso_pathdescription in "See Also" to recommend it forcomputing true Lasso paths