# Cross-Validation the Wrong Way and Right Way With Feature Selection

Cross-validation is a popular technique to evaluate true model accuracy. However, cross-validation is not as straight forward as it may seem and can provide false confidence. This means that it is easy to overfit when not done properly. So, how can we avoid doing cross-validation the wrong way? First, I will be going over one pitfall of cross-validation called data leakage.

# What is Data Leakage?

The PC Magazine Encyclopedia defines data leakage as:

The unauthorized transfer of classified information from a computer or datacenter to the outside world.

The classified information in terms of cross-validation is the data in the test set. A computer or data center would be the test set and the outside world the training set.

In other words, data leakage can happen when we are learning from both, the testing and training set. If we do any pre-processing outside the cross-validation algorithm, we will bias our results and most likely overfit our model.

So, consider a scenario where we want to reduce our predictors. We can do that by stepwise selection or for example based on correlations. So we are doing some sort of variable selection and then applying k-fold cross-validation to our data set to estimate the test set error.

The problem arises, when using our training and testing data set for variable selection. This results in a biased estimate of our model accuracy. In other words, our k-fold cross-validation accuracy is an overestiamte of the true test set error.

What we are going to cover:

• We will be presenting how to do cross-validation the wrong way and the right way. We will be looking at a real data set (Pima Indians Data Set).
• In order to make the difference between a right cross-validation loop and a wrong cross-validation loop more visible, we will be creating a random data set and compare accuracies. Then, we will be visualizing the difference between the right and wrong cross-validation method.
• What kind of pre-processing is allowed before applying cross-validation? Which procedures lead to overfitting?

Let’s get started!

# Doing Cross-Validation the Wrong Way (Pima Indians Data Set)

Here is an example of the Pima Indians data set. There are 9 variables in the data set. One response variable (being diabetic or not) and 8 explanatory variables.

After some pre-processing of the data, we are left with 392 rows. Because we do not have many samples (only 392) we will be doing 5-fold cross-validation instead of 10-fold cross-validation.

We will be getting some help from the `caret` package.

### What Happens in our Cross-Validation Loop?

In the section below, there is a short explanation of our cross-validation loop:

1.  First, we are creating 5 folds with the `caret` package. Each fold has roughly the same amount of data.
2. Then we are creating a testing and a training data set. The testing data set consists of 1 out of 5 folds and the training set consists of 4 out of 5 folds.
3. After that, we are doing some variable selection based on the highest correlation. This is the step where the mistake happens. In this step, we are combining the test and training sets. Based on the entire data set, we are finding the highest correlated variables with our response variable.

This is wrong!!!

Instead, we should only use the training data set to find the variables with the highest correlations. Hence, not touching the test set. Let’s continue in our loop.

1. In the next step, we are picking the two variables with the highest correlation.
2. Then we are plugging these two variables in our logistic regression model.
3. After that, we are predicting our outcomes and rounding the predicted probability scores to 0 or 1.
4. Then, we are putting the predicted and actual outcomes in a data frame, converting these variables to factors, and using the `confusionMatrix` function to evaluate our model accuracy.

In between, I inserted a print statement so you can see which variables we are selecting in each fold.

Because we are using the entire data set to select features, we are getting the same features in each loop. Namely `Glucose` and `Age`. This is exactly how you dcross-validation the wrong way.

# Doing Cross-Validation the Right Way (Pima Indians Data Set)

Let’s see how to do cross-validation the right way.

The code below is basically the same as the above one with one little exception.

In step three, we are only using the training data to do feature selection. This ensures, that there is no data leakage and we are not using information that is in the test set to help with feature selection.

After we are done, we can see that during our forth loop, the algorithm chooses `Glucose` and `Insulin` as being the “best” predictors (based on the correlation coefficient). However, for all other loops the algorithm still chooses `Glucose` and `Age` as our “best” predictors.

So the questions we have to answer are now: “How are we supposed to continue?” and “Is the error from the right cross-validation loop our test set error?”

The next step is to choose features that have the maximum number of votes. In this case it is `Glucose` and `Age`. Now, we have to do another round of cross-validation on only these set of features.

Luckily in this example, doing feature selection and cross-validation the wrong way and the right way, gave us identical features. So, our cross-validation test set error in the first code block would not be biased.

However, it could have been that our second code block, where we did cross-validation the right way, had given us completely different features. Then, the test set error in the first code block would have been extremely biased.

Getting extremely biased results when doing cross-validation the wrong way usually happens with wider data sets. So, with data sets that have hundreds of predictors and just a small amount of samples. (You will see that later on our simulated data).

So, as we said, we are doing cross-validation again with the majority of features selected in code block 2 (`Glucose` and `Age`). This is because cross-validation should only be used to measure how a SINGLE model performs on a given test set. If we are comparing models that have `Glucose` and `Age` with models that have `Glucose` and `Insulin` as predictors, then we are not comparing the performance correctly.

### Cross-Validation With the Caret Package

The following code does everything for us. So, we are not ending up with a lot of lines of code.

The accuracy here is different from the accuracy we got in our first code block even though we used the same features. This is because the `caret` functions are using different splits for the data.

# Doing Cross-Validation the Right Way With a Simulated Data Set

Now let’s consider an example where the accuracy between doing cross-validation the wrong way and the right way is more evident.

First, we are creating 100 samples, 5000 predictors, and 1 response variable randomly. Hence, we have a very wide data set. We know exactly how the explanatory variables are related to the response variable.  The answer is that there is no relationship. All the correlation that will be created occurs by chance.

So theoretically, the accuracy of the test set should be 50%. In other words, it shouldn’t be better than guessing.

Let’s see what happens when we perform cross-validation the right way.

As expected, we are getting around 48% accuracy which is no better than guessing.

Moreover, we are noticing that our predictors are always different and changing. This indicates that there is no consistency across our data set. Choosing predictors is random and we should conclude that we can’t build a predictive model based on the data set.

What would have happened however, if we had included the test data? So, if we had done cross-validation the wrong way?

# Doing Cross-Validation the Wrong Way With a Simulated Data Set

Let’s find out. Below is the code where we do cross-validation the wrong way. Again, the only difference is that we are including the test data set when choosing the predictors with the highest correlation coefficient.

It is no surprise, that we see the same two predictors for each iteration. `V4827` and `V1293` pop up every time.

If we had no idea that we have applied cross-validation the wrong way, choosing `V4827` and `V1293` seems like a reasonable choice to make. Moreover, these predictors give us 70% accuracy. This is very good depending on the problem at hand.

Thankfully, we know that there is no relationship between predictors and response variable. Therefore, a 70% accuracy is a gross overestimation of the test set accuracy.

Let’s compare our results to the `caret` package.

### Cross-Validation With the Caret Package

And as expected, the caret package gives us a similar result to our loop. A 69% accuracy is also a great over estimation of the real test set accuracy, which we know is 50%.

In conclusion, cross-validation seems like a very straight forward concept. However, in practice it is not as easy and we do have to follow certain practices to not overfit a model.

So far, we have talked a lot about how to choose features correctly using cross-validation. However, it is also worth noting what we can do before doing cross-validation.

So what kind of pre-processing is allowed vs. what do we have to include inside the cross-validation loop?

# Pre-processing Inside the Cross-Validation Loop Vs. Outside the Loop

Everything is allowed that operates on each sample independently. Therefore, methods like smoothing or normalization are okay. This is because it only works on one sample at a time and doesn’t affect other samples.

Other techniques like centering is a problem because we are subtracting the mean of the entire column from every single observation in the column. Therefore, centering has to be done in the cross-validation loop. Same procedure as with feature selection.

I you enjoyed this blog post, you might also like the post where I am talking about the bias-variance trade-off in machine learning.

If you have any questions or suggestions for improvements, please let me know in the comments below.

### Other Recources

You can find out more about what you can do before cross-validation and what you have to put inside the loop here.

When you want to find out more about the topic then this is a great post about a Kaggle competition, cross-validation, and overfitting the public leaderboard.

Other great resources that show code examples of how to do cross-validation the wrong and right way can be found here and here.

Similar Topics: