-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlab3.qmd
298 lines (217 loc) · 8.02 KB
/
lab3.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
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
---
title: Lab 03 - Functions and data.table
author: George G. Vega Yon, Ph.D.
date-modified: 2024-09-12
format:
html:
embed-resources: true
---
## Learning goals
- Used advanced features of functions in R.
- Use the `merge()` function to join two datasets.
- Deal with missings and data imputation data.
- Identify relevant observations using `quantile()`.
- Practice your GitHub skills.
## Lab description
For this lab, we will deal with the meteorological dataset downloaded
from the NOAA, the `met`. We will use `data.table` to answer some
questions regarding the `met` data set, and practice our Git+GitHub
skills.
This markdown document should be rendered using `gfm` document.
## Part 1: Setup the Git project and the GitHub repository
1. Go to your documents (or wherever you are planning to store the
data) in your computer, and create a folder for this project, for
example, “PHS7045-labs”
2. In that folder, save [this
template](https://raw.githubusercontent.com/UofUEpiBio/PHS7045-advanced-programming/main/labs/03-functions-and-datatable/03-functions-and-datatable.qmd)
as “README.qmd.” This will be the markdown file where all the magic
will happen.
3. Go to your GitHub account and create a new repository, hopefully of
the same name this folder has, i.e., “PHS7045-labs”.
4. Initialize the Git project, add the “README.qmd” file, and make your
first commit.
5. Add the repo you just created on GitHub.com to the list of remotes,
and push your commit to `origin` while setting the upstream.
Most of the steps can be done using the command line:
```bash
# Step 1
cd ~/Documents
mkdir PHS7045-labs
cd PHS7045-labs
# Step 2
wget https://raw.githubusercontent.com/UofUEpiBio/PHS7045-advanced-programming/main/03-more-functions-and-datatable/lab.qmd
mv 03-functions-and-datatable.qmd README.qmd
# Step 3
# Happens on github
# Step 4
git init
git add README.Rmd
git commit -m "First commit"
# Step 5
git remote add origin [email protected]:[username]/PHS7045
git push -u origin master
```
You can also complete the steps in R (replace with your paths/username
when needed)
```bash
# Step 1
setwd("~/Documents")
dir.create("PHS7045-labs")
setwd("PHS7045-labs")
# Step 2
download.file(
"https://raw.githubusercontent.com/UofUEpiBio/PHS7045-advanced-programming/main/03-more-functions-and-datatable/lab.qmd",
destfile = "README.qmd"
)
# Step 3: Happens on Github
# Step 4
system("git init && git add README.Rmd")
system('git commit -m "First commit"')
# Step 5
system("git remote add origin [email protected]:[username]/PHS7045-labs")
system("git push -u origin master")
```
Once you are done setting up the project, you can now start working on
the lab.
## Part 2: Advanced functions
### Question 1: **Ellipsis**
Write a function using the ellipsis argument (`...`) with the goal of
(i) retrieving the list of arguments passed to it, (ii) printing
information about them using `str()`, and (iii) printing the environment
where they belong and the address of the object in memory using
`data.table::address()`.
```{r}
#| label: answ-part2-q1
myfun <- function(...) {
args <- list(...)
str(args)
print(parent.frame())
print(lapply(args, data.table::address))
}
myfun2 <- function() myfun()
myfun2()
a <- 1
b <- 2
myfun(a, b, c(a, b))
data.table::address(a)
data.table::address(b)
```
Knit the document, commit your changes, and push them to GitHub.
### Question 2: **Lazy evaluation**
A concept we did not review was lazy evaluation. Write a function with
two arguments (`a` and `b`) that only uses one of them as an integer,
and then call the function passing the following arguments
`(1, this_stuff)`
```{r}
# ...
fun <- function(a, b) {
as.integer(a)
if (missing(b))
print("b is missing")
}
fun(1, my_stuff) # Lazy eval
fun(1) # lazy eval strikes again!
```
Knit the document, commit your changes, and push them to GitHub.
### Question 3: **Putting all together**
Write a function that fits a linear regression model and saves the
result to the global environment using the `assign()` function. The name
of the output must be passed as a symbol using lazy evaluation.
```{r}
myreg <- function(..., outputname) {
# Fit the model
fit <- lm(...)
# Save the model
assign(
deparse(substitute(outputname)),
fit, envir = .GlobalEnv
)
invisible(NULL)
}
ans1 <- myreg(mpg ~ wt, data = mtcars, outputname = mymodel)
mymodel
myreg2 <- function(..., outputname) {
# Fit the model
fit <- lm(...)
# Save the model
assign(
deparse(substitute(outputname)),
fit, envir = .GlobalEnv
)
# invisible(NULL)
}
ans2 <- myreg2(mpg ~ wt, data = mtcars, outputname = mymodel2)
ans1
ans2
```
Knit the document, commit your changes, and push them to GitHub.
## Part 3: Data.table
### Setup in R
1. Load the `data.table` (and the `dtplyr` and `dplyr` packages if you
plan to work with those).
2. Load the met data from
https://raw.githubusercontent.com/USCbiostats/data-science-data/master/02_met/met_all.gz,
and the station data. For the latter, you can use the code we used
during the lecture to pre-process the stations’ data:
```{r}
#| eval: false
# Download the data
stations <- fread("ftp://ftp.ncdc.noaa.gov/pub/data/noaa/isd-history.csv")
stations[, USAF := as.integer(USAF)]
# Dealing with NAs and 999999
stations[, USAF := fifelse(USAF == 999999, NA_integer_, USAF)]
stations[, CTRY := fifelse(CTRY == "", NA_character_, CTRY)]
stations[, STATE := fifelse(STATE == "", NA_character_, STATE)]
# Selecting the three relevant columns, and keeping unique records
stations <- unique(stations[, list(USAF, CTRY, STATE)])
# Dropping NAs
stations <- stations[!is.na(USAF)]
# Removing duplicates
stations[, n := 1:.N, by = .(USAF)]
stations <- stations[n == 1,][, n := NULL]
```
3. Merge the data as we did during the lecture.
### Question 1: Representative station for the US
What is the median station in terms of temperature, wind speed, and
atmospheric pressure? Look for the three weather stations that best
represent the continental US using the `quantile()` function. Do these
three coincide?
Knit the document, commit your changes, and Save it on GitHub. Don’t
forget to add `README.md` to the tree, the first time you render it.
### Question 2: Representative station per state
Identify what the most representative (the median) station per state is.
Instead of looking at one variable at a time, look at the euclidean
distance. If multiple stations show in the median, select the one at the
lowest latitude.
Knit the doc and save it on GitHub.
### (optional) Question 3: In the middle?
For each state, identify the closest station to the mid-point of the
state. Combining these with the stations you identified in the previous
question, use `leaflet()` to visualize all ~100 points in the same
figure, applying different colors for those identified in this question.
Knit the doc and save it on GitHub.
### (optional) Question 4: Means of means
Using the `quantile()` function, generate a summary table that shows the
number of states included, average temperature, wind speed, and
atmospheric pressure by the variable “average temperature level,” which
you’ll need to create.
Start by computing the states’ average temperature. Use that measurement
to classify them according to the following criteria:
- low: temp \< 20
- Mid: temp \>= 20 and temp \< 25
- High: temp \>= 25
Once you are done with that, you can compute the following:
- Number of entries (records),
- Number of NA entries,
- Number of stations,
- Number of states included, and
- Mean temperature, wind speed, and atmospheric pressure.
All by the levels described before.
Knit the document, commit your changes, and push them to GitHub. If
you’d like, you can take this time to include the link of [the issue of
the
week](https://github.com/UofUEpiBio/PHS7045-advanced-programming/issues/5)
so that you let us know when you are done, e.g.,
```bash
git commit -a -m "Finalizing lab 3 https://github.com/UofUEpiBio/PHS7045-advanced-programming/issues/5"
```