Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/1898#discussion_r63497505
--- Diff: docs/apis/batch/libs/ml/cross_validation.md ---
@@ -0,0 +1,175 @@
+---
+mathjax: include
+title: Cross Validation
+
+# Sub navigation
+sub-nav-group: batch
+sub-nav-parent: flinkml
+sub-nav-title: Cross Validation
+---
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+* This will be replaced by the TOC
+{:toc}
+
+## Description
+
+ A prevalent problem when utilizing machine learning algorithms is
*overfitting*, or when an algorithm "memorizes" the training data but does a
poor job extrapolating to out of sample cases. A common method for dealing with
the overfitting problem is to hold back some subset of data from the original
training algorithm and then measure the fit algorithm's performance on this
hold-out set. This is commonly known as *cross validation*. A model is trained
on one subset of data and then *validated* on another set of data.
+
+## Cross Validation Strategies
+
+There are several strategies for holding out data. FlinkML has convenience
methods for
+- Train-Test Splits
+- Train-Test-Holdout Splits
+- K-Fold Splits
+- Multi-Random Splits
+
+### Train-Test Splits
+
+The simplest method of splitting is the `trainTestSplit`. This split takes
a DataSet and a parameter *fraction*. The *fraction* indicates the portion of
the DataSet that should be allocated to the training set. This split also takes
two additional optional parameters, *precise* and *seed*.
+
+By default, the Split is done by randomly deciding weather or not an
observation is assigned to the training DataSet with probability = *fraction*.
When *precise* is `true` however, additional steps are taken to ensure the
training set is as close as possible to the length of the DataSet $\cdot$
*fraction*.
--- End diff --
typo: weather --> whether
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
