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

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

GitHub user thvasilo opened a pull request:

    https://github.com/apache/flink/pull/899

    [FLINK-2342] [ml]  Add new fit operation and more tests for StandardScaler

    StandardScaler currently has a transform operation for types (Vector, 
Double), but no corresponding fit operation.
    
    The test cases also do not cover all the possible types that we can call 
fit and transform on.
    
    This PR addresses this, and removes some unused code.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/thvasilo/flink scaler-extra-tests

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/899.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #899
    
----
commit aa18b3dc82475c179f56fad25363184a47c36c2f
Author: Theodore Vasiloudis <[email protected]>
Date:   2015-07-10T09:34:32Z

    More tests and a new operation for StandardScaler

----


> Add new fit operation and more tests for StandardScaler
> -------------------------------------------------------
>
>                 Key: FLINK-2342
>                 URL: https://issues.apache.org/jira/browse/FLINK-2342
>             Project: Flink
>          Issue Type: Improvement
>          Components: Machine Learning Library
>            Reporter: Theodore Vasiloudis
>            Assignee: Theodore Vasiloudis
>            Priority: Minor
>              Labels: ML
>             Fix For: 0.10
>
>
> StandardScaler currently has a transform operation for types (Vector, 
> Double), but no  corresponding fit operation.
> The test cases also do not cover all the possible types that we can call fit 
> and transform on.



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

Reply via email to