typos and expanded discussion of interactions, adding links, etc.

[stats_class_2020.git] / psets / pset8-worked_solution.rmd

---
title: "Problem set 8: Worked solutions"
subtitle: "Statistics and statistical programming  \nNorthwestern University  \nMTS 525"
author: "Aaron Shaw"
date: "November 23, 2020"
output:
  html_document:
    toc: yes
    toc_depth: 3
    toc_float:
      collapsed: true
      smooth_scroll: true
    theme: readable
  pdf_document:
    toc: yes
    toc_depth: '3'
  header-includes:
  - \newcommand{\lt}{<}
  - \newcommand{\gt}{>}
---

```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE, message=FALSE, tidy='styler')
```

# Import libraries

I'll start by loading some useful libraries...
```{r dependencies}
library(openintro)
library(tidyverse)
library(ggfortify)
library(haven)
```

# Part I: Mario kart replication/extension  

## Import data and setup
```{r}
data(mariokart)

mariokart
```

To make things a bit easier to manage, I'll select the variables I want to use in the analysis and do some cleanup. Note that I convert the `cond_new` and `stock_photo` variables to logical `TRUE/FALSE` values first (using boolean comparisons) and then coerce them to be numeric values (using `as.numeric()`). This results in 1/0 values corresponding to the observations shown/described in Figure 9.13 and 9.14 on p. 365 of the textbook.

```{r}
mariokart <- mariokart %>% 
  select(
    price = total_pr, cond_new = cond, stock_photo, duration, wheels
  ) %>% mutate(
    cond_new = as.numeric(cond_new == "new"),
    stock_photo = as.numeric(stock_photo == "yes")
  ) 

mariokart
```

Now let's summarize and explore the variables in our model. I'll calculate summary statistics for each, univariate density plots for the continuous measures, boxplots for the dichotomous indicators, and some bivariate plots with each predictor and the outcome variable.

```{r}
summary(mariokart)

sd(mariokart$price)
sd(mariokart$duration)
sd(mariokart$wheels)

qplot(data=mariokart, x=price, geom="density")
qplot(data=mariokart, y=price, geom="boxplot") # check out the outliers!
qplot(data=mariokart, x=duration, geom="density")
qplot(data=mariokart, x=wheels, geom="density")

ggplot(data=mariokart, aes(cond_new, price)) + geom_boxplot()
ggplot(data=mariokart, aes(stock_photo, price)) + geom_boxplot()
ggplot(data=mariokart, aes(duration, price)) + geom_point()
ggplot(data=mariokart, aes(wheels, price)) + geom_point()

```

I'm also going to calculate correlation coefficients for all of the variables. We can discuss what to make of this in class:

```{r}
cor(mariokart)
```

## Replicate model results

Based on the information in the textbook, I'm assuming that the model is an ordinary least squares regression.
```{r}
model <- lm(price ~ cond_new + stock_photo + duration + wheels, data=mariokart)
summary(model)
```

Huh, that doesn't quite look like what's in the textbook Figure 9.15...

I'll go ahead and calculate a confidence interval around the only parameter for which the model rejects the null hypothesis (`wheels`):
```{r}
confint(model, "wheels")
```

Without more information from the authors of the textbook it's very hard to determine exactly where or why the differences emerge. My guess at this point is that it might have something to do with those outlying `price` values (take a look at that boxplot and density plot again). Maybe they did something to transform the variable? Remove the outliers? I have no idea.

## Assess model fit/assumptions  

I've already generated a bunch of univariate and bivariate summaries and plots. Let's inspect the residuals more closely to see what else we can learn. I'll use the `autoplot()` function from the `ggfortify` package.

```{r}
autoplot(model)
```

There are those outliers again. At this point, there are a number of issues with this model fit that I'd want to mention/consider:
* The distribution of the dependent variable (`price`) is skewed, with two extreme outliers. I'd recommend trying some transformations to see if it would look more appropriate for a linear regression and/or inspecting the cases that produced the outlying values more closely to understand what's happening there and identify reasons why they're so different.
* The plots of the residuals reveal those same two outlying points are also outliers with respect to the line of best fit. That said, they are not exerting huge amounts of leverage on the estimates, so it's possible that the estimates from the fitted model wouldn't change *too much* without those two points. Indeed, based on the degrees of freedom reported in Figure 9.15 (136) vs. the number reported in our version of the model (138) my best guess at this point is that the textbook authors silently dropped those two outlying observations from their model.

More out of curiosity than anything, I'll create a version of the model that drops the two largest values of price. From the plots, I can see that those two are the only ones above \$100, so I'll use that information here:

```{r}
summary(
  lm(price ~ cond_new + stock_photo + duration + wheels, 
     data = mariokart[mariokart$price < 100,]
     )
  )
```

What do you know. That was it. The difference in $R^2$ is huge! 

## Interpret some results  

The issues above notwithstanding, we can march ahead and interpret the results of the original model that I fit. Here are some general comments and some specifically focused on the `cond_new` and `stock_photo` variables:
* Overall, the linear model regressing total auction price on condition, stock photo, duration, and number of Wii wheels shows evidence of a positive, significant relationship between number of wheels and price. According to this model fit, an increase of 1 wheel in a listing is associated with a total auction price increase of \$10 on average (95% confindence interval: \$4.57-\$15.32). 
* The point estimate for selling a new condition game is positive, but with a large standard error. The model fails to reject the null of no association and provides no evidence of any relationship between the game condition and auction price. 
* The point estimate for including a stock photo is negative, but again, the standard error is very large and the model fails to reject the null hypothesis. There is no evidence of any relationship between including a stock photo and the final auction price.

## Recommendations  

Based on this model result, I'd recommend the prospective vendor of a **used** copy of the game not worry about it too much unless they can get their hands on some extra Wii wheels, since it seems like the number of Wii wheels explains variations in the auction price outcome more than anything else they can control (such as whether or not a stock photo is included). 

# Part II: Hypothetical study 

## Import, explore, summarize  

I'll start off by just importing things and summarizing the different variables we care about here:
```{r}
grads <- readRDS(url("https://communitydata.science/~ads/teaching/2020/stats/data/week_11/grads.rds"))

summary(grads)

table(grads$cohort)
sd(grads$gpa)
sd(grads$income)

qplot(data=grads, x=gpa, geom="density")
qplot(data=grads, x=income, geom="density")

ggplot(data=grads, aes(x=gpa, y=income)) + geom_point()
```

I'll also calculate some summary statistics and visual comparisons within districts (cohorts):

```{r}

tapply(grads$income, grads$cohort, summary)
tapply(grads$income, grads$cohort, sd)

tapply(grads$gpa, grads$cohort, summary)
tapply(grads$gpa, grads$cohort, sd)
```

Note that you could also do this pretty easily with a call to `group_by` and `summarize` in the tidyverse:

```{r}
grads %>% 
  group_by(cohort) %>% 
  summarize(
    n = n(),
    min = min(income),
    mean = mean(income),
    max = max(income),
    sd = sd(income)
  ) 

grads %>% 
  group_by(cohort) %>% 
  summarize(
    n = n(),
    min = min(gpa),
    mean = mean(gpa),
    max = max(gpa),
    sd = sd(gpa)
  )
```


Huh. Those are remarkably similar values for the group means and the group standard deviations...weird.

Onwards to plotting:
```{r}
ggplot(data=grads, aes(x=cohort, y=income)) + geom_boxplot()

ggplot(data=grads, aes(x=gpa, y=income, color=cohort)) + geom_point()
```

Those plots are also a little strange. Even though this is just a simulated analysis, it still seems weird that overall the scatterplot just looks like a big mass of points, but when I color the points by district, I can see some regularities within groups. At this point, I might want to facet the scatterplots by district to see any patterns more clearly.

```{r}
ggplot(data=grads, aes(x=gpa, y=income, color=cohort)) + geom_point() + facet_wrap(vars(cohort))
```

Okay, that's...a joke (in particular, cohort 8 looks like a sideways dinosaur). At this point, if I were really working as a consultant on this project, I would write to the client and start asking some probing questions about data quality (who collected this data? how did it get recorded/stored/etc.? what quality controls were in place?). I would also feel obligated to tell them that I suspect there's just no way the data correspond to the variables they think are here. If you did that and the client was honest, they might tell you [where the data actually came from](https://www.autodesk.com/research/publications/same-stats-different-graphs).

In the event that you marched ahead with the analysis and are curious about what that could have looked like, I've provided some example code below. That said, **this is a situation where the assumptions and conditions necessary to identify ANOVA, t-tests, or regression are all pretty broken** because the data was generated programmatically in ways that undermine the kinds of interpretation you've been asked to make. The best response here (IMHO) is to abandon these kinds of analysis once you discover that there's something systematically weird going on like this. While the experience of discovering a scatterplot dinosaur in your data is...unlikely outside of the context of a problem set, there are many situations in which careful data exploration will bring a realization that you just don't understand some important things about the sources or qualities of your data. You have to learn to identify these moments and develop strategies for dealing with them! Often, the statistical procedures will "work" in the sense that they will return a result without any apparent errors, but because those results aren't even close to meaningful, any relationships you do observe in the data reflect something different than the sorts of relationships the statistical procedures were designed to identify.

## Fake analysis for fake data  

Okay, if you wanted example code to look at for this, here it is. Please just keep in mind that the results are not informative!
```{r}
summary(aov(income ~ cohort, data=grads))  # no global differences of means across groups

summary(grads.model <-  lm(income ~ gpa + cohort, data=grads)) # gpa percentile has a small, negative association with income. 

confint(grads.model, "gpa") # 95% confidence interval

```

Note that the failure to reject the null of any association between district and income in the ANOVA would not (even in the event of more realistic data) provide very compelling evidence that the relationship between GPA and income does not vary by cohort. There were several things you might have done here. One is to calculate correlation coefficients within groups. Here's some tidyverse code that does that:

```{r}
grads %>% 
  group_by(cohort) %>% 
  summarize(
    correlation = cor(income, gpa)
  )
```
Because these correlation coefficients are nearly identical, I would likely end an analysis here and conclude that the correlation between gpa and income appears to be consistently small and negative. If you wanted to go further, you could theoretically calculate an interaction term in the model (by including `I(gpa*cohort)` in the model formula), but the analysis up to this point gives no indication that you'd be likely to find much of anything (and we haven't really talked about interactions yet). On top of that, there's a literal dinosaur lurking in your data...just give up!  

# Part III: Trick or treating again  
## Import and update data

Revisit the text and worked solutions for problem set 7 for more details about the study design, data collection and more.

```{r import}
## reminder that the "read_dta()" function requires the "haven" library

df <- read_dta(url('https://communitydata.science/~ads/teaching/2020/stats/data/week_07/Halloween2012-2014-2015_PLOS.dta'))

df <- df %>%
  mutate(
    obama = as.logical(obama),
    fruit = as.logical(fruit),
    year = as.factor(year),
    male = as.logical(male),
    age = age-mean(age, na.rm=T)
  )

df
```

That looks consistent with what we want here. Let's fit and summarize the model:  
```{r}
f <- formula(fruit ~ obama + age + male + year)

fit <- glm(f, data=df, family=binomial("logit"))

summary(fit)
```

Interesting. Looks like adjusting for these other variables in a regression setting allows us to uncover some different the results. 

Onwards to generating more interpretable results.

First, odds-ratios instead of "raw" log-odds coefficients:

```{r}
## Odds ratios (exponentiated log-odds!)
exp(coef(fit))
exp(confint(fit))
```

Now, model-predicted probabilities for prototypical observations. Recall that it's necessary to create synthetic ("fake"), hypothetical individuals to generate predicted probabilities like these. In this case, I'll create two versions of each fake kid: one assigned to the treatment condition and one assigned to the control. Then I'll use the `predict()` function to generate fitted values for each of the fake kids.

```{r}
fake.kids = data.frame(
  obama = c(FALSE, FALSE, TRUE, TRUE),
  year = factor(rep(c("2015", "2012"), 2)),
  age = rep(c(9, 7), 2),
  male= rep(c(FALSE, TRUE), 2)
)

fake.kids.pred <- cbind(fake.kids, pred.prob = predict(fit, fake.kids, type="response"))

fake.kids.pred
```

Note that [this UCLA logit regression tutorial](https://stats.idre.ucla.edu/r/dae/logit-regression/) also contains example code to help extract standard errors and confidence intervals around these predicted probabilities. You were not asked to create them here, but if you'd like an example here you go. The workhorse is the `plogis()` function, which essentially does the inverse logit transformation detailed in the textbook chapter 8:

```{r}
fake.kids.more.pred <- cbind(fake.kids,
                      predict(fit, fake.kids, type= "link", se=TRUE))

within(fake.kids.more.pred, {
  pred.prob = plogis(fit);
  lower = plogis(fit - (1.96*se.fit));
  upper = plogis(fit + (1.96*se.fit))
} )
```

## Sub-group analysis

To do this, we'll need to create a slightly new model formula that drops the `year` term since we're going to restrict each subset of the data along that dimension.

Once I fit the models, I'll use the `stargazer` package to create a reasonably pretty regression table that incorporates all three summaries.  
```{r}
f2 <- formula(fruit ~ obama + age + male)

m2012 <- glm(f2, data=df[df$year == "2012",], family=binomial("logit"))
m2014 <- glm(f2, data=df[df$year == "2014",], family=binomial("logit"))
m2015 <- glm(f2, data=df[df$year == "2015",], family=binomial("logit"))

 
## I can make a pretty table out of that:
library(stargazer)  
stargazer(m2012, m2014, m2015, column.labels = c("2012", "2014", "2015"), type="text")

```

## Interpret and discuss

Well, for starters, the model providing a "pooled" estimate of treatment effects while adjusting for age, gender, and study year suggests that the point estimate is "marginally" statistically significant ($p <0.1$) indicating some evidence that the data support the alternative hypothesis (being shown a picture of Michelle Obama causes trick-or-treaters to be more likely to pick up fruit than the control condition). In more concrete terms, the trick-or-treaters shown the Obama picture were, on average, about 25\% more likely to pick up fruit than those exposed to the control (95\% CI:  $-4\%~-~+66\%$). In even more concrete terms, the estimated probability that a 9 year-old girl in 2015 and a 7 year-old boy in 2012 would take fruit increase about 17\% and 19\% respectively on average (from 29\% to 34\% in the case of the 9 year-old and from 21\% to 25\% in the case of the 7 year-old). These findings are sort of remarkable given the simplicity of the intervention and the fairly strong norm that Halloween is all about candy.

All of that said, the t-test results from Problem set 7 and the "unpooled" results reported in the sub-group analysis point to some potential concerns and limitations. For starters, the fact that the experiment was run iteratively over multiple years and that the sample size grew each year raises some concerns that the study design may not have anticipated the small effect sizes eventually observed and/or was adapted on the fly. This would undermine confidence in some of the test statistics and procedures. Furthermore, because the experiment occurred in sequential years, there's a very real possibility that the significance of a picture of Michelle Obama shifted during that time period and/or the house in question developed a reputation for being "that weird place where they show you pictures of Michelle Obama and offer you fruit." Whatever the case, my confidence in the findings here is not so great and I have some lingering suspicions that the results might not replicate.

On a more nuanced/advanced statistical note, I also have some concerns about the standard errors. This goes beyond the content of our course, but basically, a randomized controlled trial introduces clustering into the data by-design (you can think of it as analogous to the observations coming from the treatment "cluster" and the control "cluster"). In this regard, the normal standard error formulas can be biased. Luckily, there's a fix for this: compute "robust" standard errors as a result and re-calculate the corresponding confidence intervals. Indeed, robust standard errors are often considered to be the best choice even when you don't know about potential latent clustering or heteroskedastic error structures in your data. [This a short pdf](https://oes.gsa.gov/assets/files/calculating-standard-errors-guidance.pdf) provides a little more explanation, citations, as well as example R code for how you might calculate robust standard errors.