Skip to content

Commit

Permalink
Render site
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Sep 26, 2024
1 parent 02774df commit 5dec561
Show file tree
Hide file tree
Showing 3 changed files with 112 additions and 410 deletions.
8 changes: 4 additions & 4 deletions help.html
Original file line number Diff line number Diff line change
Expand Up @@ -350,14 +350,14 @@ <h2><strong>Why are my changes not taking effect? It’s making my results look
<p>Here we are creating a new object from an existing one:</p>
<pre class="r"><code>new_rivers &lt;- sample(rivers, 5)
new_rivers</code></pre>
<pre><code>## [1] 1243 390 720 237 460</code></pre>
<pre><code>## [1] 383 350 250 430 1459</code></pre>
<p>Using just this will only print the result and not actually change <code>new_rivers</code>:</p>
<pre class="r"><code>new_rivers + 1</code></pre>
<pre><code>## [1] 1244 391 721 238 461</code></pre>
<pre><code>## [1] 384 351 251 431 1460</code></pre>
<p>If we want to modify <code>new_rivers</code> and save that modified version, then we need to reassign <code>new_rivers</code> like so:</p>
<pre class="r"><code>new_rivers &lt;- new_rivers + 1
new_rivers</code></pre>
<pre><code>## [1] 1244 391 721 238 461</code></pre>
<pre><code>## [1] 384 351 251 431 1460</code></pre>
<p>If we forget to reassign this can cause subsequent steps to not work as expected because we will not be working with the data that has been modified.</p>
<hr />
</div>
Expand Down Expand Up @@ -406,7 +406,7 @@ <h2><strong>Error: object ‘X’ not found</strong></h2>
<p>Make sure you run something like this, with the <code>&lt;-</code> operator:</p>
<pre class="r"><code>rivers2 &lt;- new_rivers + 1
rivers2</code></pre>
<pre><code>## [1] 1245 392 722 239 462</code></pre>
<pre><code>## [1] 385 352 252 432 1461</code></pre>
<hr />
</div>
<div id="error-unexpected-in-error-unexpected-in-error-unexpected-x-in" class="section level2">
Expand Down
76 changes: 16 additions & 60 deletions modules/RStudio/lab/RStudio_Lab.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -5,71 +5,32 @@ editor_options:
chunk_output_type: console
---

## R Markdown
# R Markdown

Please read through everything and then try the exercises.
Please read through everything and then try the exercises. This is an R Markdown document. Markdown is a simple formatting syntax for authoring HTML, PDF, and MS Word documents. For more details on using R Markdown see <http://rmarkdown.rstudio.com>. The way you can create a file like this in RStudio is: File → New File → R Markdown and then using the default or using a template.

This is an R Markdown document. Markdown is a simple formatting syntax for authoring HTML, PDF, and MS Word documents. For more details on using R Markdown see <http://rmarkdown.rstudio.com>.
### The Code

The way you can create a file like this in RStudio is: File → New File → R Markdown and then using the default or using a template.

Now we will install some packages! Note it may take ~5-10 minutes to run all these steps. **You need to run these steps in the order listed.**

### 0.1

First copy and paste the following code into the console (the lower left panel/pane):
install.packages("remotes")

This code will install a package from CRAN called "remotes". <br>
You may be asked a question in the console when you do this. If so, answer by typing Yes into the console.

### 0.2

Next copy and paste the following code again into the console (the lower left panel/pane):
library(remotes)

This code loads the remotes package into memory- in other words we can use the functions within the package.<br>
You may be asked a question in the console when you do this. If so, answer by typing Yes into the console.

### 0.3

Now install a package that the instructors made that is not on CRAN but on GitHub, by copy and pasting the code into the console:

install_github("fhdsl/dasehr")

You may be asked a question in the console when you do this. If so, answer by typing Yes into the console.

### 0.4

The gray area below is a code chunk that will set up our packages and data (this will not show up in the rendered report when we press knit). You can also run the code within the editor area by pressing the green play button. Don't worry right now about what the code is doing, we will cover this later. We just want you to get used to RStudio and RMarkdowns.
The gray area below is a code chunk that will set up our packages and data. You can also run the code within the editor area by pressing the green play button. Don't worry right now about what the code is doing, we will cover this later. We just want you to get used to RStudio and RMarkdowns. This dataset is one we'll be working with quite a lot in the lectures. It contains county-level data about ER visits for heat-related illnesses in Colorado for the years 2011-2022.

```{r setup, message=FALSE}
knitr::opts_chunk$set(echo = TRUE)
library(dasehr)
library(ggplot2)
library(dplyr)
library(tidyverse)
ER <- CO_heat_ER_bygender
er <- read_csv(file = "https://daseh.org/data/CO_ER_heat_visits.csv")
# keep non-missing data
ER_2 <- ER %>%
er_2 <- er %>%
filter(!is.na(rate))
```

When you click the **Knit** button (at the top of RStudio), a document will be generated that includes both content as well as the output of any embedded R code chunks within the document.
Next we will show you some code - no worries about understanding it yet, we just want to get you familiar with where code goes.

When code is in an RMarkdown file chunk, it is saved to a file. When it is in the console, it is not saved.
When you click the **Knit** button (at the top of RStudio), a document will be generated that includes both content as well as the output of any embedded R code chunks within the document. Next we will show you some code - no worries about understanding it yet, we just want to get you familiar with where code goes. When code is in an RMarkdown file chunk, it is saved to a file. When it is in the console, it is not saved. The console is useful for installing packages like we just did, this is because we only need to do it once, so we don't usually need to save the code.

The console is useful for installing packages like we just did, this is because we only need to do it once, so we don't usually need to save the code.
### Plotting some data

## Plotting some data

Here is code that will make a plot of some data.
You can embed an R code chunk like this: Try pressing the green play button to see what happens. Make sure you have run the previous code chunk first by pressing the green play button in that chunk.
Here is code that will make a plot of some data.You can embed an R code chunk like this: Try pressing the green play button to see what happens. Make sure you have run the previous code chunk first by pressing the green play button in that chunk.

```{r plot, out.width = "100%"}
# keep only some counties
ER_3 <- ER_2 %>%
er_3 <- er_2 %>%
filter(county %in% c("Arapahoe", "Denver", "Jefferson", "Larimer"))
palette <- c(
Expand All @@ -79,9 +40,8 @@ palette <- c(
Larimer = "purple"
)
ggplot(aes(x = year, y = rate, colour = county, group = county), data = ER_3) +
ggplot(aes(x = year, y = rate, colour = county, group = county), data = er_3) +
geom_line() +
facet_wrap(~gender) +
scale_colour_manual(values = palette)
```

Expand All @@ -90,25 +50,24 @@ ggplot(aes(x = year, y = rate, colour = county, group = county), data = ER_3) +
```


## Exercise
# Exercise

Here are a few changes that will show you how to change small things in `R` code and the output it makes. After each change, hit the **Knit** button again.



### 1.1

Go through the code for the plot above and change the colors in `palette` to something other than what they originally were. See http://www.stat.columbia.edu/~tzheng/files/Rcolor.pdf for a large list of colors. For example, you could replace blue with red.

### 1.2

Add a new R chunk below the following chunk. You can use the insert chunk button or copy paste an existing code chunk. Include a lowercase x inside the chunk as the code. Make sure you press the knit button after this to see what the new chunk looks like.

Add a new R chunk after `<!-- Your code chunk goes here -->`. You can use the insert chunk button or copy paste an existing code chunk. Include a lowercase x inside the chunk as the code. Make sure you press the knit button after this to see what the new chunk looks like.

```{r}
x <- c(1, 2, 3)
```

<!-- Your code chunk goes here -->

# Practice on Your Own!

### P.1
Expand All @@ -118,6 +77,3 @@ Update the options of the R chunk you just made (with the lowercase x in it) so
### P.2

Create another R Markdown Document from RStudio dropdowns: File → New File → R Markdown.



438 changes: 92 additions & 346 deletions modules/RStudio/lab/RStudio_Lab_Key.html

Large diffs are not rendered by default.

0 comments on commit 5dec561

Please sign in to comment.