[ 
https://issues.apache.org/jira/browse/FLINK-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628551#comment-14628551
 ] 

ASF GitHub Bot commented on FLINK-2131:
---------------------------------------

Github user thvasilo commented on the pull request:

    https://github.com/apache/flink/pull/757#issuecomment-121713405
  
    Hello Sachin,
    
    I'm currently on vacation until August so someone else needs to so the
    reviews until then.
    
    Regards,
    Theodore
    
    -- 
    Sent from a mobile device. May contain autocorrect errors.
    On Jul 15, 2015 3:50 PM, "Sachin Goel" <[email protected]> wrote:
    
    > @thvasilo <https://github.com/thvasilo> I've incorporated different
    > initialization strategies in the KMeans algorithm itself. Please review.
    >
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/flink/pull/757#issuecomment-121605233>.
    >



> Add Initialization schemes for K-means clustering
> -------------------------------------------------
>
>                 Key: FLINK-2131
>                 URL: https://issues.apache.org/jira/browse/FLINK-2131
>             Project: Flink
>          Issue Type: Task
>          Components: Machine Learning Library
>            Reporter: Sachin Goel
>            Assignee: Sachin Goel
>
> The Lloyd's [KMeans] algorithm takes initial centroids as its input. However, 
> in case the user doesn't provide the initial centers, they may ask for a 
> particular initialization scheme to be followed. The most commonly used are 
> these:
> 1. Random initialization: Self-explanatory
> 2. kmeans++ initialization: http://ilpubs.stanford.edu:8090/778/1/2006-13.pdf
> 3. kmeans|| : http://theory.stanford.edu/~sergei/papers/vldb12-kmpar.pdf
> For very large data sets, or for large values of k, the kmeans|| method is 
> preferred as it provides the same approximation guarantees as kmeans++ and 
> requires lesser number of passes over the input data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to