mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Eastman (Commented) (JIRA)" <>
Subject [jira] [Commented] (MAHOUT-843) Top Down Clustering
Date Thu, 03 Nov 2011 18:21:33 GMT


Jeff Eastman commented on MAHOUT-843:

You've not said how you plan to do a CLI for this, and why the Java classes are an improvement
over using the existing CLI calls in a script?

I don't think a multiplier approach will be workable. In general you need to provide all the
A and B arguments, for every combination of A and B including A = B. I believe by instantiating
the requisite config and executor classes you can make it work, but the CLI is a big part
of the Mahout API.

Bring on the unit tests.
> Top Down Clustering
> -------------------
>                 Key: MAHOUT-843
>                 URL:
>             Project: Mahout
>          Issue Type: New Feature
>          Components: Clustering
>    Affects Versions: 0.6
>            Reporter: Paritosh Ranjan
>              Labels: clustering, patch
>             Fix For: 0.6
>         Attachments: MAHOUT-843-patch, Top-Down-Clustering-patch
> Top Down Clustering works in multiple steps. The first step is to find comparative bigger
clusters. The second step is to cluster the bigger chunks into meaningful clusters. This can
performance while clustering big amount of data. And, it also removes the dependency of providing
input clusters/numbers to the clustering algorithm.
> The "big" is a relative term, as well as the smaller "meaningful" terms. So, the control
of this "bigger" and "smaller/meaningful" clusters will be controlled by the user.
> Which clustering algorithm to be used in the top level and which to use in the bottom
level can also be selected by the user. Initially, it can be done for only one/few clustering
algorithms, and later, option can be provided to use all the algorithms ( which suits the
case ). 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message