Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing ELKI on custom objects and making sense of results
    primarykey
    data
    text
    <p>I am trying to use <a href="http://elki.dbs.ifi.lmu.de/releases/release0.5.5/doc/de/lmu/ifi/dbs/elki/algorithm/clustering/SLINK.html" rel="nofollow">ELKI's SLINK implementation</a> of hierarchical clustering in my program.</p> <p>I have a set of objects (of my own type) that need to be clustered. For that, I convert them to feature vectors before clustering.</p> <p>This is how I currently got it to run and produce some result (code is in Scala):</p> <pre><code>val clusterer = new SLINK(CosineDistanceFunction.STATIC, 3) val connection = new ArrayAdapterDatabaseConnection(featureVectors) val database = new StaticArrayDatabase(connection, null) database.initialize() val result = clusterer.run(database).asInstanceOf[Clustering[_ &lt;: Model]] </code></pre> <p>Now, the result is a <code>Clustering</code> that contains elements of type <code>Model</code>. I can output them, but I don't know how to make sense of this result, especially since <code>SLINK</code> returns models of type <code>DendrogramModel</code> which does not seem to be parametrizable.</p> <p>Specifically, how can I link the results back to my original elements (the ones from which I created the variable <code>featureVectors</code> earlier)?</p> <p>I assume I need to create some kind of custom model or somehow maintain some link to the original elements through initialization and execution of the algorithm to retrieve from the result. I cannot find where to get started on this though.</p> <p>I am aware that embedding ELKI into own programs is discouraged. However, it seems that calling ELKI in some other way would not be any different: I need to cluster and map the results back to my objects during runtime of my program.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload