Due: Monday, October 21, at 23:59.
The intent of the participation assessment is to encourage following along with class activities, which are usually coding sessions. You’ll be putting all your in-class work in your own participation repository hosted on your GitHub user account, which we will evaluate at the end of the course.
In short, we’re evaluating completeness, not correctness. Specifically:
Your participation component will be evaluated by the completeness of your repository. You’ll be prompted in class when you should be contributing to your participation repository.
Your repository should be complete with all in-class exercises. Your work should resemble an honest attempt at the activities, but does not need to be anywhere near “correct” – even completely failing at an activity will earn you full marks here!
Each of the 14 classes wil receive equal weight here (5% per class).
Your repository should be well-documented.
- 10%: Does your main README orient a stranger to your repository?
- 10%: Will a stranger be able to figure out what the main files of your repository are for, and where they are located?
- 10%: Are the contents of your files human readable? Although we aren’t expecting publication-quality prose, there should be a moderate level of readability of your scripts to earn you full points here.
If you miss class, you can still do the activities another time.
Here are the instructions to set up your participation repository.
- On your user account, make a new repository:
- Click the “+” in the top-right corner -> “New repository”
- Call it
- We highly recommend making this a public repo. But if you so desire, make it private. You can change this later.
- Say YES to initializing with a README.
- Add the teaching team as collaborators:
- Click on “Settings” -> “Collaborators”.
- Add the instructors:
- Add the TA’s (see note below)
- Submit your participation repo to canvas right away, by submitting a URL to the repo.
- Don’t worry, we won’t grade it until it’s finished.
Note: If your participation repo is private, and you have a free GitHub account without the student developer pack, you will be limited to adding three collaborators. Add the instructors (
firasm), along with the TA who will be grading your participation repo. Will be listed later.
Participation Check List
Below is a checklist with all the materials needed to get full participation marks. Instructor version of the scripts run in class are provided for your reference.
Note that instructor copy is just for your reference. You cannot just copy-paste the code written by the instructors and submit it as your participation. It is the responsibility of every student to be aware and adhere to the policies on plaigiarism: Code Plagiarism.
- Class Meeting 1 Introduction to STAT 545 and GitHub
- Register a GitHub account
- Share your username by filling out this survey
- Create and populate
navigating_github.mdwith several links
- Class Meeting 2 Introduction to R
- Provide the R script
cm002_R_exploration.Rfile. Instructor version can be found here
- Provide the R script
- Class Meeting 3 Authoring
navigating_github.mddocument with some markdown features
- Convert the
.mdfile into both
htmland add them to your repo
rmd_exploration.Rmdand its output formats (
- Class Meeting 4 The version control workflow
- nothing is required for submisison
- Class Meeting 5 Intro to plotting with ggplot2, Part I
- Class Meeting 6 Intro to data wrangling, Part I
- Class Meeting 7 Intro to data wrangling, Part II
- Class Meeting 8 Intro to plotting with ggplot2, Part II
- Class Meeting 9 Tidy Data and Pivoting
- Class Meeting 10 Tibble Joins
- Class Meeting 11 File input/output (I/O)
- Complete the steps described in lesson 11.
.Rscript with your work
- Class Meeting 12 Working with factors in R
- Class Meeting 13 Effective Visualizations
- Class Meeting 14 The Model-Fitting Paradigm in R
Submitting your participation repository
If you’ve completed Step 3 in the above “Setup” section, you don’t have to do anything. We will grade your repository as it was on the last commit before the deadline.