Day 1 / Morning


Introductory talk

For more on efficiency, reproducibility, and correctness, see this talk Titus gave in Colorado yesterday,, as well as the paper Best Practices in Scientific Computing.

You might also be interested in this blog post and the associated paper on version control.

Using this Web site

Reload to get the latest links!


Here’s a Google Doc that we’ll paste stuff into:.

Intro technology, and Python basics

(Titus Brown)

Git quick guide:

  • to retrieve the materials for the class, do:

    git clone
    cd 2013-04-az/notebooks

    at the shell prompt. On Windows, you may need to use Git Bash to create the directory, and then cmd.exe to run ipython notebook (see below).

  • to update the materials, do:

    git pull origin master

IPython Notebook quick guide:

  • run

    ipython notebook --pylab=inline

    in the directory containing your notebook files. A Web view of the notebook should pop up.

    If you’re using Anaconda, you can type:

    c:\anaconda\scripts\ipython notebook --pylab=inline

    The trick will be running this in the correct directory, but you have a little bit of time to figure this out because we won’t start with a preexisting notebook.

  • executing code

    shift-ENTER -- to execute current "code cell" and move to next
    ctrl-ENTER -- to execute current "code cell" and stay

Python installing guide:

  • run, variously, one of

    pip install <packagename>


    ~/anaconda/bin/pip install <packagename>


    sudo pip install <packagename>
comments powered by Disqus

Edit this document!

This file can be edited directly through the Web. Anyone can update and fix errors in this document with few clicks -- no downloads needed.

  1. Go to Day 1 / Morning on GitHub.
  2. Edit files using GitHub's text editor in your web browser (see the 'Edit' tab on the top right of the file)
  3. Fill in the Commit message text box at the bottom of the page describing why you made the changes. Press the Propose file change button next to it when done.
  4. Then click Send a pull request.
  5. Your changes are now queued for review under the project's Pull requests tab on GitHub!

For an introduction to the documentation format please see the reST primer.