-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
ENH Support float32 in SGDClassifier and SGDRegressor #25587
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
thomasjpfan
merged 14 commits into
scikit-learn:main
from
OmarManzoor:sgd_float32_support
Feb 27, 2023
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
7e46e43
ENH Support float32 in SGDClassifier and SGDRegressor
OmarManzoor 09320c1
Fix existing tests
OmarManzoor 027f728
Add tests
OmarManzoor 80c8f60
Add a function in sgd_fast to call the respective 64 or 32 function
OmarManzoor 5ca63a1
Refactoring
OmarManzoor c5d96e9
Fix the tests by adjusting the iterations
OmarManzoor 674e329
Add changelog entry
OmarManzoor 156c5d0
Add preserves_dtype in _more_tags
OmarManzoor 0be5a71
PR suggestions
OmarManzoor 3459d9a
Merge branch 'main' into sgd_float32_support
OmarManzoor 463d2a1
Merge branch 'main' into sgd_float32_support
OmarManzoor 23b3977
Merge branch 'main' into sgd_float32_support
OmarManzoor 7daef3e
Merge branch 'main' into sgd_float32_support
OmarManzoor cb3875e
Applied PR suggestions
OmarManzoor File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
When I put on my "numerical computing on a CPU hat", I tend to think that
float32
input dtypes should have accumulators offloat64
. Concretely,WeightVector32
keeps internal statistics asfloat64
and upcast data as it is processing thefloat32
input. In any case, I think this PR can be accepted as is and any updates toWeightVector32
can be done as a follow up.@jjerphan @jeremiedbb What do you think?
XREF: For reference, PyTorch uses a
float64
accumulator forfloat32
inputs on CPUS.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.
I think using float64 accumulator when on CPU is the best thing to do. We do it at several places within scikit-learn. SciPy also does this for its distance metrics' implementations.
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.
I opened #25721 to force
WeightVector32
to use afloat64
accumulator.