-
Notifications
You must be signed in to change notification settings - Fork 0
/
ae-10-flight-delays.qmd
107 lines (60 loc) · 2.91 KB
/
ae-10-flight-delays.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
---
title: "AE 10: Model comparison"
author: "Add your name here"
format: pdf
editor: visual
---
## Packages
```{r}
#| label: load-pkgs-data
#| message: false
library(tidyverse)
library(tidymodels)
library(knitr)
```
## Data
For this application exercise we will work with a dataset of 25,000 randomly sampled flights that departed one of three NYC airports (JFK, LGA, EWR) in 2013.
```{r}
flight_data <- read_csv("data/flight-data.csv")
```
1. Convert `arr_delay` to factor with levels `"late"` (first level) and `"on_time"` (second level). This variable is our outcome and it indicates whether the flight's arrival was more than 30 minutes.
```{r}
```
2. Let's get started with some data prep: Convert all variables that are character strings to factors.
```{r}
```
## Modeling prep
3. Split the data into testing (75%) and training (25%), and save each subset.
```{r}
set.seed(222)
```
4. Specify a logistic regression model that uses the `"glm"` engine.
```{r}
```
Next, we'll create two recipes and workflows and compare them to each other.
## Model 1: Everything and the kitchen sink
5. Define a recipe that predicts `arr_delay` using all variables except for `flight` and `time_hour`, which, in combination, can be used to identify a flight. Also make sure this recipe handles dummy coding as well as issues that can arise due to having categorical variables with some levels apparent in the training set but not in the testing set. Call this recipe `flights_rec1`.
```{r}
```
6. Create a workflow that uses `flights_rec1` and the model you specified.
```{r}
```
7. Fit the this model to the training data using your workflow and display a tidy summary of the model fit.
```{r}
```
8. Predict `arr_delay` for the testing data using this model.
```{r}
```
9. Plot the ROC curve and find the area under the curve. Comment on how well you think this model has done for predicting arrival delay.
```{r}
```
## Model 2: Let's be a bit more thoughtful
10. Define a new recipe, `flights_rec2`, that, in addition to what was done in `flights_rec1`, adds features for day of week and month based on `date` and also adds indicators for all US holidays (also based on `date`). A list of these holidays can be found in `timeDate::listHolidays("US")`. Once these features are added, `date` should be removed from the data. Then, create a new workflow, fit the same model (logistic regression) to the training data, and do predictions on the testing data. Finally, draw another ROC curve and find the area under the curve. Compare the predictive performance of this new model to the previous one. Based on the area under the curve statistic, which model does better?
```{r}
```
## Putting it altogether
11. Create an ROC curve that plots both models, in different colors, and adds a legend indicating which model is which.
```{r}
```
## Acknowledgement
This exercise was inspired by <https://www.tidymodels.org/start/recipes/>.