# Download the data
<- fread("ftp://ftp.ncdc.noaa.gov/pub/data/noaa/isd-history.csv")
stations := as.integer(USAF)]
stations[, USAF
# Dealing with NAs and 999999
:= fifelse(USAF == 999999, NA_integer_, USAF)]
stations[, USAF := fifelse(CTRY == "", NA_character_, CTRY)]
stations[, CTRY := fifelse(STATE == "", NA_character_, STATE)]
stations[, STATE
# Selecting the three relevant columns, and keeping unique records
<- unique(stations[, list(USAF, CTRY, STATE)])
stations
# Dropping NAs
<- stations[!is.na(USAF)]
stations
# Removing duplicates
:= 1:.N, by = .(USAF)]
stations[, n <- stations[n == 1,][, n := NULL] stations
Lab 03 - Functions and data.table
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
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”
In that folder, save this template as “README.qmd.” This will be the markdown file where all the magic will happen.
Go to your GitHub account and create a new repository, hopefully of the same name this folder has, i.e., “PHS7045-labs”.
Initialize the Git project, add the “README.qmd” file, and make your first commit.
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:
# 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 git@github.com:[username]/PHS7045
git push -u origin master
You can also complete the steps in R (replace with your paths/username when needed)
# 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 git@github.com:[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()
.
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)
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.
Knit the document, commit your changes, and push them to GitHub.
Part 3: Data.table
Setup in R
Load the
data.table
(and thedtplyr
anddplyr
packages if you plan to work with those).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:
- 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 so that you let us know when you are done, e.g.,
git commit -a -m "Finalizing lab 3 https://github.com/UofUEpiBio/PHS7045-advanced-programming/issues/5"