UBC_adv-r

We are a group of useRs at the University of British Columbia, who meet weekly to discuss Hadley Wickham's Advanced R Programming.

We meet Thursdays at 1pm PST in Biodiversity 224.

Schedule

Reading	Week(s)
Data Structures	week 01: 2014 July 03
Subsetting	week 02: 2014 July 10
Functions	week 03: 2014 July 17
	week 04: 2014 July 24
Environments	week 05: 2014 July 31
Debugging	week 06: 2014 Aug 07
Fnl Programming	week 07: 2014 Aug 21
Functionals	week 08: 2014 Sep 4
Function Operators	week 09: 2014 Oct 7
Non-Standard Evaluation	week 10
Expressions	week 11

how to contribute to this repository

• sign up for a github account (if you don't have one) here
• Fork this repository (click Fork in the top-right corner of this page)
• You now have your own personal fork of this project on your github account
• Go to your github account. You'll find the link to your fork of the repository on the right-hand side. If you are using Rstudio, you can use this link to make a local copy of the repository on your computer directions here.
• When you are working through examples or creating demonstrations, write in .Rmd
• push your changes to your github
• submit a pull request
• you're done! you can get a copy of git for your computer here and there is a great little walkthrough here although most of the commands can be done through Rstudio rather than using the command line.

using knitr

• install the package within Rstudio by:

install.packages("knitr")

• the R markdown files are suffixed with .Rmd
• when you run knitr, you can choose to create an html, word doc, pdf, or .md file. The .md files show up nicely on Github, so we recommend creating those. To do this, specify "md_document" in your .Rmd header like this:

---
title: "Your title"
author: "You"
date: 'if you want a date'
output: md_document
---

• now your .Rmd and .md files will be uploaded to the Github repositories

keeping your fork up to date

Once you have forked this repository, your version will quickly get out of date with the original. When other people's documents are pulled to the master repository, you will not automatically get copies of these. This is not a problem, but if you want to keep your version identical to the original, take a look at this help page on syncing and this one on configuring a remote fork. It is even possible to get changes from the master repository into your fork via the GitHub web interface. Then you can pull them into your local repository. Read more in this blog post Updating a fork directly from GitHub.