Skip to content

Latest commit

 

History

History
69 lines (51 loc) · 6.15 KB

README.md

File metadata and controls

69 lines (51 loc) · 6.15 KB
Raw

Into the Tidyverse

Introduction and setup

For details on how to install software and download the tutorials, click here.

File and folder structure

  • Files in the parent folder: Whenever you want to engage with these workshops, remember to first double-click on into-the-tidyverse.Rproj first. This opens up a new R session (so that work you're doing for this project doesn't disturb whatever work you might be doing for other R projects).

  • Tutorials: This is where you can find the HTML files containing all tutorials. Each one features a self-contained lesson on a particular topic.

  • Sandbox: This is the only folder you should be modifying. You should never, ever, ever modify anything that's in any other folder. Seriously, under most circumstances, there should be no reason for you to ever navigate into these directories or open these files. If you're wanting to save scripts, plots, whatever, you should do it in the Sandbox. Make sure to follow these three simple rules to make sure everything goes smoothly:

    1. Basically, don't touch anything in the Code and Data folders, and you'll be alright. For those of you following along in realtime (i.e., I haven't finished writing/developing all of the materials yet), this lets you avoid merge conflicts. In short, a merge conflict emerges when my version of the file looks different from your version of the same file. So if you take my code and you use it to play around by adding/deleting code, your file is now different from my file. When you try to "sync" new materials from my repository to your forked clone, this creates a merge conflict that you're forced to resolve before you're allowed to download my new materials.

    2. Any time you write new code, do it in this Sandbox folder. The point of a sandbox is that you can do anything you want, and the (potentially destructive) consequences of your actions will never leave the sandbox. This is important because I'm going to encourage you very, very, very strongly never to simply run the existing scripts in the Code folder (or equivalently, simply copy/pasting existing code). So when you're typing code from scratch and need a place to save your scripts, save them in the Sandbox.

    3. On that note, you should be typing code from scratch. This sandbox should be full of code, whether it works or not. You learn a lot from typing things from scratch, especially when you're a beginner. This is because you'll inevitably type things incorrectly when you do it from scratch, and then you'll have to self-diagnose why your code doesn't work. That is invaluable experience for learning how to code. And it will also help with your muscle memory. It takes virtually zero time for me to write a pipe (%>%) because I have typed thousands and thousands and thousands of pipes. You cannot get good at writing code quickly without building muscle memory. If you simply run existing code, or copy/paste existing code, you are hurting your own learning. There are no shortcuts to learning code. You must do it the hard way.

  • Code: I'm providing all of the R Markdown code from the videos in the Code folder. These scripts are provided primarily for folks with visual impairments, who would find it useful to have the text for accessibility reasons. By and large, I do NOT want any other group of people looking at this code. Why? Because most of your learning occurs when you make (and correct) mistakes, and you can only make mistakes if you're trying things out from scratch. You can't make mistakes if you're simply running someone else's code, or just copy/pasting code.

  • Data: We will be using a diverse range of datasets from a variety of sources. There are times when it will make sense for you to directly download the data from the source (such as timeseries data on covid19, which is updated on a daily basis), but otherwise, the datasets will be provided in the Data folder. When applicable/available, the URL to the original dataset will be documented in the relevant scripts.

  • Output: Sometimes, there'll be some kind of output I want to save to your hard drive (like a plot or table), so that you have a sense for what your output ought to look like. These will be saved in the Output folder. Anytime you have some output, you should save that to the Sandbox instead.

Session descriptions

  1. Reading data.
    • Using readr to get data into R.
    • Understanding dataframes and their close cousins, the tibble.
    • Datatypes.
  2. Manipulating data.
    • Getting familiar with functions.
    • An introduction to using dplyr to manipulate data.
  3. Tidying data.
    • Introduction to the "tidy" philosophy (after which the tidyverse is named)
    • More practice using dplyr and learning some handy tidyr functions.
  4. Plotting data I.
    • Understanding the grammar of graphics.
    • Using ggplot2 to make beautiful plots.
    • Aesthetics, mappings, and geometries
  5. Plotting data II.
    • Additional ggplot2 features.
    • Labels, facets, scales and legends, coordinates, and themes.
  6. Data types, revisited.
    • Why do stringr, forcats, and lubridate exist?
    • Revisiting readr, and introducing haven and readxl.
  7. Iteration.
    • The DIE principle: Duplication Is Evil.
    • Serial operations.
    • Vectorized operations.
    • A very cursory introduction to functional programming using purrr.
  8. The integrated tidyverse and beyond.
    • What does it mean for a non-tidyverse library to be tidy-friendly?
    • What are some challenges in using libraries that are not tidy-friendly?

Useful resources

  1. R for Data Science
    • Oriented around data science workflows, and less around statistics
    • Extremely accessible to people who know nothing about programming
    • Makes extensive use of the tidyverse, which is a collection of R packages that streamlines the process of cleaning/analyzing data
    • Written by one of the lead programmers of many tidyverse packages
  2. Advanced R
    • For people who are specifically interested in doing a deep-dive into R as a programming language
    • Not really necessary for the average user, but may be a good resource if you're getting a weird error message and want to figure out exactly what it means