[ https://issues.apache.org/jira/browse/LUCENE-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651813#comment-14651813 ]
Tommaso Teofili commented on LUCENE-6654: ----------------------------------------- thanks Alessandro for clarifying, I've committed your patch, will take a look at LUCENE-6631 in a short while and check out if we can avoid such _protected_ methods / variables. > KNearestNeighborClassifier not taking in consideration Class ranking > -------------------------------------------------------------------- > > Key: LUCENE-6654 > URL: https://issues.apache.org/jira/browse/LUCENE-6654 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/classification > Affects Versions: 5.2.1 > Reporter: Alessandro Benedetti > Assignee: Tommaso Teofili > Priority: Minor > Labels: classification, knn > Attachments: LUCENE-6654.patch > > > Currently the KNN Classifier assign the score for a ClassificationResult, > based only on the frequency of the class in the top K results. > This is conceptually a simplification. > Actually the ranking must take a part. > If not this can happen : > Top 4 > 1) Class1 > 2) Class1 > 3) Class2 > 4) Class2 > As a result of this Top 4 , both the classes will have the same score. > But the expected result is that Class1 has a better score, as the MLT score > the documents accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org