Multioutput-multiclass estimators have broken score method.
See original GitHub issueIt looks to me like the decision trees use accuracy_score
for their score
but accuracy_score
doesn’t document that it’s supporting multiclass-multioutput
which the trees do.
I guess the y_true == y_pred
works in this case, but it should be documented.
There’s no list of scores supporting multiclass-multioutput in the docs, and that should be fixed, too.
Update:
Calling score
in this case errors 😕
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:10 (7 by maintainers)
Top Results From Across the Web
3.3. Metrics and scoring: quantifying the quality of predictions
Estimator score method : Estimators have a score method providing a default ... And some work with binary and multilabel (but not multiclass)...
Read more >3.3. Model evaluation: quantifying the quality of predictions
Estimator score method : Estimators have a score method providing a default ... In extending a binary metric to multiclass or multilabel problems,...
Read more >Multi-Output Text Classification with Machine Learning Python
In this tutorial we will be exploring multi-output /multi-target text classification using Scikit-Learn and Python.
Read more >UserWarning: One or more of the test scores are non-finite ...
And would you rather propose that I try to use one of the multiclass-multioutput estimators (from the User Guide page)? I think ensemble....
Read more >One-vs-Rest and One-vs-One for Multi-Class Classification
This approach is commonly used for algorithms that naturally predict numerical class membership probability or score, such as: Logistic ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Wow, that’s pretty bad. We allow to train but the
score
method is broken? That seems like one more reason to kick this out.The warning is right. I guess the API allows you to make predictions using supported classifiers but user will have to define their own functions to find accuracy or other measures.