Sep 15-16, 2016
8:00 am - 4:30 pm
Instructors: John Blischak, Emily Davenport
Helpers: Nick Knoblauch, Sahar Mozaffari, Joyce Hsiao, Daniel Rabe, Gao Wang
The following links will be useful during the workshop:
Registration is required and is limited to those affiliated with the Biological Sciences Division. Please register at 2016-09-15-chicago.eventbrite.com.
Software Carpentry's mission is to help scientists and engineers get more research done in less time and with less pain by teaching them basic lab skills for scientific computing. This hands-on workshop is aimed at intermediate programmers that know the basics of R and want to learn more. It is ideal for past attendees of our novice Software Carpentry workshops (e.g. 2013, 2014), incoming graduate students that attended the MBL bootcamp, and graduate students or postdocs that currently use R for their research.
Coffee and lunch will be provided both days.
This workshop will cover the same material as last year's workshop.
Who: The course is limited to graduate students and other researchers in the Biological Sciences Division at the University of Chicago.
Prerequisites: Attendees should be familiar with the basics of navigating a filesystem in a Unix-like shell and writing functions and loops in R. If you are new to programming, you should consider attending our Introduction to R workshop.
Where: Stuart 101, 5835 South Greenwood Avenue Chicago, IL 60637. Get directions with OpenStreetMap or Google Maps.
Requirements: Participants must bring a laptop with a Mac, Linux, or Windows operating sytem (not a tablet, Chromebook, etc.) that they have administrative privileges on. They should have a few specific software packages installed (listed below). They are also required to abide by Software Carpentry's Code of Conduct.
Funding: This workshop was made possible through the generous sponsorhip of the Office of Graduate and Postdoctoral Affairs, the Department of Human Genetics, and the Department of Biochemistry and Molecular Biology.
Faculty advisors: Allan Drummond, Matthew Stephens, Mark Abney
Administrators: Lisa Anderson, Candice Lewis
Contact: Please mail jdblischak@uchicago.edu for more information.
08:00 am - 08:30 am - Installation help |
08:30 am - 10:00 am - Review of Unix shell and R |
10:00 am - 10:30 am - Coffee break |
10:30 am - 12:00 pm - Writing reproducible reports |
12:00 pm - 01:00 pm - Lunch |
01:00 pm - 02:30 pm - Analyzing data with dplyr |
02:30 pm - 03:00 pm - Coffee break |
03:00 pm - 04:30 pm - Visualizing data with ggplot2 |
08:00 am - 08:30 am - Installation help |
08:30 am - 10:00 am - Version control with Git |
10:00 am - 10:30 am - Coffee break |
10:30 am - 12:00 pm - Version control with Git |
12:00 pm - 01:00 pm - Lunch |
01:00 pm - 02:30 pm - Debugging |
02:30 pm - 03:00 pm - Coffee break |
03:00 pm - 04:30 pm - Defensive programming |
We will start with a refresher on the Unix shell and R programming. Specifically, we will quickly review how to manage files with the Unix shell and write loops and functions in R. This will ensure that everyone is reminded of the relevant syntax needed for the rest of the workshop.
We will introduce the concept of literate programming, in which code, plots, and text are combined into one document. This makes it easier to organize a research project and share the results. Specifically, we will use knitr/rmarkdown/pandoc to convert R code into html, pdf, and Word documents.
We will teach how to subset, summarize, and clean a data set using the R package dplyr. Furthermore, we will demonstrate how to visualize multivariate data using the popular graphics package ggplot2.
We will cover how to track code development using the version control software Git. This facilitates both experimenting with new ideas and the ability to reproduce past results with a specific version of the code. Furthermore, we will teach how to share their code online and collaborate using the website GitHub.
We will cover multiple aspects of ensuring that code is working correctly. This will include how to debug functions, programming defensively by including assertion statements to check code behavior, and writing tests that can be run automatically.
To participate in a Software Carpentry workshop, you will need access to the software described below. In addition, you will need an up-to-date web browser.
We maintain a list of common issues that occur during installation as a reference for instructors that may be useful on the Configuration Problems and Solutions wiki page.
Bash is a commonly-used shell that gives you the power to do simple tasks more quickly.
cmd
and press [Enter])setx HOME "%USERPROFILE%"
SUCCESS: Specified value was saved.
exit
then pressing [Enter]This will provide you with both Git and Bash in the Git Bash program.
The default shell in all versions of Mac OS X is Bash, so no
need to install anything. You access Bash from the Terminal
(found in
/Applications/Utilities
).
See the Git installation video tutorial
for an example on how to open the Terminal.
You may want to keep
Terminal in your dock for this workshop.
The default shell is usually Bash, but if your
machine is set up differently you can run it by opening a
terminal and typing bash
. There is no need to
install anything.
Git is a version control system that lets you track who made changes to what when and has options for easily updating a shared or public version of your code on github.com. You will need a supported web browser (current versions of Chrome, Firefox or Safari, or Internet Explorer version 9 or above).
You will need an account at github.com for parts of the Git lesson. Basic GitHub accounts are free. We encourage you to create a GitHub account if you don't have one already. Please consider what personal information you'd like to reveal. For example, you may want to review these instructions for keeping your email address private provided at GitHub.
Git should be installed on your computer as part of your Bash install (described above).
For OS X 10.9 and higher, install Git for Mac
by downloading and running the most recent "mavericks" installer from
this list.
After installing Git, there will not be anything in your /Applications
folder,
as Git is a command line program.
For older versions of OS X (10.5-10.8) use the
most recent available installer labelled "snow-leopard"
available here.
If Git is not already available on your machine you can try to
install it via your distro's package manager. For Debian/Ubuntu run
sudo apt-get install git
and for Fedora run
sudo yum install git
.
When you're writing code, it's nice to have a text editor that is
optimized for writing code, with features like automatic
color-coding of key words. The default text editor on Mac OS X and
Linux is usually set to Vim, which is not famous for being
intuitive. if you accidentally find yourself stuck in it, try
typing the escape key, followed by :q!
(colon, lower-case 'q',
exclamation mark), then hitting Return to return to the shell.
nano is a basic editor and the default that instructors use in the workshop. To install it, download the Software Carpentry Windows installer and double click on the file to run it. This installer requires an active internet connection.
nano is a basic editor and the default that instructors use in the workshop. See the Git installation video tutorial for an example on how to open nano. It should be pre-installed.
nano is a basic editor and the default that instructors use in the workshop. It should be pre-installed.
R is a programming language that is especially powerful for data exploration, visualization, and statistical analysis. To interact with R, we use RStudio.
Install R by downloading and running this .exe file from CRAN. Also, please install the RStudio IDE.
Install R by downloading and running this .pkg file from CRAN. Also, please install the RStudio IDE.
You can download the binary files for your distribution
from CRAN. Or
you can use your package manager (e.g. for Debian/Ubuntu
run sudo apt-get install r-base
and for Fedora run
sudo yum install R
). Also, please install the
RStudio IDE.
Please install the following R packages using install.packages
: