commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Tompkins (JIRA)" <>
Subject [jira] [Updated] (MATH-1315) MultiKMeansPlusPlusClusterer buggy for alternative evaluators
Date Wed, 12 Apr 2017 00:11:41 GMT


Rob Tompkins updated MATH-1315:
    Fix Version/s: 4.0

> MultiKMeansPlusPlusClusterer buggy for alternative evaluators
> -------------------------------------------------------------
>                 Key: MATH-1315
>                 URL:
>             Project: Commons Math
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Thorsten Schäfer
>             Fix For: 4.0
>         Attachments: MATH-1315.patch
> I just looked into the source code for the MultiKMeansPlusPlusClusterer and realized
that it would return null in case of an alternative evaluator that favors bigger values instead
of smaller ones:
> The basic idea of the clustering method is that we perform n clusterings and choose the
best result. The decision what's the best result is performed by the evaluator, which by default
assumes smaller values are better. 
> According to the documentation, we can also provide a different evaluator, which for
instance would decide that bigger values are better, but given we initialize the best value
with Double.POSITIVE_INFINITY in method MultiKMeansPlusPlusClusterer.cluster(Collection<T>),
we would never find a "better" result and thus always return null. 

This message was sent by Atlassian JIRA

View raw message