Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Missing type support in unique_labels() utility
See original GitHub issueDescription
sklearn.utils.multiclass unique_labels() does not yet allow "multiclass-multioutput" input type for y .
See this comment in the code: https://github.com/scikit-learn/scikit-learn/blob/3a48f0ab7cf75dea55f313da6b33f7b6772d28af/sklearn/utils/multiclass.py#L53
This type is used by multilabel classifiers such as sklearn.tree.DecisionTreeClassifier.
https://github.com/scikit-learn/scikit-learn/blob/4bba21659c68d65b4555ea86751aac1fab9fd8e4/sklearn/tree/tree.py#L763
So I propose to add support for this. At first glance, it doesn’t appear to be difficult. Is there any reason not to to this?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Not a significant issue for me after all. Closing to reduce clutter. Thanks.
Detecting output types is really fragile 😕 would be nice if we could warn better… Or get rid of
multioutput multiclassand make it less fragile 😉