July 03-05, 2017
9:30 - 5:00
Instructors: Jarek Bryk, Martin Callaghan, Ian Carr, Alastair Droop
Next Generation Biologists is a series of training courses that uses the Software Carpentry model.
We aim to help researchers in the Biological sciences 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.
We'll signpost directions to the room from the street entrance to the Worsley Building (which is on level 4) on Clarenden Way and from the level 7 entrance to the Worsley Building from the University campus.
For those arriving by train, it's approximately a 20 minute walk from the station. If taking a taxi, note that there are roadworks on Clarenden Way and the taxi may not be able to drop you at the front door.
When: July 03-05, 2017. 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 organisers 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 and we will attempt to provide them.
|09:30||Introduction & Automating tasks with the Unix shell|
|11:00||Automating tasks with the Unix shell|
|11:45||Introduction to R using gapminder data. Part 1|
|13:45||Introduction to R using gapminder data. Part 2.|
|09:30||Version control with Git and collaboration on GitHub|
|11:00||Version control with Git and collaboration on GitHub|
|11:45||Introduction to R using gapminder data. Part 3|
|13:45||Introduction to R using gapminder data. Part 4.|
You will use the tools and techniques that you have learned over the previous two days and we'll wrap up the workshop with a short presentation from each group.
Please not that this schedule is subject to change.
We may change or update content as we progress through the workshop depending on the needs of the workshop attendees.
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.
cmdand press [Enter])
setx HOME "%USERPROFILE%"
SUCCESS: Specified value was saved.
exitthen 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
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
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
After installing Git, there will not be anything in your
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"
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.
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.