library(ggplot2)## Warning: package 'ggplot2' was built under R version 3.3.2
library(dplyr)##
## Attaching package: 'dplyr'
## The following objects are masked from 'package:stats':
##
## filter, lag
## The following objects are masked from 'package:base':
##
## intersect, setdiff, setequal, union
The movie Moneyball focuses on the “quest for the secret of success in baseball”. It follows a low-budget team, the Oakland Athletics, who believed that underused statistics, such as a player’s ability to get on base, betterpredict the ability to score runs than typical statistics like home runs, RBIs (runs batted in), and batting average. Obtaining players who excelled in these underused statistics turned out to be much more affordable for the team.
In this lab we’ll be looking at data from all 30 Major League Baseball teams and examining the linear relationship between runs scored in a season and a number of other player statistics. Our aim will be to summarize these relationships both graphically and numerically in order to find which variable, if any, helps us best predict a team’s runs scored in a season.
Let’s load up the data for the 2011 season.
load("more/mlb11.RData")
nrow(mlb11)## [1] 30
print(mlb11)## team runs at_bats hits homeruns bat_avg strikeouts stolen_bases wins new_onbase new_slug new_obs
## 1 Texas Rangers 855 5659 1599 210 0.283 930 143 96 0.340 0.460 0.800
## 2 Boston Red Sox 875 5710 1600 203 0.280 1108 102 90 0.349 0.461 0.810
## 3 Detroit Tigers 787 5563 1540 169 0.277 1143 49 95 0.340 0.434 0.773
## 4 Kansas City Royals 730 5672 1560 129 0.275 1006 153 71 0.329 0.415 0.744
## 5 St. Louis Cardinals 762 5532 1513 162 0.273 978 57 90 0.341 0.425 0.766
## 6 New York Mets 718 5600 1477 108 0.264 1085 130 77 0.335 0.391 0.725
## 7 New York Yankees 867 5518 1452 222 0.263 1138 147 97 0.343 0.444 0.788
## 8 Milwaukee Brewers 721 5447 1422 185 0.261 1083 94 96 0.325 0.425 0.750
## 9 Colorado Rockies 735 5544 1429 163 0.258 1201 118 73 0.329 0.410 0.739
## 10 Houston Astros 615 5598 1442 95 0.258 1164 118 56 0.311 0.374 0.684
## 11 Baltimore Orioles 708 5585 1434 191 0.257 1120 81 69 0.316 0.413 0.729
## 12 Los Angeles Dodgers 644 5436 1395 117 0.257 1087 126 82 0.322 0.375 0.697
## 13 Chicago Cubs 654 5549 1423 148 0.256 1202 69 71 0.314 0.401 0.715
## 14 Cincinnati Reds 735 5612 1438 183 0.256 1250 97 79 0.326 0.408 0.734
## 15 Los Angeles Angels 667 5513 1394 155 0.253 1086 135 86 0.313 0.402 0.714
## 16 Philadelphia Phillies 713 5579 1409 153 0.253 1024 96 102 0.323 0.395 0.717
## 17 Chicago White Sox 654 5502 1387 154 0.252 989 81 79 0.319 0.388 0.706
## 18 Cleveland Indians 704 5509 1380 154 0.250 1269 89 80 0.317 0.396 0.714
## 19 Arizona Diamondbacks 731 5421 1357 172 0.250 1249 133 94 0.322 0.413 0.736
## 20 Toronto Blue Jays 743 5559 1384 186 0.249 1184 131 81 0.317 0.413 0.730
## 21 Minnesota Twins 619 5487 1357 103 0.247 1048 92 63 0.306 0.360 0.666
## 22 Florida Marlins 625 5508 1358 149 0.247 1244 95 72 0.318 0.388 0.706
## 23 Pittsburgh Pirates 610 5421 1325 107 0.244 1308 108 72 0.309 0.368 0.676
## 24 Oakland Athletics 645 5452 1330 114 0.244 1094 117 74 0.311 0.369 0.680
## 25 Tampa Bay Rays 707 5436 1324 172 0.244 1193 155 91 0.322 0.402 0.724
## 26 Atlanta Braves 641 5528 1345 173 0.243 1260 77 89 0.308 0.387 0.695
## 27 Washington Nationals 624 5441 1319 154 0.242 1323 106 80 0.309 0.383 0.691
## 28 San Francisco Giants 570 5486 1327 121 0.242 1122 85 86 0.303 0.368 0.671
## 29 San Diego Padres 593 5417 1284 91 0.237 1320 170 71 0.305 0.349 0.653
## 30 Seattle Mariners 556 5421 1263 109 0.233 1280 125 67 0.292 0.348 0.640
In addition to runs scored, there are seven traditionally used variables in the data set: at-bats, hits, home runs, batting average, strikeouts, stolen bases, and wins. There are also three newer variables: on-base percentage, slugging percentage, and on-base plus slugging. For the first portion of the analysis we’ll consider the seven traditional variables. At the end of the lab, you’ll work with the newer variables on your own.
runs and one of the other numerical variables? Plot this relationship using the variable at_bats as the predictor. Does the relationship look linear? If you knew a team’s at_bats, would you be comfortable using a linear model to predict the number of runs?graph1 <- ggplot(data=mlb11, aes(x=at_bats, y=runs)) + geom_point()
graph1at_bats and runs variables. If the relationship looks linear, we can quantify the strength of the relationship with the correlation coefficient.
cor(mlb11$runs, mlb11$at_bats)## [1] 0.610627
Think back to the way that we described the distribution of a single variable. Recall that we discussed characteristics such as center, spread, and shape. It’s also useful to be able to describe the relationship of two numerical variables, such as runs and at_bats above.
at_bats and runs appears to be positive and linear. The strength of the relationship is weak to moderate. There are few outliers with at_bats above 5500 and runs above 850. Other than that there are no unusual observations.Just as we used the mean and standard deviation to summarize a single variable, we can summarize the relationship between these two variables by finding the line that best follows their association. Use the following interactive function to select the line that you think does the best job of going through the cloud of points.
plot_ss(x = mlb11$at_bats, y = mlb11$runs)## Click two points to make a line.
## Call:
## lm(formula = y ~ x, data = pts)
##
## Coefficients:
## (Intercept) x
## -2789.2429 0.6305
##
## Sum of Squares: 123721.9
After running this command, you’ll be prompted to click two points on the plot to define a line. Once you’ve done that, the line you specified will be shown in black and the residuals in blue. Note that there are 30 residuals, one for each of the 30 observations. Recall that the residuals are the difference between the observed values and the values predicted by the line:
\[ e_i = y_i - \hat{y}_i \]
The most common way to do linear regression is to select the line that minimizes the sum of squared residuals. To visualize the squared residuals, you can rerun the plot command and add the argument showSquares = TRUE.
plot_ss(x = mlb11$at_bats, y = mlb11$runs, showSquares = TRUE)## Click two points to make a line.
## Call:
## lm(formula = y ~ x, data = pts)
##
## Coefficients:
## (Intercept) x
## -2789.2429 0.6305
##
## Sum of Squares: 123721.9
Note that the output from the plot_ss function provides you with the slope and intercept of your line as well as the sum of squares.
plot_ss, choose a line that does a good job of minimizing the sum of squares. Run the function several times. What was the smallest sum of squares that you got? How does it compare to your neighbors?It is rather cumbersome to try to get the correct least squares line, i.e. the line that minimizes the sum of squared residuals, through trial and error. Instead we can use the lm function in R to fit the linear model (a.k.a. regression line).
m1 <- lm(runs ~ at_bats, data = mlb11)The first argument in the function lm is a formula that takes the form y ~ x. Here it can be read that we want to make a linear model of runs as a function of at_bats. The second argument specifies that R should look in the mlb11 data frame to find the runs and at_bats variables.
The output of lm is an object that contains all of the information we need about the linear model that was just fit. We can access this information using the summary function.
summary(m1)##
## Call:
## lm(formula = runs ~ at_bats, data = mlb11)
##
## Residuals:
## Min 1Q Median 3Q Max
## -125.58 -47.05 -16.59 54.40 176.87
##
## Coefficients:
## Estimate Std. Error t value Pr(>|t|)
## (Intercept) -2789.2429 853.6957 -3.267 0.002871 **
## at_bats 0.6305 0.1545 4.080 0.000339 ***
## ---
## Signif. codes: 0 '***' 0.001 '**' 0.01 '*' 0.05 '.' 0.1 ' ' 1
##
## Residual standard error: 66.47 on 28 degrees of freedom
## Multiple R-squared: 0.3729, Adjusted R-squared: 0.3505
## F-statistic: 16.65 on 1 and 28 DF, p-value: 0.0003388
Let’s consider this output piece by piece. First, the formula used to describe the model is shown at the top. After the formula you find the five-number summary of the residuals. The “Coefficients” table shown next is key; its first column displays the linear model’s y-intercept and the coefficient of at_bats. With this table, we can write down the least squares regression line for the linear model:
\[ \hat{runs} = -2789.2429 + 0.6305 * atbats \]
One last piece of information we will discuss from the summary output is the Multiple R-squared, or more simply, \(R^2\). The \(R^2\) value represents the proportion of variability in the response variable that is explained by the explanatory variable. For this model, 37.3% of the variability in runs is explained by at-bats.
homeruns to predict runs. Using the estimates from the R output, write the equation of the regression line. What does the slope tell us in the context of the relationship between success of a team and its home runs?m2 <- lm(runs ~ homeruns, data = mlb11)
summary(m2)##
## Call:
## lm(formula = runs ~ homeruns, data = mlb11)
##
## Residuals:
## Min 1Q Median 3Q Max
## -91.615 -33.410 3.231 24.292 104.631
##
## Coefficients:
## Estimate Std. Error t value Pr(>|t|)
## (Intercept) 415.2389 41.6779 9.963 1.04e-10 ***
## homeruns 1.8345 0.2677 6.854 1.90e-07 ***
## ---
## Signif. codes: 0 '***' 0.001 '**' 0.01 '*' 0.05 '.' 0.1 ' ' 1
##
## Residual standard error: 51.29 on 28 degrees of freedom
## Multiple R-squared: 0.6266, Adjusted R-squared: 0.6132
## F-statistic: 46.98 on 1 and 28 DF, p-value: 1.9e-07
\[ \hat{runs} = 415.2388849 + 1.8345416 * homeruns \]
at_bats slope.Let’s create a scatterplot with the least squares line laid on top.
plot(mlb11$runs ~ mlb11$at_bats)
abline(m1)The function abline plots a line based on its slope and intercept. Here, we used a shortcut by providing the model m1, which contains both parameter estimates. This line can be used to predict \(y\) at any value of \(x\). When predictions are made for values of \(x\) that are beyond the range of the observed data, it is referred to as extrapolation and is not usually recommended. However, predictions made within the range of the data are more reliable. They’re also used to compute the residuals.
atbats <- 5578
yPredicted <- -2789.2429 + 0.6305 * atbats
yPredicted## [1] 727.6861
# Philadephia Phillies `at_bats` score is 5,579
observed_df = filter(mlb11, at_bats == 5579)
yObserved = observed_df$runs
residual = yObserved - yPredictedmlb11 dataset we notice that Philadephia Phillies at_bats score is 5,579 (~5,578) with 713 runs. So, the observed runs would be close to 713, but the residual is -14.6861. Therefore we can say that our model overestimated their performance. The residual is -14.6861. To assess whether the linear model is reliable, we need to check for (1) linearity, (2) nearly normal residuals, and (3) constant variability.
Linearity: You already checked if the relationship between runs and at-bats is linear using a scatterplot. We should also verify this condition with a plot of the residuals vs. at-bats. Recall that any code following a # is intended to be a comment that helps understand the code but is ignored by R.
plot(m1$residuals ~ mlb11$at_bats)
abline(h = 0, lty = 3) # adds a horizontal dashed line at y = 0Nearly normal residuals: To check this condition, we can look at a histogram
hist(m1$residuals)or a normal probability plot of the residuals.
qqnorm(m1$residuals)
qqline(m1$residuals) # adds diagonal line to the normal prob plotConstant variability:
mlb11 that you think might be a good predictor of runs. Produce a scatterplot of the two variables and fit a linear model. At a glance, does there seem to be a linear relationship?stolen_bases variable. graph3 = ggplot(data=mlb11, aes(x=stolen_bases, y=runs)) + geom_point()
graph3m3 = lm(runs ~ stolen_bases, data=mlb11)\[ \hat{runs} = 677.3074253 + 0.1490629 * stolen\_bases \]
stolen_bases and runs. At best we can say that there is a very week relationship.runs and at_bats? Use the R\(^2\) values from the two model summaries to compare. Does your variable seem to predict runs better than at_bats? How can you tell?m1 = lm(runs ~ at_bats, data = mlb11)
m3 = lm(runs ~ stolen_bases, data = mlb11)
rSquaredAtBats = summary(m1)$r.squared
rSquaredStBases = summary(m3)$r.squared
rSquaredAtBats## [1] 0.3728654
rSquaredStBases## [1] 0.002913993
at_bats is 0.3728654 and the R\(^2\) value for variable stolen_bases is 0.002914. Since R\(^2\) value of at_bats is significantly higher than R\(^2\) value of stolen_bases, we can say that at_bats is a better predictor than stolen_bases.runs and each of the other five traditional variables. Which variable best predicts runs? Support your conclusion using the graphical and numerical methods we’ve discussed (for the sake of conciseness, only include output for the best variable, not all five).graph4 = ggplot(data=mlb11, aes(x=bat_avg, y=runs)) + geom_point()
graph4m4 = lm(runs ~ bat_avg, data=mlb11)
rSquaredBatAvg = summary(m4)$r.squared
rSquaredBatAvg## [1] 0.6560771
\[ \hat{runs} = -642.8189333 + 5242.2290794 * bat\_avg \]
bat_avg is 0.6560771. bat_avg variable appears to show the best positive relationship with runs. The scaterplot also shows a linear trend.new_obs seems to have the highest R\(^2\) value of all 10 variables. Therefore, we can say that the variable new_obs is the best predictor of runs.m10 = lm(runs ~ new_obs, data = mlb11)
plot(m10$residuals ~ mlb11$new_obs)
abline(h = 0, lty = 3) # adds a horizontal dashed line at y = 0hist(m10$residuals)qqnorm(m10$residuals)
qqline(m10$residuals) # adds diagonal line to the normal prob plotThis is a product of OpenIntro that is released under a Creative Commons Attribution-ShareAlike 3.0 Unported. This lab was adapted for OpenIntro by Andrew Bray and Mine Çetinkaya-Rundel from a lab written by the faculty and TAs of UCLA Statistics.