You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I use train_test_split the indeces are shuffled sometimes, sometimes not. Also if you use the scoring method of an SVR estimator multiple times in a row with the same estimator and the same parameters, it can produce different scores.
To Reproduce
well you should be able to write a simple reproducer yourself, since this occurs frequently.
Expected behavior
No bugs.
Environment:
Windows 10
Anaconda
The text was updated successfully, but these errors were encountered:
sklearnex.svm.SVR is also buggy. Using .predict() on the same X_test set in a pipeline with preprocessors and encoders yiels different predictions. Just do it like ~50 times in a row and you will see what I mean.
This is also reproducible with basic examples like:
Maybe this happens because I use AMD CPU or something.
nilslacroix
changed the title
Train_test_split index bug, scoring bug in SVR
Predict and Scoring Bug in sklearnex.svm.SVR and Train_test_split index bug
Apr 25, 2022
I confirmed this bug happens (at least the scoring) when using AMD Hardware. Please at least implement a warning message, which checks the current CPU so people get a notice that this library will only work with intel specific hardware.
Describe the bug
When I use train_test_split the indeces are shuffled sometimes, sometimes not. Also if you use the scoring method of an SVR estimator multiple times in a row with the same estimator and the same parameters, it can produce different scores.
To Reproduce
well you should be able to write a simple reproducer yourself, since this occurs frequently.
Expected behavior
No bugs.
Environment:
The text was updated successfully, but these errors were encountered: