See the scikit-learn cross validation documentation for a fuller discussion of cross validation. This document only describes the extensions made to support Dask arrays.
The simplest way to split one or more Dask arrays is with
In : import dask.array as da In : from dask_ml.datasets import make_regression In : from dask_ml.model_selection import train_test_split In : X, y = make_regression(n_samples=125, n_features=4, random_state=0, chunks=50) In : X Out: dask.array<normal, shape=(125, 4), dtype=float64, chunksize=(50, 4), chunktype=numpy.ndarray>
The interface for splitting Dask arrays is the same as scikit-learn’s version.
In : X_train, X_test, y_train, y_test = train_test_split(X, y) In : X_train # A dask Array Out: dask.array<concatenate, shape=(112, 4), dtype=float64, chunksize=(45, 4), chunktype=numpy.ndarray> In : X_train.compute()[:3] Out: array([[ 0.99177505, -0.9955949 , 0.96753301, 1.39729242], [-2.48417857, -1.51302803, 1.18438 , 0.64385103], [-1.05879148, -0.89722898, 0.96089406, -0.97585992]])
While it’s possible to pass dask arrays to
sklearn.model_selection.train_test_split(), we recommend
using the Dask version for performance reasons. There are two major difference that let make the Dask version
First, the Dask version shuffles blockwise. In a distributed setting, shuffling between blocks may require sending large amounts of data between machines, which can be slow. However, if there’s a strong pattern in your data, you’ll want to perform a full shuffle.
Second, the Dask version avoids allocating large intermediate NumPy arrays storing the indexes for slicing.
For very large datasets, creating and transmitting
np.arange(n_samples) can be expensive.