[
https://issues.apache.org/jira/browse/MAHOUT-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129078#comment-13129078
]
Jeff Eastman edited comment on MAHOUT-843 at 10/17/11 6:55 PM:
---------------------------------------------------------------
Ok, but how is this better than using the existing jobs?
bin/mahout canopy <...>
bin/mahout separateclusters <...> // your new postprocessor job
for i in <separateclusters output> do
bin/mahout kmeans <...>
done
There is a bit of global argument coupling needed between the -o of canopy and
the -i of separateclusters, also between the -o of separateclusters and the -i
of kmeans. Are there any other argument couplings? It seems to me that the new
postprocessor would be a useful addition to Mahout and the user would then be
responsible for wiring the three steps together. Can you think of a way to
improve upon this?
This problem also seems to be similar to the Mahout recommender code: all done
by plugging existing Java classes together in a program which is specific for
each problem domain/application. There is no CLI for doing this because of the
same sorts of issues we are discussing here.
was (Author: jeastman):
Ok, but how is this better than using the existing jobs?
bin/mahout canopy <...>
bin/mahout separateclusters <...> // your new postprocessor job
bin/mahout kmeans <...>
There is a bit of global argument coupling needed between the -o of canopy and
the -i of separateclusters, also between the -o of separateclusters and the -i
of kmeans. Are there any other argument couplings? It seems to me that the new
postprocessor would be a useful addition to Mahout and the user would then be
responsible for wiring the three steps together. Can you think of a way to
improve upon this?
This problem also seems to be similar to the Mahout recommender code: all done
by plugging existing Java classes together in a program which is specific for
each problem domain/application. There is no CLI for doing this because of the
same sorts of issues we are discussing here.
> Top Down Clustering
> -------------------
>
> Key: MAHOUT-843
> URL: https://issues.apache.org/jira/browse/MAHOUT-843
> Project: Mahout
> Issue Type: New Feature
> Components: Clustering
> Affects Versions: 0.6
> Reporter: Paritosh Ranjan
> Labels: clustering, patch
> Fix For: 0.6
>
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
