Train-test split for time series in ML Python - Model Pipeline Trace

Model Pipeline - Train-test split for time series

This pipeline shows how time series data is split into training and testing sets while keeping the order of data. It helps the model learn from past data and test on future data without mixing time order.

Data Flow - 2 Stages

1Original time series data

1000 rows x 1 column→Raw sequential data collected over time→1000 rows x 1 column

[10, 12, 15, 14, 16, 18, 20, ...]

↓

2Train-test split

1000 rows x 1 column→Split data by time order: first 800 rows for training, last 200 rows for testing→Train: 800 rows x 1 column, Test: 200 rows x 1 column

Train: [10, 12, ..., 25], Test: [26, 27, ..., 29]

Training Trace - Epoch by Epoch

Loss
0.5 |****
0.4 |****
0.3 |***
0.2 |**
0.1 |*
    +------------
     1 2 3 4 5 Epochs

Epoch	Loss ↓	Accuracy ↑	Observation
1	0.45	0.60	Model starts learning patterns from training data
2	0.35	0.70	Loss decreases, accuracy improves as model fits data better
3	0.28	0.78	Model continues to improve with more training
4	0.22	0.83	Training loss decreases steadily, accuracy rises
5	0.18	0.87	Model converges with good performance on training data

Prediction Trace - 4 Layers

Layer 1: Input test sample

Layer 2: Feature scaling

Layer 3: Model prediction

Layer 4: Inverse scaling

Model Quiz - 3 Questions

Why do we split time series data by order instead of randomly?

A To keep the time order and avoid future data leaking into training

B To make training and testing sets exactly equal in size

C To shuffle data for better randomness

D To reduce the number of features

Key Insight

Splitting time series data by time order ensures the model learns from past data and is tested on future data, preventing data leakage. Training shows steady improvement in loss and accuracy, and scaling inputs helps the model make better predictions.

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