Jan 14-15, 2019
9:00 - 17:00
Instructors: Like Fokkens, Marc Galland, Pietro Marchesi
Helpers: Zsofia Koma (M), Caspar Treijtel (M+T), Carlos Martinez (T), Tijs Bliek (M+T), Michelle Mantel (M+T), Jihed Chouaref (T), Fred White (M+T)
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: The workshop will be located on the Roeterseiland Campus (Plantage Muidergracht 12, 1018 TV Amsterdam, Roetersstraat, 1012 WX Amsterdam, The Netherlands). Find the exact locations on OpenStreetMap or Google Maps. We will use two different rooms:
Requirements: Participants must bring a laptop with a Linux, Mac 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.
Registration: Staff from the University of Amsterdam get a reduced fee to cover the catering costs. Please get your ticket using the Eventbrite widget (see above).
Organisers: This workshop is organized by the Science Park Study Group members as part of its recurring activities. Please visit our website for other events that take place in Amsterdam (usually Science Park). If there are any questions get in touch and send us an email (see contact)
Accessibility: We are committed to making this workshop accessible to everybody. The workshop organizers have checked that:
Contact: Please email m.galland@uva.nl or l.fokkens@uva.nl for more information.
Please be sure to complete these surveys before and after the workshop.
| 09:00 | Welcome and introduction |
| 09:30 | Shell: Introducing the Shell |
| 09.40 | Shell: Navigating Files and Directories |
| 10.20 | Coffee break |
| 10.30 | Shell: Working With Files and Directories |
| 11:10 | Shell: Pipes and Filters |
| 12:00 | Shell: Loops |
| 12:50 | Lunch break |
| 14:00 | Python: Analyzing Patient Data |
| 15:30 | Python: Coffee break |
| 15:45 | Python: Repeating actions with loops |
| 16:15 | Python: Storing multiple values in lists |
| 16:45 | Python Analysing data from multiple files |
| 17:05 | Python: Wrap-up of the day |
| 17:15 | Finish |
| 09:00 | Python: Making choices |
| 09:30 | Python: Creating functions |
| 10:00 | Python: Errors and exceptions |
| 10:30 | Coffee break |
| 10:45 | Python: Defensive programming |
| 11:15 | Python: Debugging |
| 11:45 | Python: Command-line programs |
| 12:15 | Lunch break |
| 13:15 | Git: intro, config, repository, changes, history |
| 14:20 | Git: gitignore, remotes, collaborating, conflicts |
| 15:35 | Coffee break |
| 16:00 | Git: Open Science, licensing, citation, hosting, RStudio |
| 16:45 | Wrap-up |
| 17:00 | Finish: drinks at the CREA café |
We will use this 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 softwares 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 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 (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.
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, 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. 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 Text Wrangler 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.
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.6 is fine).
We will teach Python using the 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. If it does not, navigate to the folder where you downloaded the file, for example with:
cd DownloadsThen, try again.
yes and
press enter to approve the license. Press enter to approve the
default location for the files. Type yes and
press enter to prepend Anaconda to your PATH
(this makes the Anaconda distribution the default Python).