Machine Learning with R: A Complete Guide to Decision Trees

Reading time:

time

min

February 10, 2021

Updated: August 22, 2022. <h2>R Decision Trees</h2> R Decision Trees are among the most fundamental algorithms in supervised machine learning, used to handle both regression and classification tasks. In a nutshell, you can think of it as a glorified collection of if-else statements. What makes these if-else statements different from traditional programming is that the logical conditions are "generated" by the machine learning algorithm, but more on that later. <blockquote>Interested in more basic machine learning guides? <a class="editor-rtfLink" href="https://wordpress.appsilon.com/r-logistic-regression/" target="_blank" rel="noopener noreferrer">Check our detailed guide on Logistic Regression with R</a>.</blockquote> Today you'll learn the basic theory behind the decision trees algorithm and also how to implement the algorithm in R. Table of contents: <ul><li><a href="#introduction">Introduction to R Decision Trees</a></li><li><a href="#data-loading">Dataset Loading and Preparation</a></li><li><a href="#modeling">Predictive Modeling with R Decision Trees</a></li><li><a href="#predictions">Generating Predictions</a></li><li><a href="#conclusion">Summary of R Decision Trees</a></li></ul> <hr /> <h2 id="introduction">Introduction to R Decision Trees</h2> Decision trees are intuitive. All they do is ask questions like is the gender male or is the value of a particular variable higher than some threshold. Based on the answers, either more questions are asked, or the classification is made. Simple! To predict class labels, the decision tree starts from the root (root node). Calculating which attribute should represent the root node is straightforward and boils down to figuring out which attribute best separates the training records. The calculation is done with the gini impurity formula. It's simple math but can get tedious to do manually if you have many attributes. After determining the root node, the tree "branches out" to better classify all of the impurities found in the root node. That's why it's common to hear decision tree = multiple if-else statements analogy. The analogy makes sense to a degree, but the conditional statements are calculated automatically. In simple words, the machine learns the best conditions for your data. Let's take a look at the following decision tree representation to drive these points further home: <img class="size-full wp-image-6590" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d5646d54b9a126ed53de_86704c27_1-2.webp" alt="Image 1 - Example decision tree" width="573" height="404" /> Image 1 - Example decision tree (<a href="https://commons.wikimedia.org/wiki/File:Decision_tree_model.png" target="_blank" rel="noopener noreferrer">source</a>) As you can see, variables Outlook?, Humidity?, and Windy? are used to predict the dependent variable - Play. You now know the basic theory behind the algorithm, and you'll learn how to implement it in R next. <h2 id="data-loading">Dataset Loading and Preparation</h2> There's no machine learning without data, and there's no working with data without libraries. You'll need these ones to follow along: <pre><code class="language-r">library(caTools) library(rpart) library(rpart.plot) library(caret) library(Boruta) library(cvms) library(dplyr) head(iris)</code></pre> As you can see, we'll use the Iris dataset to build our decision tree classifier. This is how the first couple of lines look like (output from the <code>head()</code> function call): <img class="size-full wp-image-6591" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d5652195e903584ea296_ad75d8f3_2-2.webp" alt="Image 2 - Iris dataset head" width="958" height="264" /> Image 2 - Iris dataset head The dataset is pretty much familiar to anyone with a week of experience in data science and machine learning, so it doesn't require a further introduction. Also, the dataset is as clean as they come, which will save us a lot of time in this section. The only thing we have to do before continuing to predictive modeling is to split this dataset randomly into training and testing subsets. You can use the following code snippet to do a split in a 75:25 ratio: <pre><code class="language-r">set.seed(42) sample_split <- sample.split(Y = iris$Species, SplitRatio = 0.75) train_set <- subset(x = iris, sample_split == TRUE) test_set <- subset(x = iris, sample_split == FALSE)</code></pre> And that's it! Let's start with modeling next. <h2 id="modeling">Predictive Modeling with R Decision Trees</h2> We're using the <code>rpart</code> library to build the model. The syntax for building models is identical to linear and logistic regression. You'll need to put the target variable on the left and features on the right, separated with the ~ sign. If you want to use all features, put a dot (.) instead of feature names. Also, don't forget to specify <code>method = "class"</code> since we're dealing with a classification dataset here. Here's how to train the model: <pre><code class="language-r">model <- rpart(Species ~ ., data = train_set, method = "class") model</code></pre> The output of calling <code>model</code> is shown in the following image: <img class="wp-image-6592 size-large" src="https://wordpress.appsilon.com/wp-content/uploads/2021/02/3-2-1024x302.png" alt="Image 3 - Decision tree classifier model" width="1024" height="302" /> Image 3 - Decision tree classifier model From this image alone, you can see the "rules" decision tree model used to make classifications. If you'd like a more visual representation, you can use the <code>rpart.plot</code> package to visualize the tree: <pre><code class="language-r">rpart.plot(model)</code></pre> <img class="size-full wp-image-6593" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d566a42dfbe3c048dce4_829cc4c4_4-2.webp" alt="Image 4 - Visual representation of the decision tree" width="1886" height="1306" /> Image 4 - Visual representation of the decision tree You can see how many classifications were correct (in the train set) by examining the bottom nodes. The setosa was correctly classified every time, the versicolor was misclassified for virginica 5% of the time, and virginica was misclassified for versicolor 3% of the time. It's a simple graph, but you can read everything from it. Decision trees are also useful for examining feature importance, ergo, how much predictive power lies in each feature. You can use the <code>varImp()</code> function to find out. The following snippet calculates the importance and sorts them descendingly: <pre><code class="language-r">importances <- varImp(model) importances %>% arrange(desc(Overall))</code></pre> The results are shown in the image below: <img class="size-full wp-image-6594" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d5670ca3d363ce96649f_afb9b55e_5-2.webp" alt="Image 5 - Feature importances" width="350" height="190" /> Image 5 - Feature importances If the <code>varImp()</code> doesn't do it for you and you're looking for something more advanced, look no further than Boruta. <h3>Feature Importances with Boruta</h3> Boruta is a feature ranking and selection algorithm based on the Random Forests algorithm. It will tell you if features in your dataset are relevant for making predictions. There are ways to adjust this "relevancy", such as tweaking the P-value and other parameters, but that's not something we'll go over today. A call to <code>boruta()</code> function is identical to <code>part()</code>, with the additional <code>doTrace</code> parameter for limiting the console output. The code snippet below shows you how to find the importance, and how to print them sorted in descending order: <pre><code class="language-r">library(Boruta) boruta_output <- Boruta(Species ~ ., data = train_set, doTrace = 0) rough_fix_mod <- TentativeRoughFix(boruta_output) boruta_signif <- getSelectedAttributes(rough_fix_mod) importances <- attStats(rough_fix_mod) importances <- importances[importances$decision != "Rejected", c("meanImp", "decision")] importances[order(-importances$meanImp), ]</code></pre> <img class="size-full wp-image-15282" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d56734291e95149c095f_4827e203_6-3.webp" alt="Image 6 - Boruta importances" width="510" height="190" /> Image 6 - Boruta importances In case you want to present these results visually, the package has you covered: <pre><code class="language-r">plot(boruta_output, ces.axis = 0.7, las = 2, xlab = "", main = "Feature importance")</code></pre> <img class="size-full wp-image-15284" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d5680a40386eec0a8c1b_3b98dbf7_7-2.webp" alt="Image 7 - Boruta plot" width="2186" height="1730" /> Image 7 - Boruta plot Look only for the green color - it means the feature is important. The red color would indicate the feature isn't important, and blue represents the variable used by Boruta to determine importance, so these can be discarded. The higher the box plot on the Y-axis is, the more important the feature. It's that easy! You've built and explored the model so far, but there's no use in it yet. The next section shows you how to make predictions on previously unseen data and evaluate the model. <h2 id="predictions">Generating Predictions</h2> Predicting new instances is now a trivial task. All you have to do is use the <code>predict()</code> function and pass in the testing subset. Also, make sure to specify <code>type = "class"</code> for everything to work correctly. Here's an example: <pre><code class="language-r">preds <- predict(model, newdata = test_set, type = "class") preds</code></pre> The results are shown in the following image: <img class="wp-image-6595 size-full" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d5697a511f178f8cc113_b32c7035_6-2.webp" alt="Image 8 - Decision tree predictions" width="1402" height="424" /> Image 8 - Decision tree predictions But how good are these predictions? Let's evaluate. The confusion matrix is one of the most commonly used metrics to evaluate classification models. In R, it also outputs values for other metrics, such as sensitivity, specificity, and others. Here's how you can print the confusion matrix: <pre><code class="language-r">confusionMatrix(test_set$Species, preds)</code></pre> And here are the results: <img class="wp-image-6596 size-full" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d5697e3fcb2832abb75b_fdf492c2_7-2.webp" alt="Image 9 - Confusion matrix on the test set" width="1108" height="1144" /> Image 9 - Confusion matrix on the test set As you can see, there are some misclassifications in versicolor and virginica classes, similar to what we've seen in the training set. Overall, the model is just short of 90% accuracy, which is more than acceptable for a simple decision tree classifier. But let's be honest - the amount of details in the previous image is overwhelming. What if you want to display the confusion matrix only, and display it visually as a heatmap? That's where the <code>cvms</code> package comes in. It allows you to visually represent a tibble, which is just what we need. Keep in mind the parameters in <code>plot_confusion_matrix()</code> function - all are intuitive to understand, and the values are fetched from <code>cfm</code>. Your's might be different: <pre><code class="language-r">library(cvms) cm <- confusionMatrix(test_set$Species, preds) cfm <- as_tibble(cm$table) plot_confusion_matrix(cfm, target_col = "Reference", prediction_col = "Prediction", counts_col = "n")</code></pre> <img class="size-full wp-image-15286" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b7d56ab6953e1bff271e3e_5095643a_10.webp" alt="Image 10 - Confusion matrix plot" width="1602" height="1618" /> Image 10 - Confusion matrix plot Much better, isn't it? Now you have something to present. Let's wrap things up in the following section. <hr /> <h2 id="conclusion">Summary of R Decision Trees</h2> Decision trees are an excellent introductory algorithm to the whole family of tree-based algorithms. It's commonly used as a baseline model, which more sophisticated tree-based algorithms (such as random forests and gradient boosting) need to outperform. Today you've learned basic logic and intuition behind decision trees, and how to implement and evaluate the algorithm in R. You can expect the whole suite of tree-based algorithms covered soon, so stay tuned to the Appsilon blog if you want to learn more. If you want to implement machine learning in your organization, you can always reach out to <a class="editor-rtfLink" href="https://wordpress.appsilon.com/" target="_blank" rel="noopener noreferrer">Appsilon</a> for help. <h3>Learn More</h3><ul><li><a class="editor-rtfLink" href="https://wordpress.appsilon.com/r-logistic-regression/" target="_blank" rel="noopener noreferrer">Machine Learning with R: A Complete Guide to Logistic Regression</a></li><li><a class="editor-rtfLink" href="https://wordpress.appsilon.com/r-linear-regression/" target="_blank" rel="noopener noreferrer">Machine Learning with R: A Complete Guide to Linear Regression</a></li><li><a class="editor-rtfLink" href="https://wordpress.appsilon.com/r-for-programmers/" target="_blank" rel="noopener noreferrer">What Can I Do With R? 6 Essential R Packages for Programmers</a></li><li><a class="editor-rtfLink" href="https://wordpress.appsilon.com/ai-for-wildlife-image-classification-appsilon-ai4g-project-receives-google-grant/" target="_blank" rel="noopener noreferrer">AI for Good: ML Wildlife Image Classification to Analyze Camera Trap Datasets</a></li><li><a class="editor-rtfLink" href="https://wordpress.appsilon.com/object-detection-yolo-algorithm/" target="_blank" rel="noopener noreferrer">YOLO Algorithm and YOLO Object Detection: An Introduction</a></li></ul>

Have questions or insights?

Engage with experts, share ideas and take your data journey to the next level!

Is Your Software GxP Compliant?

Download a checklist designed for clinical managers in data departments to make sure that software meets requirements for FDA and EMA submissions.

Get the Checklist