Jan 25-26, 2019
9:00 am to 4:30 pm
Instructors: Jon Jablonski, Ian Lessing, Greg Janee, Sharon Solis, Mary Donovan, Katja Seltmann, Yuan Wu
Please register using EventBrite
SOLD OUT! We will open registration for a February 21-22 workshop soon. If you would like to be on a waiting list, please email collaboratory@library.ucsb.edu
Software Carpentry aims to help researchers get their work done in less time and with less pain by teaching them basic research computing skills. This hands-on workshop will cover basic concepts and tools, including program design, version control, data management, and task automation. Participants will be encouraged to help one another and to apply what they have learned to their own research problems.
For more information on what we teach and why, please see our paper "Best Practices for Scientific Computing".
Who: The course is aimed at graduate students and other researchers. You don't need to have any previous knowledge of the tools that will be presented at the workshop.
Where: UCSB, Santa Barbara, CA 93106. Get directions with OpenStreetMap or Google Maps.
When: Jan 25-26, 2019. Add to your Google Calendar.
Requirements: Participants must bring a laptop with a Mac, Linux, or Windows operating system (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.
Accessibility: We are committed to making this workshop accessible to everybody. The workshop organizers have checked that:
Materials will be provided in advance of the workshop and large-print handouts are available if needed by notifying the organizers in advance. If we can help making learning easier for you (e.g. sign-language interpreters, lactation facilities) please get in touch (using contact details below) and we will attempt to provide them.
Contact: Please email collaboratory@library.ucsb.edu for more information.
Please be sure to complete these surveys before and after the workshop.
| Before | Pre-workshop survey |
| 08:15 | Installation help. Please arrive early if you had problems installing all of the required software. |
| 08:30 | Coffee and light breakfast |
| 09:00 | Introductions |
| 09:15 | The Unix Shell |
| 09:20 | Navigating Files & Directories |
| 10:00 | Working with Files & Directories |
| 10:50 | Coffee |
| 11:05 | Finding files |
| 11:50 | Pipes and Filters |
| 12:25 | Lunch break (lunch will be provided) |
| 13:25 | Automated Version Control |
| 13:35 | Setting up Git |
| 13:45 | Creating a Repository |
| 13:55 | Tracking Changes |
| 14:15 | Coffee |
| 14:45 | Exploring History |
| 15:10 | Ignoring Things |
| 15:15 | Remotes in Github |
| 15:45 | Collaborating |
| 16:10 | Conflicts |
| 16:40 | Open Science |
| 16:30 | END |
| 08:30 | Coffee and light breakfast |
| 09:00 | Introduction to R and Rstudio |
| 10:00 | Project Management with Rstudio |
| 10:30 | Using Git from Rstudio |
| 10:35 | Coffee |
| 10:50 | Seeking Help |
| 11:00 | Data Structures |
| 11:40 | Data Frames |
| 12:10 | Lunch break (lunch will be provided) |
| 12:55 | Subsetting Data |
| 13:30 | Plotting with ggplot2 |
| 14:30 | Vectorization |
| 14:40 | Coffee |
| 14:55 | Dataframe Manipulation with dplyr |
| 15:55 | Dataframe Maninpulation with tidyr |
| 16:40 | Writing Good Software |
| 16:50 | Post-workshop Survey |
| 17:00 | END |
We will use this Etherpad collaborative document for chatting, taking notes, and sharing URLs and bits of code.
add, commit, ...status, diff, ...clone, pull, push, ...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.
For this workshop's lessons, please download the following data to your desktop:
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 macOS 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.
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.
Because this installer is not signed by the developer, you may have to
right click (control click) on the .pkg file, click Open, and click
Open on the pop up window.
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 dnf 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 macOS and Linux is usually set to Vim, which is not famous for being intuitive. If you accidentally find yourself stuck in it, hit the Esc 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. It is installed along with Git.
Others editors that you can use are Notepad++ or Sublime Text. Be aware that you must add its installation directory to your system path. Please ask your instructor to help you do this.
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.
Others editors that you can use are BBEdit or Sublime Text.
nano is a basic editor and the default that instructors use in the workshop. It should be pre-installed.
Others editors that you can use are Gedit, Kate or Sublime Text.
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. Note that if you have separate user and admin accounts, you should run the installers as administrator (right-click on .exe file and select "Run as administrator" instead of double-clicking). Otherwise problems may occur later, for example when installing R packages.
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 dnf install R). Also, please install the
RStudio IDE.