Fix classification report for multilabel #150
Merged
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.
This fixes #148.
In multilabel classification we evaluate by predicting multihot vectors (ids), whereas in binary classification we predict label values (strings). Therefore, we need to supply different types of lists to the
labels
arg of sklearn's classification report: list of ids for multilabel vs. list of strings for binary.Quickfix: distinguishing these cases
Longterm: We might wanna predict also label values (strings) in multilabel classification. However, we then also need to find/implement another classification report