Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9B8C2187C8 for ; Fri, 26 Feb 2016 10:53:29 +0000 (UTC) Received: (qmail 64840 invoked by uid 500); 26 Feb 2016 10:53:18 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 64733 invoked by uid 500); 26 Feb 2016 10:53:18 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 64708 invoked by uid 99); 26 Feb 2016 10:53:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Feb 2016 10:53:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0C9CF2C14F2 for ; Fri, 26 Feb 2016 10:53:18 +0000 (UTC) Date: Fri, 26 Feb 2016 10:53:18 +0000 (UTC) From: "Artem Barger (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MATH-1330) KMeans clustering algorithm, doesn't support clustering of sparse input data. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MATH-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Barger updated MATH-1330: ------------------------------- Description: Currently *KMeansPlusPlusClusterer* class require from generic parameter *T`* to extend from *Clusterable* interface, which is: {quote} public interface Clusterable { /** * Gets the n-dimensional point. * * @return the point array */ double[] getPoint(); } {quote} i.e. returns dense representation of the clusterable data, hence making it impossible to efficiently compute kmeans clustering on big dimensional, but very sparse data. I think it will be much better if *Clusterable* interface will return a *Vector* allowing usage of *SparceVector*s while clustering the data. Of course *KMeansPlusPlusClusterer* implementation and I assume other clustering implementations should be refactored accordingly to support this. was: Currently `KMeansPlusPlusClusterer` class require from generic parameter `T` to extend from `Clusterable` interface, which is: ``` public interface Clusterable { /** * Gets the n-dimensional point. * * @return the point array */ double[] getPoint(); } ``` i.e. returns dense representation of the clusterable data, hence making it impossible to efficiently compute kmeans clustering on big dimensional, but very sparse data. I think it will be much better if `Clusterable` interface will return a `Vector` allowing usage of `SparceVector`s while clustering the data. Of course `KMeansPlusPlusClusterer` implementation and I assume other clustering implementations should be refactored accordingly to support this. > KMeans clustering algorithm, doesn't support clustering of sparse input data. > ----------------------------------------------------------------------------- > > Key: MATH-1330 > URL: https://issues.apache.org/jira/browse/MATH-1330 > Project: Commons Math > Issue Type: Improvement > Reporter: Artem Barger > > Currently *KMeansPlusPlusClusterer* class require from generic parameter *T`* to extend from *Clusterable* interface, which is: > {quote} > public interface Clusterable { > /** > * Gets the n-dimensional point. > * > * @return the point array > */ > double[] getPoint(); > } > {quote} > i.e. returns dense representation of the clusterable data, hence making it impossible to efficiently compute kmeans clustering on big dimensional, but very sparse data. I think it will be much better if *Clusterable* interface will return a *Vector* allowing usage of *SparceVector*s while clustering the data. Of course *KMeansPlusPlusClusterer* implementation and I assume other clustering implementations should be refactored accordingly to support this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)