Skip to content
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

Elastic Net Sparse co-ordinate descent doesn't take the maxium of the absolute value of the weight #10992

Craigacp opened this issue Apr 17, 2018 · 2 comments


Copy link

@Craigacp Craigacp commented Apr 17, 2018

In cd_fast.pyx, the function sparse_enet_coordinate_descent at lines 483 & 484 doesn't take the absolute value of the weight to check the max, it uses the signed value. This means it will ignore negative updates, and probably trigger the duality gap check more frequently than it should. Looking at lines 270 and 271 of enet_coordinate_descent the absolute value of the weight is used.

I think this is a replica of issue #283, which was fixed many years ago in enet_coordinate_descent, enet_coordinate_descent_gram and enet_coordinate_descent_multi_task.

agramfort added a commit to agramfort/scikit-learn that referenced this issue Apr 18, 2018
Copy link

@agramfort agramfort commented Apr 18, 2018

@Craigacp can you check #10995 if this is what you suggested?


Copy link

@Craigacp Craigacp commented Apr 18, 2018

@agramfort, yep that's it. Sorry I couldn't do a pull request, it would have taken a while to get approval from my management.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants