March 6-7, 2017
9:00 am - 4:30 pm
Instructors: Carl Ferkinhoff, Hannah Leverentz, Nathan Moore, Chris Phan
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.
The Software Carpentry and Data Carpentry organizations have a large number of tutorials written and available on the web via a Creative Commons Attribution License. These lessons could be classified as "Open Educational Resources", and we think this material can be relevant and useful to the undergraduate classroom. Further, the best way to get to know the lessons is to work through them, in teams, in a dedicated setting. Attendees should expect to gain proficiency with the shell, programming in python, and implementing revision control with git, all in a supportive setting. There will also be some discussion of how we can use these materials in undergraduate classrooms.
Please note, if you teach, study, or work outside of science you are still very welcome! The practices presented at the workshop are quite general, and have led to the sister organizations of Library Carpentry, https://librarycarpentry.github.io/, and The Programming Historian http://programminghistorian.org/.
For more information on what we teach and why, please see our paper "Best Practices for Scientific Computing".
Who: The course is aimed at faculty members within the Minnesota State system. Depending on registrations there may be space for staff, students, and community members. Participants do not need to have any previous knowledge of the tools that will be presented at the workshop.
Registration: To register, please fill out this google form. The workshop is funded by the Minnesota Legislature, via Minnesota State system. Per the funders' intention, faculty members have first priority in registration. Other staff, students, and community members who fill out this form will be added to a waiting list. If workshop seats are open on Feb 27 we will contact those on the waiting list.
There is no fee for the 2-day workshop, and coffee will be provided during the breaks. On-campus parking will be available. Meals, transportation, and lodging are not provided. Feel free to contact the organizers for advice on travel and accomodations.
Parking will be available in the Gold Main Lot, which is Lot #1 shown on this WSU campus map.
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.
Please be sure to complete these surveys before and after the workshop.
|08:30||Soft start, software installs, coffee, etc|
|09:00||Automating tasks with the Unix shell|
|13:00||Building programs with Python|
|08:30||Soft start, coffee, overnight questions|
|09:00||Building programs with Python|
|13:00||Version control with Git|
We will use this Etherpad for chatting, taking notes, and sharing URLs and bits of code.
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.
Python is a popular language for research computing, and great for general-purpose programming as well. Installing all of its research packages individually can be a bit difficult, so we recommend Anaconda, an all-in-one installer.
Regardless of how you choose to install it, please make sure you install Python version 3.x (e.g., 3.4 is fine).
We will teach Python using the IPython notebook, aka Jupyter notebook, a programming environment that runs in a web browser. For this to work you will need a reasonably up-to-date browser. The current versions of the Chrome, Safari and Firefox browsers are all supported (some older browsers, including Internet Explorer version 9 and below, are not).
bash Anaconda3-and then press tab. The name of the file you just downloaded should appear.
yesand press enter to approve the license. Press enter to approve the default location for the files. Type
yesand press enter to prepend Anaconda to your
PATH(this makes the Anaconda distribution the default Python).
Once you are done installing the software listed above, please go to this page, which has instructions on how to test that everything was installed correctly.