Train-test split for time series in ML Python

Introduction

We split time series data into training and testing parts to check if our model can predict future values well, without cheating by looking ahead.

When you want to predict stock prices using past data.

When forecasting weather based on historical temperature records.

When analyzing sales trends to plan future inventory.

When monitoring sensor data to detect equipment failures.

When building models that learn from sequences over time.

Syntax

ML Python

train_size = int(len(data) * 0.8)
train = data[:train_size]
test = data[train_size:]

We split data by slicing, keeping the order intact because time matters.

Avoid random shuffling since it breaks the time order and can cause wrong results.

Examples

Splits 10 data points into 7 for training and 3 for testing, keeping order.

ML Python

data = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
train_size = int(len(data) * 0.7)
train = data[:train_size]
test = data[train_size:]

Using pandas Series, first 80 points for training, last 20 for testing.

ML Python

import pandas as pd
series = pd.Series(range(100))
train = series[:80]
test = series[80:]

Sample Model

This code creates a simple linear time series, splits it by time, trains a model on the past, and tests on future points.

ML Python

import numpy as np
from sklearn.linear_model import LinearRegression
from sklearn.metrics import mean_squared_error

# Create a simple time series: y = 2*x + noise
np.random.seed(0)
x = np.arange(50).reshape(-1, 1)
y = 2 * x.flatten() + np.random.normal(0, 5, 50)

# Split data: first 40 for training, last 10 for testing
train_size = 40
x_train, y_train = x[:train_size], y[:train_size]
x_test, y_test = x[train_size:], y[train_size:]

# Train linear regression model
model = LinearRegression()
model.fit(x_train, y_train)

# Predict on test data
y_pred = model.predict(x_test)

# Calculate mean squared error
mse = mean_squared_error(y_test, y_pred)

print(f"Mean Squared Error on test data: {mse:.2f}")
print(f"Predictions: {y_pred.round(2)}")

Important Notes

Always keep the time order when splitting time series data.

Test data should come after training data in time to simulate real forecasting.

Random shuffling is okay for regular data but not for time series.

Summary

Train-test split for time series keeps data order to respect time flow.

Use slicing to separate past (train) and future (test) data.

This helps check if the model can predict future values well.

Practice

1. Why is it important to keep the order of data when doing a train-test split for time series?

easy

A. Because time series data depends on the order of events and future data should not be used to predict past data.

B. Because random shuffling improves model accuracy in time series.

C. Because train and test sets must have the same number of samples.

D. Because test data should always come before train data.

Solution

1. Step 1: Understand time series data nature

   Time series data is sequential and depends on the order of events over time.

2. Step 2: Importance of order in train-test split

   Using future data to predict past data breaks the time flow and causes unrealistic model evaluation.

3. Final Answer:

   Because time series data depends on the order of events and future data should not be used to predict past data. -> Option A

4. Quick Check:

   Keep order to respect time flow = A [OK]

Hint: Always keep time order to avoid future data leakage [OK]

Common Mistakes:

• Randomly shuffling time series data
• Mixing future data into training
• Ignoring time dependency

2. Which of the following Python code snippets correctly splits a time series dataset data into 80% train and 20% test sets while preserving order?

easy

A. train = data[:int(len(data)*0.8)]
test = data[int(len(data)*0.8):]

B. train = data.sample(frac=0.8)
test = data.drop(train.index)

C. train = data[int(len(data)*0.2):]
test = data[:int(len(data)*0.2)]

D. train = data.shuffle().iloc[:80]
test = data.shuffle().iloc[80:]

Solution

1. Step 1: Understand slicing for time series split

   We use slicing to keep the order: first 80% for training, last 20% for testing.

2. Step 2: Check each code snippet

   train = data[:int(len(data)*0.8)] test = data[int(len(data)*0.8):] slices data correctly without shuffling. Options B and D shuffle data, breaking order. train = data[int(len(data)*0.2):] test = data[:int(len(data)*0.2)] reverses train and test.

3. Final Answer:

   train = data[:int(len(data)*0.8)] test = data[int(len(data)*0.8):] -> Option A

4. Quick Check:

   Slicing without shuffle = C [OK]

Hint: Use slicing, not shuffle, to keep time order [OK]

Common Mistakes:

• Using sample() which shuffles data
• Reversing train and test slices
• Shuffling data before splitting

3. Given the following code, what will be the length of test if data has 1000 samples?

split_index = int(len(data) * 0.75)
train = data[:split_index]
test = data[split_index:]

medium

A. 750

B. 250

C. 1000

D. 500

Solution

1. Step 1: Calculate split index

   split_index = int(1000 * 0.75) = 750

2. Step 2: Calculate test length

   test = data[750:] means test has samples from index 750 to 999, total 1000 - 750 = 250 samples.

3. Final Answer:

   250 -> Option B

4. Quick Check:

   Test length = total - train length = 250 [OK]

Hint: Test size = total samples minus train size [OK]

Common Mistakes:

• Confusing train size with test size
• Forgetting zero-based indexing
• Using float instead of int for index

4. You wrote this code to split a time series dataset data:

from sklearn.model_selection import train_test_split
train, test = train_test_split(data, test_size=0.2)

What is the main problem with this approach?

medium

A. test_size=0.2 is too small for time series

B. train and test sets will have overlapping samples

C. train_test_split cannot handle numeric data

D. train_test_split shuffles data by default, breaking time order

Solution

1. Step 1: Understand train_test_split default behavior

   By default, train_test_split shuffles data before splitting.

2. Step 2: Why shuffling is a problem for time series

   Shuffling breaks the time order, causing future data to leak into training, invalidating model evaluation.

3. Final Answer:

   train_test_split shuffles data by default, breaking time order -> Option D

4. Quick Check:

   Default shuffle breaks time order = B [OK]

Hint: train_test_split shuffles unless shuffle=False [OK]

Common Mistakes:

• Ignoring shuffle=True default
• Assuming test_size controls order
• Thinking train_test_split is time-series aware

5. You have daily sales data for 3 years and want to train a model to predict future sales. Which approach correctly splits the data to train on the first 2.5 years and test on the last 0.5 year, ensuring no data leakage?

hard

A. train = data[int(len(data)*0.5):]
test = data[:int(len(data)*0.5)]

B. train = data.sample(frac=0.83)
test = data.drop(train.index)

C. train = data[:int(len(data)*5/6)]
test = data[int(len(data)*5/6):]

D. train = data.shuffle().iloc[:900]
test = data.shuffle().iloc[900:]

Solution

1. Step 1: Calculate split fraction for 2.5 years out of 3 years

   2.5 years / 3 years = 5/6 ≈ 0.8333, so train is first 5/6 of data.

2. Step 2: Use slicing to split data preserving order

   train = data[:int(len(data)*5/6)] test = data[int(len(data)*5/6):] slices data correctly from start to 5/6 for train, and last 1/6 for test, preserving time order and avoiding leakage.

3. Final Answer:

   train = data[:int(len(data)*5/6)] test = data[int(len(data)*5/6):] -> Option C

4. Quick Check:

   Slice first 5/6 for train, last 1/6 for test = A [OK]

Hint: Split by slicing using fraction of total length [OK]

Common Mistakes:

• Using random sampling instead of slicing
• Reversing train and test sets
• Shuffling data before splitting