X-Git-Url: https://code.communitydata.science/stats_class_2020.git/blobdiff_plain/c3ab23dc32bf58365b77cc044c6f51afa22ec5de..5adecb998e3ae7930f1c09da7490bf28d2742177:/r_tutorials/w03a-R_tutorial.rmd?ds=sidebyside

diff --git a/r_tutorials/w03a-R_tutorial.rmd b/r_tutorials/w03a-R_tutorial.rmd
new file mode 100644
index 0000000..49e4406
--- /dev/null
+++ b/r_tutorials/w03a-R_tutorial.rmd
@@ -0,0 +1,123 @@
+---
+title: "Week 3 R tutorial supplement"
+subtitle: "Statistics and statistical programming  \nNorthwestern University  \nMTS 525"
+author: "Aaron Shaw and Nick Vincent"
+date: "September 29, 2020"
+output:
+  html_document:
+    toc: yes
+    number_sections: true
+    toc_depth: 3
+    toc_float:
+      collapsed: false
+      smooth_scroll: true
+    theme: readable
+  pdf_document:
+    toc: yes
+    toc_depth: '3'
+---
+
+```{r setup, include=FALSE}
+knitr::opts_chunk$set(echo = TRUE)
+```
+This supplementary tutorial goes through some additional examples and concepts that came up in our class session today (September 29, 2020). Nick and Aaron have tried to elaborate some examples that illustrate our responses. 
+
+Note that we don't provide any new examples related to the `apply()` family of functions (`lapply()`, `sapply()`, `tapply()`) as the upcoming R tutorials will develop some additional material on those. 
+
+If any of these examples are unhelpful and/or more confusing, we strongly encourage you to reach out to us for additional clarification and/or just disregard for the time being. As they say, "your mileage may vary."
+
+# Using code chunks to break down a complicated function call
+One topic that came up today related into the use of chunks and breaking up functions to create more readable code.
+
+Let's use openintro county data for this example.
+```{r}
+library(openintro)
+data(county)
+```
+
+Let's look at three columns: `pop2000`, `pop2010`, and `pop2017`.
+
+For some reason, let's imagine that a homework assignment has asked us to compute the mean population in the years 2000, 2010, and 2017, take the median of the three means, and then take the log of that median. Why not?
+
+Let's start with the mean of one column...
+
+```{r}
+mean(county$pop2000)
+```
+Whoops, okay, let's use that `na.rm` argument again.
+
+```{r}
+mean(county$pop2000, na.rm=TRUE)
+```
+Ok, now we can grab just the three columns we want. Let's select a subset using brackets and variable names.
+```{r}
+three_columns <- c('pop2000', 'pop2010', 'pop2017')
+three_columns
+```
+Here's a very concise one-line command that solves our hypothetical homework problem:
+```{r}
+log(median(sapply(county[three_columns],mean, na.rm=TRUE)))
+```
+That works fine, but it can be quite confusing to read and I can't see what's happening under the hood. One approach to making things more readable and transparent might involve chunks breaking things down and creating a variable for each link in the chain of functions.
+
+First I'll get the 3 means.
+```{r}
+three_means <- sapply(county[three_columns], mean, na.rm=TRUE)
+three_means
+```
+Then I get the median of those 3 means.
+```{r}
+the_median <- median(three_means)
+the_median
+```
+Then I take the log to get a final answer.
+```{r}
+the_answer <- log(the_median)
+the_answer
+```
+It's the same result with nice breaks and space to insert comments that explain what's going on.
+
+# Formatting prettier code
+
+Another way to make complex commands more readable is to use prettier formatting. Here's what that might look like:
+```{r}
+log(
+  median(
+    sapply(
+      county[three_columns],mean, na.rm=TRUE
+      )
+    )
+  )
+```
+Again, exactly the same output, exactly the same operations. Much easier to see how the functions are layered on top of each other. 
+
+# Automatic code "prettification"
+
+We also talked about prettifying code using some built-in functions in RStudio within the `Code` dropdown menu. Specifically, you might look at the help documentation for the `Reflow comment`, `Reindent lines`, and `Reformat code` menu items or just try them out. 
+We haven't developed examples yet that can actually benefit from these commands, but here's a chunk of code from the upcoming R tutorial that I've organized "concisely." For now, try not to worry about what the code would do, and instead focus on how it's formatted. It's very short and it works perfectly, but it's pretty hard to figure out what's going on:
+
+```{r}
+## messy chunk
+my.mean <- function(z){z<-z[!is.na(z)];sigma<-sum(z);n<-length(z);out.value<-sigma/n;return(out.value)}
+```
+When I highlight that block of code and click the `Reformat Code` command from the `Code` dropdown menu here's what it looks like:
+```{r}
+## messy chunk after reformatting
+my.mean <-
+  function(z) {
+    z <-
+      z[!is.na(z)]
+    sigma <- sum(z)
+    n <- length(z)
+    out.value <- sigma / n
+    return(out.value)
+  }
+```
+It's exactly the same code. The only difference is how the text is organized. The result is far more readable.
+
+You can also use an option in RMarkdown's code chunks to call `tidy=TRUE` *inside* the beginning of the chunk within the curly brackets. The following chunk of code looks terrible in the raw .rmd fileâit's exactly the same "messy chunk" a few lines up. By including the `tidy=TRUE` option, it looks much better when it's knitted. 
+
+```{r, tidy=TRUE}
+## messy chunk with `tidy=TRUE` chunk option:
+my.mean <- function(z){z<-z[!is.na(z)];sigma<-sum(z);n<-length(z);out.value<-sigma/n;return(out.value)}
+```
\ No newline at end of file
