Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

eshilts
Copy link
Contributor

@eshilts eshilts commented Jan 9, 2014

Partially completed #2709. I'm opening this pull request to get feedback on the implementation of best_*_ attributes for LassoCV and ElasticNetCV and ideas for how to test this further. I noticed some inconsistencies between LassoCV/ElasticNetCV and GridCV with Lasso/ElasticNet which makes it difficult to validate against GridCV.

I'll continue with RidgeCV, LassoLarsCV, etc assuming this looks good so far.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that I'm always returning ElasticNet(...), even for Lasso models. This shouldn't make a difference as far as actual predictions go, but it may lead to confusion for a user who expects back a Lasso(...) model from LassoCV.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed

we should sync with #2598 as it contains fixes too.

I need to find the time to review all this. Sorry guys

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 670cfb8 on eshilts:CV-attributes into 7de3d96 on scikit-learn:master.

@MechCoder
Copy link
Member

@eshilts What is the status on this PR? I would like to see this merged

@eshilts
Copy link
Contributor Author

eshilts commented Oct 11, 2014

Sorry for the delay. I'll get on it this week.

@MechCoder
Copy link
Member

Hi, if you are busy. I could cherry-pick your commits onto a new branch and finish this up. Should not take me much time.

@agramfort
Copy link
Member

addressed by @raghavrv recently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants