matlabusers.ipynb.rtf

{\rtf1\ansi\ansicpg1252\cocoartf2707
\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fmodern\fcharset0 Courier;}
{\colortbl;\red255\green255\blue255;\red0\green0\blue0;}
{\*\expandedcolortbl;;\cssrgb\c0\c0\c0;}
\margl1440\margr1440\vieww11520\viewh8400\viewkind0
\deftab720
\pard\pardeftab720\partightenfactor0

\f0\fs26 \cf0 \expnd0\expndtw0\kerning0
\{\
 "cells": [\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# A Crash Course in Python 3 \\n",\
    "[Jian Tao](https://coehpc.engr.tamu.edu/people/jian-tao/), Texas A&M University\\n",\
    "\\n",\
    "Feb 15, 2018\\n",\
    "\\n",\
    "Converted from Python 2 notebook\\n",\
    "\\n",\
    "**A Crash Course in Python for Scientists**\\n",\
    "\\n",\
    "[Rick Muller](http://www.cs.sandia.gov/~rmuller/), Sandia National Laboratories\\n",\
    "\\n",\
    "version 0.6\\n",\
    "\\n",\
    "This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/deed.en_US)."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Why Python?\\n",\
    "Python is the programming language of choice for many scientists to a large degree because it offers a great deal of power to analyze and model scientific data with relatively little overhead in terms of learning, installation or development time. It is a language you can pick up in a weekend, and use for the rest of one's life.\\n",\
    "\\n",\
    "The [Python Tutorial](http://docs.python.org/2/tutorial/) is a great place to start getting a feel for the language. To complement this material, I taught a [Python Short Course](http://www.wag.caltech.edu/home/rpm/python_course/) years ago to a group of computational chemists during a time that I was worried the field was moving too much in the direction of using canned software rather than developing one's own methods. I wanted to focus on what working scientists needed to be more productive: parsing output of other programs, building simple models, experimenting with object oriented programming, extending the language with C, and simple GUIs. \\n",\
    "\\n",\
    "I'm trying to do something very similar here, to cut to the chase and focus on what scientists need. In the last year or so, the [IPython Project](http://ipython.org) has put together a notebook interface that I have found incredibly valuable. A large number of people have released very good IPython Notebooks that I have taken a huge amount of pleasure reading through. Some ones that I particularly like include:\\n",\
    "\\n",\
    "* Rob Johansson's [excellent notebooks](http://jrjohansson.github.io/), including [Scientific Computing with Python](https://github.com/jrjohansson/scientific-python-lectures) and [Computational Quantum Physics with QuTiP](https://github.com/jrjohansson/qutip-lectures) lectures;\\n",\
    "* [XKCD style graphs in matplotlib](http://nbviewer.ipython.org/url/jakevdp.github.com/downloads/notebooks/XKCD_plots.ipynb);\\n",\
    "* [A collection of Notebooks for using IPython effectively](https://github.com/ipython/ipython/tree/master/examples/notebooks#a-collection-of-notebooks-for-using-ipython-effectively)\\n",\
    "* [A gallery of interesting IPython Notebooks](https://github.com/ipython/ipython/wiki/A-gallery-of-interesting-IPython-Notebooks)\\n",\
    "\\n",\
    "I find IPython notebooks an easy way both to get important work done in my everyday job, as well as to communicate what I've done, how I've done it, and why it matters to my coworkers. I find myself endlessly sweeping the [IPython subreddit](http://ipython.reddit.com) hoping someone will post a new notebook. In the interest of putting more notebooks out into the wild for other people to use and enjoy, I thought I would try to recreate some of what I was trying to get across in the original Python Short Course, updated by 15 years of Python, Numpy, Scipy, Matplotlib, and IPython development, as well as my own experience in using Python almost every day of this time."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## What You Need to Install\\n",\
    "\\n",\
    "There are two branches of current releases in Python: the older-syntax Python 2, and the newer-syntax Python 3. This schizophrenia is largely intentional: when it became clear that some non-backwards-compatible changes to the language were necessary, the Python dev-team decided to go through a five-year (or so) transition, during which the new language features would be introduced and the old language was still actively maintained, to make such a transition as easy as possible. We're now (2013) past the halfway point, and, IMHO, at the first time when I'm considering making the change to Python 3.\\n",\
    "\\n",\
    "Nonetheless, I'm going to write these notes with Python 2 in mind, since this is the version of the language that I use in my day-to-day job, and am most comfortable with. If these notes are important and are valuable to people, I'll be happy to rewrite the notes using Python 3.\\n",\
    "\\n",\
    "With this in mind, these notes assume you have a Python distribution that includes:\\n",\
    "\\n",\
    "* [Python](http://www.python.org) version 2.7;\\n",\
    "* [Numpy](http://www.numpy.org), the core numerical extensions for linear algebra and multidimensional arrays;\\n",\
    "* [Scipy](http://www.scipy.org), additional libraries for scientific programming;\\n",\
    "* [Matplotlib](http://matplotlib.sf.net), excellent plotting and graphing libraries;\\n",\
    "* [IPython](http://ipython.org), with the additional libraries required for the notebook interface.\\n",\
    "\\n",\
    "A good, easy to install option that supports Mac, Windows, and Linux, and that has all of these packages (and much more) is the [Entought Python Distribution](https://www.enthought.com/products/epd), also known as EPD, which appears to be changing its name to Enthought Canopy. Enthought is a commercial company that supports a lot of very good work in scientific Python development and application. You can either purchase a license to use EPD, or there is also a [free version](https://www.enthought.com/products/epd/free/) that you can download and install.\\n",\
    "\\n",\
    "Here are some other alternatives, should you not want to use EPD:\\n",\
    "\\n",\
    "**Linux** Most distributions have an installation manager. Redhat has yum, Ubuntu has apt-get. To my knowledge, all of these packages should be available through those installers.\\n",\
    "\\n",\
    "**Mac** I use [Macports](http://www.macports.org/), which has up-to-date versions of all of these packages.\\n",\
    "\\n",\
    "**Windows** The [PythonXY](https://code.google.com/p/pythonxy/) package has everything you need: install the package, then go to Start > PythonXY > Command Prompts > IPython notebook server.\\n",\
    "\\n",\
    "**Cloud** This notebook is currently not running on the [IPython notebook viewer](http://nbviewer.ipython.org/), but will be shortly, which will allow the notebook to be viewed but not interactively. I'm keeping an eye on [Wakari](http://www.wakari.io), from [Continuum Analytics](http://continuum.io/), which is a cloud-based IPython notebook. Wakari appears to support free accounts as well. Continuum is a company started by some of the core Enthought Numpy/Scipy people focusing on big data. \\n",\
    "\\n",\
    "Continuum also supports a bundled, multiplatform Python package called [Anaconda](https://store.continuum.io/) that I'll also keep an eye on."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# I. Python Overview\\n",\
    "This is a quick introduction to Python. There are lots of other places to learn the language more thoroughly. I have collected a list of useful links, including ones to other learning resources, at the end of this notebook. If you want a little more depth, [Python Tutorial](http://docs.python.org/2/tutorial/) is a great place to start, as is Zed Shaw's [Learn Python the Hard Way](http://learnpythonthehardway.org/book/).\\n",\
    "\\n",\
    "The lessons that follow make use of the IPython notebooks. There's a good introduction to notebooks [in the IPython notebook documentation](http://ipython.org/notebook.html) that even has a [nice video](http://www.youtube.com/watch?v=H6dLGQw9yFQ#!) on how to use the notebooks. You should probably also flip through the [IPython tutorial](http://ipython.org/ipython-doc/dev/interactive/tutorial.html) in your copious free time.\\n",\
    "\\n",\
    "Briefly, notebooks have code cells (that are generally followed by result cells) and text cells. The text cells are the stuff that you're reading now. The code cells start with \\"In []:\\" with some number generally in the brackets. If you put your cursor in the code cell and hit Shift-Enter, the code will run in the Python interpreter and the result will print out in the output cell. You can then change things around and see whether you understand what's going on. If you need to know more, see the [IPython notebook documentation](http://ipython.org/notebook.html) or the [IPython tutorial](http://ipython.org/ipython-doc/dev/interactive/tutorial.html)."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Using Python as a Calculator"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Many of the things I used to use a calculator for, I now use Python for:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "2+2"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "(50-5*6)/4"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "(If you're typing this into an IPython notebook, or otherwise using notebook file, you hit shift-Enter to evaluate a cell.)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are some gotchas compared to using a normal calculator."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "7/3"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Python integer division, like C or Fortran integer division, truncates the remainder and returns an integer. At least it does in version 2. In version 3, Python returns a floating point number. You can get a sneak preview of this feature in Python 2 by importing the module from the future features:\\n",\
    "\\n",\
    "    from __future__ import division"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Alternatively, you can convert one of the integers to a floating point number, in which case the division function returns another floating point number."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "7/3."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "7/float(3)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "In the last few lines, we have sped by a lot of things that we should stop for a moment and explore a little more fully. We've seen, however briefly, two different data types: **integers**, also known as *whole numbers* to the non-programming world, and **floating point numbers**, also known (incorrectly) as *decimal numbers* to the rest of the world.\\n",\
    "\\n",\
    "We've also seen the first instance of an **import** statement. Python has a huge number of libraries included with the distribution. To keep things simple, most of these variables and functions are not accessible from a normal Python interactive session. Instead, you have to import the name. For example, there is a **math** module containing many useful functions. To access, say, the square root function, you can either first\\n",\
    "\\n",\
    "    from math import sqrt\\n",\
    "\\n",\
    "and then"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "sqrt(81)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "or you can simply import the math library itself"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import math\\n",\
    "math.sqrt(81)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can define variables using the equals (=) sign:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "width = 20\\n",\
    "length = 30\\n",\
    "area = length*width\\n",\
    "area"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If you try to access a variable that you haven't yet defined, you get an error:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "volume"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "and you need to define it:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "depth = 10\\n",\
    "volume = area*depth\\n",\
    "volume"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can name a variable *almost* anything you want. It needs to start with an alphabetical character or \\"\\\\_\\", can contain alphanumeric charcters plus underscores (\\"\\\\_\\"). Certain words, however, are reserved for the language:\\n",\
    "\\n",\
    "    and, as, assert, break, class, continue, def, del, elif, else, except, \\n",\
    "    exec, finally, for, from, global, if, import, in, is, lambda, not, or,\\n",\
    "    pass, print, raise, return, try, while, with, yield\\n",\
    "\\n",\
    "Trying to define a variable using one of these will result in a syntax error:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "return = 0"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The [Python Tutorial](http://docs.python.org/2/tutorial/introduction.html#using-python-as-a-calculator) has more on using Python as an interactive shell. The [IPython tutorial](http://ipython.org/ipython-doc/dev/interactive/tutorial.html) makes a nice complement to this, since IPython has a much more sophisticated iteractive shell."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Strings\\n",\
    "Strings are lists of printable characters, and can be defined using either single quotes"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "'Hello, World!'"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "or double quotes"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "\\"Hello, World!\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "But not both at the same time, unless you want one of the symbols to be part of the string."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "\\"He's a Rebel\\""\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "'She asked, \\"How are you today?\\"'"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Just like the other two data objects we're familiar with (ints and floats), you can assign a string to a variable"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "greeting = \\"Hello, World!\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **print** statement is often used for printing character strings:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "print(greeting)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "But it can also print data types other than strings:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "print(\\"The area is \\",area)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "In the above snipped, the number 600 (stored in the variable \\"area\\") is converted into a string before being printed out."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can use the + operator to concatenate strings together:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "statement = \\"Hello,\\" + \\"World!\\"\\n",\
    "print(statement)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Don't forget the space between the strings, if you want one there. "\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "statement = \\"Hello, \\" + \\"World!\\"\\n",\
    "print(statement)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can use + to concatenate multiple strings in a single statement:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "print(\\"This \\" + \\"is \\" + \\"a \\" + \\"longer \\" + \\"statement.\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If you have a lot of words to concatenate together, there are other, more efficient ways to do this. But this is fine for linking a few strings together."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Lists\\n",\
    "Very often in a programming language, one wants to keep a group of similar items together. Python does this using a data type called **lists**."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week = [\\"Sunday\\",\\"Monday\\",\\"Tuesday\\",\\"Wednesday\\",\\"Thursday\\",\\"Friday\\",\\"Saturday\\"]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can access members of the list using the **index** of that item:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week[2]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Python lists, like C, but unlike Fortran, use 0 as the index of the first element of a list. Thus, in this example, the 0 element is \\"Sunday\\", 1 is \\"Monday\\", and so on. If you need to access the *n*th element from the end of the list, you can use a negative index. For example, the -1 element of a list is the last element:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week[-1]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can add additional items to the list using the .append() command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "languages = [\\"Fortran\\",\\"C\\",\\"C++\\"]\\n",\
    "languages.append(\\"Python\\")\\n",\
    "print(languages)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **range()** command is a convenient way to make sequential lists of numbers:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "list(range(10))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Note that range(n) starts at 0 and gives the sequential list of integers less than n. If you want to start at a different number, use range(start,stop)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "list(range(2,8))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The lists created above with range have a *step* of 1 between elements. You can also give a fixed step size via a third command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "evens = list(range(0,20,2))\\n",\
    "evens"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "evens[3]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Lists do not have to hold the same data type. For example,"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "[\\"Today\\",7,99.3,\\"\\"]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "However, it's good (but not essential) to use lists for similar objects that are somehow logically connected. If you want to group different data types together into a composite data object, it's best to use **tuples**, which we will learn about below.\\n",\
    "\\n",\
    "You can find out how long a list is using the **len()** command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "help(len)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "len(evens)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Iteration, Indentation, and Blocks\\n",\
    "One of the most useful things you can do with lists is to *iterate* through them, i.e. to go through each element one at a time. To do this in Python, we use the **for** statement:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for day in days_of_the_week:\\n",\
    "    print(day)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This code snippet goes through each element of the list called **days_of_the_week** and assigns it to the variable **day**. It then executes everything in the indented block (in this case only one line of code, the print statement) using those variable assignments. When the program has gone through every element of the list, it exists the block.\\n",\
    "\\n",\
    "(Almost) every programming language defines blocks of code in some way. In Fortran, one uses END statements (ENDDO, ENDIF, etc.) to define code blocks. In C, C++, and Perl, one uses curly braces \{\} to define these blocks.\\n",\
    "\\n",\
    "Python uses a colon (\\":\\"), followed by indentation level to define code blocks. Everything at a higher level of indentation is taken to be in the same block. In the above example the block was only a single line, but we could have had longer blocks as well:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for day in days_of_the_week:\\n",\
    "    statement = \\"Today is \\" + day\\n",\
    "    print(statement)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **range()** command is particularly useful with the **for** statement to execute loops of a specified length:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for i in range(20):\\n",\
    "    print(\\"The square of \\",i,\\" is \\",i*i)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Slicing\\n",\
    "Lists and strings have something in common that you might not suspect: they can both be treated as sequences. You already know that you can iterate through the elements of a list. You can also iterate through the letters in a string:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for letter in \\"Sunday\\":\\n",\
    "    print(letter)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is only occasionally useful. Slightly more useful is the *slicing* operation, which you can also use on any sequence. We already know that we can use *indexing* to get the first element of a list:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week[0]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If we want the list containing the first two elements of a list, we can do this via"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week[0:2]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "or simply"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week[:2]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If we want the last items of the list, we can do this with negative slicing:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "days_of_the_week[-2:]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "which is somewhat logically consistent with negative indices accessing the last elements of the list.\\n",\
    "\\n",\
    "You can do:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "workdays = days_of_the_week[1:6]\\n",\
    "print(workdays)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Since strings are sequences, you can also do this to them:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "day = \\"Sunday\\"\\n",\
    "abbreviation = day[:3]\\n",\
    "print(abbreviation)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If we really want to get fancy, we can pass a third element into the slice, which specifies a step length (just like a third argument to the **range()** function specifies the step):"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "numbers = list(range(0,40))\\n",\
    "evens = numbers[2::2]\\n",\
    "evens"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Note that in this example I was even able to omit the second argument, so that the slice started at 2, went to the end of the list, and took every second element, to generate the list of even numbers less that 40."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Booleans and Truth Testing\\n",\
    "We have now learned a few data types. We have integers and floating point numbers, strings, and lists to contain them. We have also learned about lists, a container that can hold any data type. We have learned to print things out, and to iterate over items in lists. We will now learn about **boolean** variables that can be either True or False.\\n",\
    "\\n",\
    "We invariably need some concept of *conditions* in programming to control branching behavior, to allow a program to react differently to different situations. If it's Monday, I'll go to work, but if it's Sunday, I'll sleep in. To do this in Python, we use a combination of **boolean** variables, which evaluate to either True or False, and **if** statements, that control branching based on boolean values."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "if day == \\"Sunday\\":\\n",\
    "    print(\\"Sleep in\\")\\n",\
    "else:\\n",\
    "    print(\\"Go to work\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "(Quick quiz: why did the snippet print \\"Go to work\\" here? What is the variable \\"day\\" set to?)\\n",\
    "\\n",\
    "Let's take the snippet apart to see what happened. First, note the statement"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "day == \\"Sunday\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If we evaluate it by itself, as we just did, we see that it returns a boolean value, False. The \\"==\\" operator performs *equality testing*. If the two items are equal, it returns True, otherwise it returns False. In this case, it is comparing two variables, the string \\"Sunday\\", and whatever is stored in the variable \\"day\\", which, in this case, is the other string \\"Saturday\\". Since the two strings are not equal to each other, the truth test has the false value."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The if statement that contains the truth test is followed by a code block (a colon followed by an indented block of code). If the boolean is true, it executes the code in that block. Since it is false in the above example, we don't see that code executed.\\n",\
    "\\n",\
    "The first block of code is followed by an **else** statement, which is executed if nothing else in the above if statement is true. Since the value was false, this code is executed, which is why we see \\"Go to work\\".\\n",\
    "\\n",\
    "You can compare any data types in Python:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "1 == 2"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "50 == 2*25"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "3 < 3.14159"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "1 == 1.0"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "1 != 0"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "1 <= 2"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "1 >= 1"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We see a few other boolean operators here, all of which which should be self-explanatory. Less than, equality, non-equality, and so on.\\n",\
    "\\n",\
    "Particularly interesting is the 1 == 1.0 test, which is true, since even though the two objects are different data types (integer and floating point number), they have the same *value*. There is another boolean operator **is**, that tests whether two objects are the same object:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "1 is 1.0"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can do boolean tests on lists as well:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "[1,2,3] == [1,2,4]"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "[1,2,3] < [1,2,4]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Finally, note that you can also string multiple comparisons together, which can result in very intuitive tests:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "hours = 5\\n",\
    "0 < hours < 24"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If statements can have **elif** parts (\\"else if\\"), in addition to if/else parts. For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "if day == \\"Sunday\\":\\n",\
    "    print(\\"Sleep in\\")\\n",\
    "elif day == \\"Saturday\\":\\n",\
    "    print(\\"Do chores\\")\\n",\
    "else:\\n",\
    "    print(\\"Go to work\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Of course we can combine if statements with for loops, to make a snippet that is almost interesting:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for day in days_of_the_week:\\n",\
    "    statement = \\"Today is \\" + day\\n",\
    "    print(statement)\\n",\
    "    if day == \\"Sunday\\":\\n",\
    "        print(\\"   Sleep in\\")\\n",\
    "    elif day == \\"Saturday\\":\\n",\
    "        print(\\"   Do chores\\")\\n",\
    "    else:\\n",\
    "        print(\\"   Go to work\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is something of an advanced topic, but ordinary data types have boolean values associated with them, and, indeed, in early versions of Python there was not a separate boolean object. Essentially, anything that was a 0 value (the integer or floating point 0, an empty string \\"\\", or an empty list []) was False, and everything else was true. You can see the boolean value of any data object using the **bool()** function."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "bool(1)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "bool(0)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "bool([\\"This \\",\\" is \\",\\" a \\",\\" list\\"])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Code Example: The Fibonacci Sequence\\n",\
    "The [Fibonacci sequence](http://en.wikipedia.org/wiki/Fibonacci_number) is a sequence in math that starts with 0 and 1, and then each successive entry is the sum of the previous two. Thus, the sequence goes 0,1,1,2,3,5,8,13,21,34,55,89,...\\n",\
    "\\n",\
    "A very common exercise in programming books is to compute the Fibonacci sequence up to some number **n**. First I'll show the code, then I'll discuss what it is doing."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "n = 10\\n",\
    "sequence = [0,1]\\n",\
    "for i in range(2,n): # This is going to be a problem if we ever set n <= 2!\\n",\
    "    sequence.append(sequence[i-1]+sequence[i-2])\\n",\
    "print(sequence)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Let's go through this line by line. First, we define the variable **n**, and set it to the integer 20. **n** is the length of the sequence we're going to form, and should probably have a better variable name. We then create a variable called **sequence**, and initialize it to the list with the integers 0 and 1 in it, the first two elements of the Fibonacci sequence. We have to create these elements \\"by hand\\", since the iterative part of the sequence requires two previous elements.\\n",\
    "\\n",\
    "We then have a for loop over the list of integers from 2 (the next element of the list) to **n** (the length of the sequence). After the colon, we see a hash tag \\"#\\", and then a **comment** that if we had set **n** to some number less than 2 we would have a problem. Comments in Python start with #, and are good ways to make notes to yourself or to a user of your code explaining why you did what you did. Better than the comment here would be to test to make sure the value of **n** is valid, and to complain if it isn't; we'll try this later.\\n",\
    "\\n",\
    "In the body of the loop, we append to the list an integer equal to the sum of the two previous elements of the list.\\n",\
    "\\n",\
    "After exiting the loop (ending the indentation) we then print out the whole list. That's it!"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Functions\\n",\
    "We might want to use the Fibonacci snippet with different sequence lengths. We could cut an paste the code into another cell, changing the value of **n**, but it's easier and more useful to make a function out of the code. We do this with the **def** statement in Python:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def fibonacci(sequence_length):\\n",\
    "    \\"Return the Fibonacci sequence of length *sequence_length*\\"\\n",\
    "    sequence = [0,1]\\n",\
    "    if sequence_length < 1:\\n",\
    "        print(\\"Fibonacci sequence only defined for length 1 or greater\\")\\n",\
    "        return\\n",\
    "    if 0 < sequence_length < 3:\\n",\
    "        return sequence[:sequence_length]\\n",\
    "    for i in range(2,sequence_length): \\n",\
    "        sequence.append(sequence[i-1]+sequence[i-2])\\n",\
    "    return sequence"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can now call **fibonacci()** for different sequence_lengths:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "fibonacci(2)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "fibonacci(12)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We've introduced a several new features here. First, note that the function itself is defined as a code block (a colon followed by an indented block). This is the standard way that Python delimits things. Next, note that the first line of the function is a single string. This is called a **docstring**, and is a special kind of comment that is often available to people using the function through the python command line:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "help(fibonacci)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If you define a docstring for all of your functions, it makes it easier for other people to use them, since they can get help on the arguments and return values of the function.\\n",\
    "\\n",\
    "Next, note that rather than putting a comment in about what input values lead to errors, we have some testing of these values, followed by a warning if the value is invalid, and some conditional code to handle special cases."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Recursion and Factorials\\n",\
    "Functions can also call themselves, something that is often called *recursion*. We're going to experiment with recursion by computing the factorial function. The factorial is defined for a positive integer **n** as\\n",\
    "    \\n",\
    "$$ n! = n(n-1)(n-2)\\\\cdots 1 $$\\n",\
    "\\n",\
    "First, note that we don't need to write a function at all, since this is a function built into the standard math library. Let's use the help function to find out about it:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from math import factorial\\n",\
    "help(factorial)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is clearly what we want."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "factorial(20)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "However, if we did want to write a function ourselves, we could do recursively by noting that\\n",\
    "\\n",\
    "$$ n! = n(n-1)!$$\\n",\
    "\\n",\
    "The program then looks something like:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def fact(n):\\n",\
    "    if n <= 0:\\n",\
    "        return 1\\n",\
    "    return n*fact(n-1)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "fact(20)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Recursion can be very elegant, and can lead to very simple programs."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Two More Data Structures: Tuples and Dictionaries\\n",\
    "Before we end the Python overview, I wanted to touch on two more data structures that are very useful (and thus very common) in Python programs.\\n",\
    "\\n",\
    "A **tuple** is a sequence object like a list or a string. It's constructed by grouping a sequence of objects together with commas, either without brackets, or with parentheses:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "t = (1,2,'hi',9.0)\\n",\
    "t"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Tuples are like lists, in that you can access the elements using indices:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "t[1]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "However, tuples are *immutable*, you can't append to them or change the elements of them:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "t.append(7)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "t[1]=77"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Tuples are useful anytime you want to group different pieces of data together in an object, but don't want to create a full-fledged class (see below) for them. For example, let's say you want the Cartesian coordinates of some objects in your program. Tuples are a good way to do this:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "('Bob',0.0,21.0)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Again, it's not a necessary distinction, but one way to distinguish tuples and lists is that tuples are a collection of different things, here a name, and x and y coordinates, whereas a list is a collection of similar things, like if we wanted a list of those coordinates:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "positions = [\\n",\
    "             ('Bob',0.0,21.0),\\n",\
    "             ('Cat',2.5,13.1),\\n",\
    "             ('Dog',33.0,1.2)\\n",\
    "             ]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Tuples can be used when functions return more than one value. Say we wanted to compute the smallest x- and y-coordinates of the above list of objects. We could write:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def minmax(objects):\\n",\
    "    minx = 1e20 # These are set to really big numbers\\n",\
    "    miny = 1e20\\n",\
    "    for obj in objects:\\n",\
    "        name,x,y = obj\\n",\
    "        if x < minx: \\n",\
    "            minx = x\\n",\
    "        if y < miny:\\n",\
    "            miny = y\\n",\
    "    return minx,miny\\n",\
    "\\n",\
    "x,y = minmax(positions)\\n",\
    "print(x,y)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Here we did two things with tuples you haven't seen before. First, we unpacked an object into a set of named variables using *tuple assignment*:\\n",\
    "\\n",\
    "    >>> name,x,y = obj\\n",\
    "\\n",\
    "We also returned multiple values (minx,miny), which were then assigned to two other variables (x,y), again by tuple assignment. This makes what would have been complicated code in C++ rather simple.\\n",\
    "\\n",\
    "Tuple assignment is also a convenient way to swap variables:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "x,y = 1,2\\n",\
    "y,x = x,y\\n",\
    "x,y"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**Dictionaries** are an object called \\"mappings\\" or \\"associative arrays\\" in other languages. Whereas a list associates an integer index with a set of objects:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "mylist = [1,2,9,21]"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The index in a dictionary is called the *key*, and the corresponding dictionary entry is the *value*. A dictionary can use (almost) anything as the key. Whereas lists are formed with square brackets [], dictionaries use curly brackets \{\}:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "ages = \{\\"Rick\\": 46, \\"Bob\\": 86, \\"Fred\\": 21\}\\n",\
    "print(\\"Rick's age is \\",ages[\\"Rick\\"])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There's also a convenient way to create dictionaries without having to quote the keys."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "dict(Rick=46,Bob=86,Fred=20)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **len()** command works on both tuples and dictionaries:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "len(t)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "len(ages)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Plotting with Matplotlib\\n",\
    "We can generally understand trends in data by using a plotting program to chart it. Python has a wonderful plotting library called [Matplotlib](http://matplotlib.sf.net). The IPython notebook interface we are using for these notes has that functionality built in.\\n",\
    "\\n",\
    "As an example, we have looked at two different functions, the Fibonacci function, and the factorial function, both of which grow faster than polynomially. Which one grows the fastest? Let's plot them. First, let's generate the Fibonacci sequence of length 20:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "fibs = fibonacci(10)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Next lets generate the factorials."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "facts = []\\n",\
    "for i in range(10):\\n",\
    "    facts.append(factorial(i))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Now we use the Matplotlib function **plot** to compare the two."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import matplotlib.pyplot as plt\\n",\
    "plt.figure()\\n",\
    "plt.plot(facts,label=\\"factorial\\")\\n",\
    "plt.plot(fibs,label=\\"Fibonacci\\")\\n",\
    "plt.xlabel(\\"n\\")\\n",\
    "plt.legend()\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The factorial function grows much faster. In fact, you can't even see the Fibonacci sequence. It's not entirely surprising: a function where we multiply by n each iteration is bound to grow faster than one where we add (roughly) n each iteration.\\n",\
    "\\n",\
    "Let's plot these on a semilog plot so we can see them both a little more clearly:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.figure()\\n",\
    "plt.semilogy(facts,label=\\"factorial\\")\\n",\
    "plt.semilogy(fibs,label=\\"Fibonacci\\")\\n",\
    "plt.xlabel(\\"n\\")\\n",\
    "plt.legend()\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are many more things you can do with Matplotlib. We'll be looking at some of them in the sections to come. In the meantime, if you want an idea of the different things you can do, look at the Matplotlib [Gallery](http://matplotlib.org/gallery.html). Rob Johansson's IPython notebook [Introduction to Matplotlib](http://nbviewer.ipython.org/urls/raw.github.com/jrjohansson/scientific-python-lectures/master/Lecture-4-Matplotlib.ipynb) is also particularly good."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Conclusion of the Python Overview\\n",\
    "There is, of course, much more to the language than I've covered here. I've tried to keep this brief enough so that you can jump in and start using Python to simplify your life and work. My own experience in learning new things is that the information doesn't \\"stick\\" unless you try and use it for something in real life.\\n",\
    "\\n",\
    "You will no doubt need to learn more as you go. I've listed several other good references, including the [Python Tutorial](http://docs.python.org/2/tutorial/) and [Learn Python the Hard Way](http://learnpythonthehardway.org/book/). Additionally, now is a good time to start familiarizing yourself with the [Python Documentation](http://docs.python.org/2.7/), and, in particular, the [Python Language Reference](http://docs.python.org/2.7/reference/index.html).\\n",\
    "\\n",\
    "Tim Peters, one of the earliest and most prolific Python contributors, wrote the \\"Zen of Python\\", which can be accessed via the \\"import this\\" command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import this"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "No matter how experienced a programmer you are, these are words to meditate on."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# II. Numpy and Scipy\\n",\
    "\\n",\
    "[Numpy](http://numpy.org) contains core routines for doing fast vector, matrix, and linear algebra-type operations in Python. [Scipy](http://scipy) contains additional routines for optimization, special functions, and so on. Both contain modules written in C and Fortran so that they're as fast as possible. Together, they give Python roughly the same capability that the [Matlab](http://www.mathworks.com/products/matlab/) program offers. (In fact, if you're an experienced Matlab user, there a [guide to Numpy for Matlab users](http://www.scipy.org/NumPy_for_Matlab_Users) just for you.)\\n",\
    "\\n",\
    "## Making vectors and matrices\\n",\
    "Fundamental to both Numpy and Scipy is the ability to work with vectors and matrices. You can create vectors from lists using the **array** command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import numpy as np"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.array([1,2,3,4,5,6])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can pass in a second argument to **array** that gives the numeric type. There are a number of types [listed here](http://docs.scipy.org/doc/numpy/user/basics.types.html) that your matrix can be. Some of these are aliased to single character codes. The most common ones are 'd' (double precision floating point number), 'D' (double precision complex number), and 'i' (int32). Thus,"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.array([1,2,3,4,5,6],'d')"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.array([1,2,3,4,5,6],'D')"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.array([1,2,3,4,5,6],'i')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "To build matrices, you can either use the array command with lists of lists:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.array([[0,1],[1,0]],'d')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can also form empty (zero) matrices of arbitrary shape (including vectors, which Numpy treats as vectors with one row), using the **zeros** command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.zeros((3,3),'d')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The first argument is a tuple containing the shape of the matrix, and the second is the data type argument, which follows the same conventions as in the array command. Thus, you can make row vectors:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.zeros(3,'d')"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.zeros((1,3),'d')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "or column vectors:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.zeros((3,1),'d')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There's also an **identity** command that behaves as you'd expect:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.identity(4,'d')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "as well as a **ones** command."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Linspace, matrix functions, and plotting\\n",\
    "The **linspace** command makes a linear array of points from a starting to an ending value."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.linspace(0,1)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If you provide a third argument, it takes that as the number of points in the space. If you don't provide the argument, it gives a length 50 linear space."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.linspace(0,1,11)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**linspace** is an easy way to make coordinates for plotting. Functions in the numpy library (all of which are imported into IPython notebook) can act on an entire vector (or even a matrix) of points at once. Thus,"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "x = np.linspace(0,2*math.pi)\\n",\
    "np.sin(x)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "In conjunction with **matplotlib**, this is a nice way to plot things:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.plot(x,np.sin(x))\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Matrix operations\\n",\
    "Matrix objects act sensibly when multiplied by scalars:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "0.125*np.identity(3,'d')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "as well as when you add two matrices together. (However, the matrices have to be the same shape.)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.identity(2,'d') + np.array([[1,1],[1,2]])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Something that confuses Matlab users is that the times (*) operator give element-wise multiplication rather than matrix multiplication:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.identity(2)*np.ones((2,2))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "To get matrix multiplication, you need the **dot** command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.dot(np.identity(2),np.ones((2,2)))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**dot** can also do dot products (duh!):"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "v = np.array([3,4],'d')\\n",\
    "np.sqrt(np.dot(v,v))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "as well as matrix-vector products."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are **determinant**, **inverse**, and **transpose** functions that act as you would suppose. Transpose can be abbreviated with \\".T\\" at the end of a matrix object:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "m = np.array([[1,2],[3,4]])\\n",\
    "m.T"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There's also a **diag()** function that takes a list or a vector and puts it along the diagonal of a square matrix. "\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.diag([1,2,3,4,5])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We'll find this useful later on."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Matrix Solvers\\n",\
    "You can solve systems of linear equations using the **linalg.solve** command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "A = np.array([[1,1,1],[0,2,5],[2,5,-1]])\\n",\
    "b = np.array([6,-4,27])\\n",\
    "np.linalg.solve(A,b)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are a number of routines to compute eigenvalues and eigenvectors\\n",\
    "\\n",\
    "* **eigvals** returns the eigenvalues of a matrix\\n",\
    "* **eigvalsh** returns the eigenvalues of a Hermitian matrix\\n",\
    "* **eig** returns the eigenvalues and eigenvectors of a matrix\\n",\
    "* **eigh** returns the eigenvalues and eigenvectors of a Hermitian matrix."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "A = np.array([[13,-4],[-4,7]],'d')\\n",\
    "np.linalg.eigvalsh(A)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.linalg.eigh(A)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Example: Finite Differences\\n",\
    "Now that we have these tools in our toolbox, we can start to do some cool stuff with it. Many of the equations we want to solve in Physics involve differential equations. We want to be able to compute the derivative of functions:\\n",\
    "\\n",\
    "$$ y' = \\\\frac\{y(x+h)-y(x)\}\{h\} $$\\n",\
    "\\n",\
    "by *discretizing* the function $y(x)$ on an evenly spaced set of points $x_0, x_1, \\\\dots, x_n$, yielding $y_0, y_1, \\\\dots, y_n$. Using the discretization, we can approximate the derivative by\\n",\
    "\\n",\
    "$$ y_i' \\\\approx \\\\frac\{y_\{i+1\}-y_\{i-1\}\}\{x_\{i+1\}-x_\{i-1\}\} $$\\n",\
    "\\n",\
    "We can write a derivative function in Python via"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def nderiv(y,x):\\n",\
    "    \\"Finite difference derivative of the function f\\"\\n",\
    "    n = len(y)\\n",\
    "    d = np.zeros(n,'d') # assume double\\n",\
    "    # Use centered differences for the interior points, one-sided differences for the ends\\n",\
    "    for i in range(1,n-1):\\n",\
    "        d[i] = (y[i+1]-y[i-1])/(x[i+1]-x[i-1])\\n",\
    "    d[0] = (y[1]-y[0])/(x[1]-x[0])\\n",\
    "    d[n-1] = (y[n-1]-y[n-2])/(x[n-1]-x[n-2])\\n",\
    "    return d"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Let's see whether this works for our sin example from above:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "x = np.linspace(0,2*math.pi, 10)\\n",\
    "dsin = nderiv(np.sin(x),x)\\n",\
    "plt.plot(x,dsin,label='numerical')\\n",\
    "plt.plot(x,np.cos(x),label='analytical')\\n",\
    "plt.title(\\"Comparison of numerical and analytical derivatives of sin(x)\\")\\n",\
    "plt.legend()\\n",\
    "plt.figure()\\n",\
    "plt.plot(x,dsin-np.cos(x),label='numerical')\\n",\
    "plt.title(\\"Difference\\")\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Pretty close!"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## One-Dimensional Harmonic Oscillator using Finite Difference\\n",\
    "Now that we've convinced ourselves that finite differences aren't a terrible approximation, let's see if we can use this to solve the one-dimensional harmonic oscillator.\\n",\
    "\\n",\
    "We want to solve the time-independent Schrodinger equation\\n",\
    "\\n",\
    "$$ -\\\\frac\{\\\\hbar^2\}\{2m\}\\\\frac\{\\\\partial^2\\\\psi(x)\}\{\\\\partial x^2\} + V(x)\\\\psi(x) = E\\\\psi(x)$$\\n",\
    "\\n",\
    "for $\\\\psi(x)$ when $V(x)=\\\\frac\{1\}\{2\}m\\\\omega^2x^2$ is the harmonic oscillator potential. We're going to use the standard trick to transform the differential equation into a matrix equation by multiplying both sides by $\\\\psi^*(x)$ and integrating over $x$. This yields\\n",\
    "\\n",\
    "$$ -\\\\frac\{\\\\hbar\}\{2m\}\\\\int\\\\psi(x)\\\\frac\{\\\\partial^2\}\{\\\\partial x^2\}\\\\psi(x)dx + \\\\int\\\\psi(x)V(x)\\\\psi(x)dx = E$$\\n",\
    "\\n",\
    "We will again use the finite difference approximation. The finite difference formula for the second derivative is\\n",\
    "\\n",\
    "$$ y'' = \\\\frac\{y_\{i+1\}-2y_i+y_\{i-1\}\}\{x_\{i+1\}-x_\{i-1\}\} $$\\n",\
    "\\n",\
    "We can think of the first term in the Schrodinger equation as the overlap of the wave function $\\\\psi(x)$ with the second derivative of the wave function $\\\\frac\{\\\\partial^2\}\{\\\\partial x^2\}\\\\psi(x)$. Given the above expression for the second derivative, we can see if we take the overlap of the states $y_1,\\\\dots,y_n$ with the second derivative, we will only have three points where the overlap is nonzero, at $y_\{i-1\}$, $y_i$, and $y_\{i+1\}$. In matrix form, this leads to the tridiagonal Laplacian matrix, which has -2's along the diagonals, and 1's along the diagonals above and below the main diagonal.\\n",\
    "\\n",\
    "The second term turns leads to a diagonal matrix with $V(x_i)$ on the diagonal elements. Putting all of these pieces together, we get:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def Laplacian(x):\\n",\
    "    h = x[1]-x[0] # assume uniformly spaced points\\n",\
    "    n = len(x)\\n",\
    "    M = -2*np.identity(n,'d')\\n",\
    "    for i in range(1,n):\\n",\
    "        M[i,i-1] = M[i-1,i] = 1\\n",\
    "    return M/h**2"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "x = np.linspace(-3,3)\\n",\
    "m = 1.0\\n",\
    "ohm = 1.0\\n",\
    "T = (-0.5/m)*Laplacian(x)\\n",\
    "V = 0.5*(ohm**2)*(x**2)\\n",\
    "H =  T + np.diag(V)\\n",\
    "E,U = np.linalg.eigh(H)\\n",\
    "h = x[1]-x[0]\\n",\
    "\\n",\
    "# Plot the Harmonic potential\\n",\
    "plt.plot(x,V,color='k')\\n",\
    "\\n",\
    "for i in range(4):\\n",\
    "    # For each of the first few solutions, plot the energy level:\\n",\
    "    plt.axhline(y=E[i],color='k',ls=\\":\\")\\n",\
    "    # as well as the eigenfunction, displaced by the energy level so they don't\\n",\
    "    # all pile up on each other:\\n",\
    "    plt.plot(x,-U[:,i]/np.sqrt(h)+E[i])\\n",\
    "plt.title(\\"Eigenfunctions of the Quantum Harmonic Oscillator\\")\\n",\
    "plt.xlabel(\\"Displacement (bohr)\\")\\n",\
    "plt.ylabel(\\"Energy (hartree)\\")\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We've made a couple of hacks here to get the orbitals the way we want them. First, I inserted a -1 factor before the wave functions, to fix the phase of the lowest state. The phase (sign) of a quantum wave function doesn't hold any information, only the square of the wave function does, so this doesn't really change anything. \\n",\
    "\\n",\
    "But the eigenfunctions as we generate them aren't properly normalized. The reason is that finite difference isn't a real basis in the quantum mechanical sense. It's a basis of Dirac \'ce\'b4 functions at each point; we interpret the space betwen the points as being \\"filled\\" by the wave function, but the finite difference basis only has the solution being at the points themselves. We can fix this by dividing the eigenfunctions of our finite difference Hamiltonian by the square root of the spacing, and this gives properly normalized functions."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Special Functions\\n",\
    "The solutions to the Harmonic Oscillator are supposed to be Hermite polynomials. The Wikipedia page has the HO states given by\\n",\
    "\\n",\
    "$$\\\\psi_n(x) = \\\\frac\{1\}\{\\\\sqrt\{2^n n!\}\}\\n",\
    "\\\\left(\\\\frac\{m\\\\omega\}\{\\\\pi\\\\hbar\}\\\\right)^\{1/4\}\\n",\
    "\\\\exp\\\\left(-\\\\frac\{m\\\\omega x^2\}\{2\\\\hbar\}\\\\right)\\n",\
    "H_n\\\\left(\\\\sqrt\{\\\\frac\{m\\\\omega\}\{\\\\hbar\}\}x\\\\right)$$\\n",\
    "\\n",\
    "Let's see whether they look like those. There are some special functions in the Numpy library, and some more in Scipy. Hermite Polynomials are in Numpy:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from numpy.polynomial.hermite import Hermite\\n",\
    "def ho_evec(x,n,m,ohm):\\n",\
    "    vec = [0]*9\\n",\
    "    vec[n] = 1\\n",\
    "    Hn = Hermite(vec)\\n",\
    "    return (1/np.sqrt(2**n*factorial(n)))*pow(m*ohm/math.pi,0.25)*np.exp(-0.5*m*ohm*x**2)*Hn(x*np.sqrt(m*ohm))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Let's compare the first function to our solution."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.plot(x,ho_evec(x,0,1,1),label=\\"Analytic\\")\\n",\
    "plt.plot(x,-U[:,0]/np.sqrt(h),label=\\"Numeric\\")\\n",\
    "plt.xlabel('x (bohr)')\\n",\
    "plt.ylabel(r'$\\\\psi(x)$')\\n",\
    "plt.title(\\"Comparison of numeric and analytic solutions to the Harmonic Oscillator\\")\\n",\
    "plt.legend()\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The agreement is almost exact."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can use the **subplot** command to put multiple comparisons in different panes on a single plot:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "phase_correction = [-1,1,1,-1,-1,1]\\n",\
    "for i in range(6):\\n",\
    "    plt.subplot(2,3,i+1)\\n",\
    "    plt.plot(x,ho_evec(x,i,1,1),label=\\"Analytic\\")\\n",\
    "    plt.plot(x,phase_correction[i]*U[:,i]/np.sqrt(h),label=\\"Numeric\\")\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Other than phase errors (which I've corrected with a little hack: can you find it?), the agreement is pretty good, although it gets worse the higher in energy we get, in part because we used only 50 points.\\n",\
    "\\n",\
    "The Scipy module has many more special functions:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from scipy.special import airy,jn,eval_chebyt,eval_legendre\\n",\
    "plt.subplot(2,2,1)\\n",\
    "x = np.linspace(-1,1)\\n",\
    "Ai,Aip,Bi,Bip = airy(x)\\n",\
    "plt.plot(x,Ai)\\n",\
    "plt.plot(x,Aip)\\n",\
    "plt.plot(x,Bi)\\n",\
    "plt.plot(x,Bip)\\n",\
    "plt.title(\\"Airy functions\\")\\n",\
    "\\n",\
    "plt.subplot(2,2,2)\\n",\
    "x = np.linspace(0,10)\\n",\
    "for i in range(4):\\n",\
    "    plt.plot(x,jn(i,x))\\n",\
    "plt.title(\\"Bessel functions\\")\\n",\
    "\\n",\
    "plt.subplot(2,2,3)\\n",\
    "x = np.linspace(-1,1)\\n",\
    "for i in range(6):\\n",\
    "    plt.plot(x,eval_chebyt(i,x))\\n",\
    "plt.title(\\"Chebyshev polynomials of the first kind\\")\\n",\
    "\\n",\
    "plt.subplot(2,2,4)\\n",\
    "x = np.linspace(-1,1)\\n",\
    "for i in range(6):\\n",\
    "    plt.plot(x,eval_legendre(i,x))\\n",\
    "plt.title(\\"Legendre polynomials\\")\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "As well as Jacobi, Laguerre, Hermite polynomials, Hypergeometric functions, and many others. There's a full listing at the [Scipy Special Functions Page](http://docs.scipy.org/doc/scipy/reference/special.html)."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Least squares fitting\\n",\
    "Very often we deal with some data that we want to fit to some sort of expected behavior. Say we have the following:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "raw_data = \\"\\"\\"\\\\\\n",\
    "3.1905781584582433,0.028208609537968457\\n",\
    "4.346895074946466,0.007160804747670053\\n",\
    "5.374732334047101,0.0046962988461934805\\n",\
    "8.201284796573875,0.0004614473299618756\\n",\
    "10.899357601713055,0.00005038370219939726\\n",\
    "16.295503211991434,4.377451812785309e-7\\n",\
    "21.82012847965739,3.0799922117601088e-9\\n",\
    "32.48394004282656,1.524776208284536e-13\\n",\
    "43.53319057815846,5.5012073588707224e-18\\"\\"\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There's a section below on parsing CSV data. We'll steal the parser from that. For an explanation, skip ahead to that section. Otherwise, just assume that this is a way to parse that text into a numpy array that we can plot and do other analyses with."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "data = []\\n",\
    "for line in raw_data.splitlines():\\n",\
    "    words = line.split(',')\\n",\
    "    data.append(list(map(float,words)))\\n",\
    "data = np.array(data)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.title(\\"Raw Data\\")\\n",\
    "plt.xlabel(\\"Distance\\")\\n",\
    "plt.plot(data[:,0],data[:,1],'bo')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Since we expect the data to have an exponential decay, we can plot it using a semi-log plot."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.title(\\"Raw Data\\")\\n",\
    "plt.xlabel(\\"Distance\\")\\n",\
    "plt.semilogy(data[:,0],data[:,1],'bo')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "For a pure exponential decay like this, we can fit the log of the data to a straight line. The above plot suggests this is a good approximation. Given a function\\n",\
    "$$ y = Ae^\{-ax\} $$\\n",\
    "$$ \\\\log(y) = \\\\log(A) - ax$$\\n",\
    "Thus, if we fit the log of the data versus x, we should get a straight line with slope $a$, and an intercept that gives the constant $A$.\\n",\
    "\\n",\
    "There's a numpy function called **polyfit** that will fit data to a polynomial form. We'll use this to fit to a straight line (a polynomial of order 1)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "params = np.polyfit(data[:,0],np.log(data[:,1]),1)\\n",\
    "a = params[0]\\n",\
    "A = np.exp(params[1])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Let's see whether this curve fits the data."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "x = np.linspace(1,45)\\n",\
    "plt.title(\\"Raw Data\\")\\n",\
    "plt.xlabel(\\"Distance\\")\\n",\
    "plt.semilogy(data[:,0],data[:,1],'bo')\\n",\
    "plt.semilogy(x,A*np.exp(a*x),'b-')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If we have more complicated functions, we may not be able to get away with fitting to a simple polynomial. Consider the following data:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "gauss_data = \\"\\"\\"\\\\\\n",\
    "-0.9902286902286903,1.4065274110372852e-19\\n",\
    "-0.7566104566104566,2.2504438576596563e-18\\n",\
    "-0.5117810117810118,1.9459459459459454\\n",\
    "-0.31887271887271884,10.621621621621626\\n",\
    "-0.250997150997151,15.891891891891893\\n",\
    "-0.1463309463309464,23.756756756756754\\n",\
    "-0.07267267267267263,28.135135135135133\\n",\
    "-0.04426734426734419,29.02702702702703\\n",\
    "-0.0015939015939017698,29.675675675675677\\n",\
    "0.04689304689304685,29.10810810810811\\n",\
    "0.0840994840994842,27.324324324324326\\n",\
    "0.1700546700546699,22.216216216216214\\n",\
    "0.370878570878571,7.540540540540545\\n",\
    "0.5338338338338338,1.621621621621618\\n",\
    "0.722014322014322,0.08108108108108068\\n",\
    "0.9926849926849926,-0.08108108108108646\\"\\"\\"\\n",\
    "\\n",\
    "data = []\\n",\
    "for line in gauss_data.splitlines():\\n",\
    "    words = line.split(',')\\n",\
    "    data.append(list(map(float,words)))\\n",\
    "data = np.array(data)\\n",\
    "\\n",\
    "plt.plot(data[:,0],data[:,1],'bo')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This data looks more Gaussian than exponential. If we wanted to, we could use **polyfit** for this as well, but let's use the **curve_fit** function from Scipy, which can fit to arbitrary functions. You can learn more using help(curve_fit).\\n",\
    "\\n",\
    "First define a general Gaussian function to fit to."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def gauss(x,A,a): return A*np.exp(a*x**2)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Now fit to it using **curve_fit**:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from scipy.optimize import curve_fit\\n",\
    "\\n",\
    "params,conv = curve_fit(gauss,data[:,0],data[:,1])\\n",\
    "x = np.linspace(-1,1)\\n",\
    "plt.plot(data[:,0],data[:,1],'bo')\\n",\
    "A,a = params\\n",\
    "plt.plot(x,gauss(x,A,a),'b-')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **curve_fit** routine we just used is built on top of a very good general **minimization** capability in Scipy. You can learn more [at the scipy documentation pages](http://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.minimize.html)."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Monte Carlo, random numbers, and computing $\\\\pi$\\n",\
    "Many methods in scientific computing rely on Monte Carlo integration, where a sequence of (pseudo) random numbers are used to approximate the integral of a function. Python has good random number generators in the standard library. The **random()** function gives pseudorandom numbers uniformly distributed between 0 and 1:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from random import random\\n",\
    "rands = []\\n",\
    "for i in range(100):\\n",\
    "    rands.append(random())\\n",\
    "plt.plot(rands)\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**random()** uses the [Mersenne Twister](http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html) algorithm, which is a highly regarded pseudorandom number generator. There are also functions to generate random integers, to randomly shuffle a list, and functions to pick random numbers from a particular distribution, like the normal distribution:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from random import gauss\\n",\
    "grands = []\\n",\
    "for i in range(100):\\n",\
    "    grands.append(gauss(0,1))\\n",\
    "plt.plot(grands)\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "It is generally more efficient to generate a list of random numbers all at once, particularly if you're drawing from a non-uniform distribution. Numpy has functions to generate vectors and matrices of particular types of random distributions."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.plot(np.random.rand(100))\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "One of the first programs I ever wrote was a program to compute $\\\\pi$ by taking random numbers as x and y coordinates, and counting how many of them were in the unit circle. For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "npts = 5000\\n",\
    "xs = 2*np.random.rand(npts)-1\\n",\
    "ys = 2*np.random.rand(npts)-1\\n",\
    "r = xs**2+ys**2\\n",\
    "ninside = (r<1).sum()\\n",\
    " # make the figure square\\n",\
    "plt.title(\\"Approximation to pi = %f\\" % (4*ninside/float(npts)))\\n",\
    "plt.plot(xs[r<1],ys[r<1],'b.')\\n",\
    "plt.plot(xs[r>1],ys[r>1],'r.')\\n",\
    "plt.axis('scaled')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The idea behind the program is that the ratio of the area of the unit circle to the square that inscribes it is $\\\\pi/4$, so by counting the fraction of the random points in the square that are inside the circle, we get increasingly good estimates to $\\\\pi$. \\n",\
    "\\n",\
    "The above code uses some higher level Numpy tricks to compute the radius of each point in a single line, to count how many radii are below one in a single line, and to filter the x,y points based on their radii. To be honest, I rarely write code like this: I find some of these Numpy tricks a little too cute to remember them, and I'm more likely to use a list comprehension (see below) to filter the points I want, since I can remember that.\\n",\
    "\\n",\
    "As methods of computing $\\\\pi$ go, this is among the worst. A much better method is to use Leibniz's expansion of arctan(1):\\n",\
    "\\n",\
    "$$\\\\frac\{\\\\pi\}\{4\} = \\\\sum_k \\\\frac\{(-1)^k\}\{2*k+1\}$$"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "n = 100\\n",\
    "total = 0\\n",\
    "for k in range(n):\\n",\
    "    total += pow(-1,k)/(2*k+1.0)\\n",\
    "print(4*total)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If you're interested a great method, check out [Ramanujan's method](http://en.wikipedia.org/wiki/Approximations_of_%CF%80). This converges so fast you really need arbitrary precision math to display enough decimal places. You can do this with the Python **decimal** module, if you're interested."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Numerical Integration\\n",\
    "Integration can be hard, and sometimes it's easier to work out a definite integral using an approximation. For example, suppose we wanted to figure out the integral:\\n",\
    "\\n",\
    "$$\\\\int_0^\\\\infty\\\\exp(-x)dx=1$$"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def f(x): return np.exp(-x)\\n",\
    "x = np.linspace(0,10)\\n",\
    "plt.plot(x,np.exp(-x))\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Scipy has a numerical integration routine **quad** (since sometimes numerical integration is called *quadrature*), that we can use for this:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from scipy.integrate import quad\\n",\
    "quad(f,0,np.inf)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are also 2d and 3d numerical integrators in Scipy. [See the docs](http://docs.scipy.org/doc/scipy/reference/integrate.html) for more information."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Fast Fourier Transform and Signal Processing\\n"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Very often we want to use FFT techniques to help obtain the signal from noisy data. Scipy has several different options for this."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from scipy.fftpack import fft,fftfreq\\n",\
    "\\n",\
    "npts = 4000\\n",\
    "nplot = npts//10 #floor division in python 3. \\n",\
    "t = np.linspace(0,120,npts)\\n",\
    "def acc(t): return 10*np.sin(2*math.pi*2.0*t) + 5*np.sin(2*math.pi*8.0*t) + 2*np.random.rand(npts)\\n",\
    "\\n",\
    "signal = acc(t)\\n",\
    "FFT = np.abs(fft(signal))\\n",\
    "freqs = fftfreq(npts, t[1]-t[0])\\n",\
    "plt.subplot(211)\\n",\
    "plt.plot(t[:nplot], signal[:nplot])\\n",\
    "\\n",\
    "plt.subplot(212)\\n",\
    "plt.plot(freqs,20*np.log10(FFT),',')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are additional signal processing routines in Scipy that you can [read about here](http://docs.scipy.org/doc/scipy/reference/tutorial/signal.html)."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# III. Intermediate Python\\n",\
    "\\n",\
    "## Output Parsing\\n",\
    "As more and more of our day-to-day work is being done on and through computers, we increasingly have output that one program writes, often in a text file, that we need to analyze in one way or another, and potentially feed that output into another file.\\n",\
    "\\n",\
    "Suppose we have the following output:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "myoutput = \\"\\"\\"\\\\\\n",\
    "@ Step       Energy      Delta E   Gmax     Grms     Xrms     Xmax   Walltime\\n",\
    "@ ---- ---------------- -------- -------- -------- -------- -------- --------\\n",\
    "@    0   -6095.12544083  0.0D+00  0.03686  0.00936  0.00000  0.00000   1391.5\\n",\
    "@    1   -6095.25762870 -1.3D-01  0.00732  0.00168  0.32456  0.84140  10468.0\\n",\
    "@    2   -6095.26325979 -5.6D-03  0.00233  0.00056  0.06294  0.14009  11963.5\\n",\
    "@    3   -6095.26428124 -1.0D-03  0.00109  0.00024  0.03245  0.10269  13331.9\\n",\
    "@    4   -6095.26463203 -3.5D-04  0.00057  0.00013  0.02737  0.09112  14710.8\\n",\
    "@    5   -6095.26477615 -1.4D-04  0.00043  0.00009  0.02259  0.08615  20211.1\\n",\
    "@    6   -6095.26482624 -5.0D-05  0.00015  0.00002  0.00831  0.03147  21726.1\\n",\
    "@    7   -6095.26483584 -9.6D-06  0.00021  0.00004  0.01473  0.05265  24890.5\\n",\
    "@    8   -6095.26484405 -8.2D-06  0.00005  0.00001  0.00555  0.01929  26448.7\\n",\
    "@    9   -6095.26484599 -1.9D-06  0.00003  0.00001  0.00164  0.00564  27258.1\\n",\
    "@   10   -6095.26484676 -7.7D-07  0.00003  0.00001  0.00161  0.00553  28155.3\\n",\
    "@   11   -6095.26484693 -1.8D-07  0.00002  0.00000  0.00054  0.00151  28981.7\\n",\
    "@   11   -6095.26484693 -1.8D-07  0.00002  0.00000  0.00054  0.00151  28981.7\\"\\"\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This output actually came from a geometry optimization of a Silicon cluster using the [NWChem](http://www.nwchem-sw.org/index.php/Main_Page) quantum chemistry suite. At every step the program computes the energy of the molecular geometry, and then changes the geometry to minimize the computed forces, until the energy converges. I obtained this output via the unix command\\n",\
    "\\n",\
    "    % grep @ nwchem.out\\n",\
    "\\n",\
    "since NWChem is nice enough to precede the lines that you need to monitor job progress with the '@' symbol.\\n",\
    "\\n",\
    "We could do the entire analysis in Python; I'll show how to do this later on, but first let's focus on turning this code into a usable Python object that we can plot.\\n",\
    "\\n",\
    "First, note that the data is entered into a multi-line string. When Python sees three quote marks \\"\\"\\" or ''' it treats everything following as part of a single string, including newlines, tabs, and anything else, until it sees the same three quote marks (\\"\\"\\" has to be followed by another \\"\\"\\", and ''' has to be followed by another ''') again. This is a convenient way to quickly dump data into Python, and it also reinforces the important idea that you don't have to open a file and deal with it one line at a time. You can read everything in, and deal with it as one big chunk.\\n",\
    "\\n",\
    "The first thing we'll do, though, is to split the big string into a list of strings, since each line corresponds to a separate piece of data. We will use the **splitlines()** function on the big myout string to break it into a new element every time it sees a newline (\\\\n) character:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "lines = myoutput.splitlines()\\n",\
    "lines"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Splitting is a big concept in text processing. We used **splitlines()** here, and we will use the more general **split()** function below to split each line into whitespace-delimited words.\\n",\
    "\\n",\
    "We now want to do three things:\\n",\
    "\\n",\
    "* Skip over the lines that don't carry any information\\n",\
    "* Break apart each line that does carry information and grab the pieces we want\\n",\
    "* Turn the resulting data into something that we can plot.\\n",\
    "\\n",\
    "For this data, we really only want the Energy column, the Gmax column (which contains the maximum gradient at each step), and perhaps the Walltime column. \\n",\
    "\\n",\
    "Since the data is now in a list of lines, we can iterate over it:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for line in lines[2:]:\\n",\
    "    # do something with each line\\n",\
    "    words = line.split()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Let's examine what we just did: first, we used a **for** loop to iterate over each line. However, we skipped the first two (the lines[2:] only takes the lines starting from index 2), since lines[0] contained the title information, and lines[1] contained underscores.\\n",\
    "\\n",\
    "We then split each line into chunks (which we're calling \\"words\\", even though in most cases they're numbers) using the string **split()** command. Here's what split does:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import string"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Here we're implicitly passing in the first argument (s, in the doctext) by calling a method .split() on a string object. In this instance, we're not passing in a sep character, which means that the function splits on whitespace. Let's see what that does to one of our lines:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "lines[2].split()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is almost exactly what we want. We just have to now pick the fields we want:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "for line in lines[2:]:\\n",\
    "    # do something with each line\\n",\
    "    words = line.split()\\n",\
    "    energy = words[2]\\n",\
    "    gmax = words[4]\\n",\
    "    time = words[8]\\n",\
    "    print(energy,gmax,time)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is fine for printing things out, but if we want to do something with the data, either make a calculation with it or pass it into a plotting, we need to convert the strings into regular floating point numbers. We can use the **float()** command for this. We also need to save it in some form. I'll do this as follows:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "data = []\\n",\
    "for line in lines[2:]:\\n",\
    "    # do something with each line\\n",\
    "    words = line.split()\\n",\
    "    energy = float(words[2])\\n",\
    "    gmax = float(words[4])\\n",\
    "    time = float(words[8])\\n",\
    "    data.append((energy,gmax,time))\\n",\
    "data = np.array(data)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We now have our data in a numpy array, so we can choose columns to print:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.plot(data[:,0])\\n",\
    "plt.xlabel('step')\\n",\
    "plt.ylabel('Energy (hartrees)')\\n",\
    "plt.title('Convergence of NWChem geometry optimization for Si cluster')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "I would write the code a little more succinctly if I were doing this for myself, but this is essentially a snippet I use repeatedly. \\n",\
    "\\n",\
    "Suppose our data was in CSV (comma separated values) format, a format that originally came from Microsoft Excel, and is increasingly used as a data interchange format in big data applications. How would we parse that?"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "csv = \\"\\"\\"\\\\\\n",\
    "-6095.12544083, 0.03686, 1391.5\\n",\
    "-6095.25762870, 0.00732, 10468.0\\n",\
    "-6095.26325979, 0.00233, 11963.5\\n",\
    "-6095.26428124, 0.00109, 13331.9\\n",\
    "-6095.26463203, 0.00057, 14710.8\\n",\
    "-6095.26477615, 0.00043, 20211.1\\n",\
    "-6095.26482624, 0.00015, 21726.1\\n",\
    "-6095.26483584, 0.00021, 24890.5\\n",\
    "-6095.26484405, 0.00005, 26448.7\\n",\
    "-6095.26484599, 0.00003, 27258.1\\n",\
    "-6095.26484676, 0.00003, 28155.3\\n",\
    "-6095.26484693, 0.00002, 28981.7\\n",\
    "-6095.26484693, 0.00002, 28981.7\\"\\"\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can do much the same as before:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "data = []\\n",\
    "for line in csv.splitlines():\\n",\
    "    words = line.split(',')\\n",\
    "    data.append(list(map(float,words)))\\n",\
    "data = np.array(data)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There are two significant changes over what we did earlier. First, I'm passing the comma character ',' into the split function, so that it breaks to a new word every time it sees a comma. Next, to simplify things a big, I'm using the **map()** command to repeatedly apply a single function (**float()**) to a list, and to return the output as a list."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "help(map)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Despite the differences, the resulting plot should be the same:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "plt.plot(data[:,0])\\n",\
    "plt.xlabel('step')\\n",\
    "plt.ylabel('Energy (hartrees)')\\n",\
    "plt.title('Convergence of NWChem geometry optimization for Si cluster')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Hartrees (what most quantum chemistry programs use by default) are really stupid units. We really want this in kcal/mol or eV or something we use. So let's quickly replot this in terms of eV above the minimum energy, which will give us a much more useful plot:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "energies = data[:,0]\\n",\
    "minE = min(energies)\\n",\
    "energies_eV = 27.211*(energies-minE)\\n",\
    "plt.plot(energies_eV)\\n",\
    "plt.xlabel('step')\\n",\
    "plt.ylabel('Energy (eV)')\\n",\
    "plt.title('Convergence of NWChem geometry optimization for Si cluster')\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This gives us the output in a form that we can think about: 4 eV is a fairly substantial energy change (chemical bonds are roughly this magnitude of energy), and most of the energy decrease was obtained in the first geometry iteration."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We mentioned earlier that we don't have to rely on **grep** to pull out the relevant lines for us. The **string** module has a lot of useful functions we can use for this. Among them is the **startswith** function. For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "lines = \\"\\"\\"\\\\\\n",\
    "                 ----------------------------------------\\n",\
    "                 |  WALL  |       0.45   |     443.61   |\\n",\
    "                 ----------------------------------------\\n",\
    "\\n",\
    "@ Step       Energy      Delta E   Gmax     Grms     Xrms     Xmax   Walltime\\n",\
    "@ ---- ---------------- -------- -------- -------- -------- -------- --------\\n",\
    "@    0   -6095.12544083  0.0D+00  0.03686  0.00936  0.00000  0.00000   1391.5\\n",\
    "                                                       ok       ok\\n",\
    "\\n",\
    "\\n",\
    "\\n",\
    "                                Z-matrix (autoz)\\n",\
    "                                --------\\n",\
    "\\"\\"\\".splitlines()\\n",\
    "\\n",\
    "for line in lines:\\n",\
    "    if line.startswith('@'):\\n",\
    "        print(line)\\n",\
    "        "\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "and we've successfully grabbed all of the lines that begin with the @ symbol."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The real value in a language like Python is that it makes it easy to take additional steps to analyze data in this fashion, which means you are thinking more about your data, and are more likely to see important patterns."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## More Sophisticated String Formatting and Processing\\n",\
    "Strings are a big deal in most modern languages, and hopefully the previous sections helped underscore how versatile Python's string processing techniques are. We will continue this topic in this chapter.\\n",\
    "\\n",\
    "We can print out lines in Python using the print command. "\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "print(\\"I have 3 errands to run\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "In IPython we don't even need the print command, since it will display the last expression not assigned to a variable."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "\\"I have 3 errands to run\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**print** even converts some arguments to strings for us:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "a,b,c = 1,2,3\\n",\
    "print(\\"The variables are \\",1,2,3)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "As versatile as this is, you typically need more freedom over the data you print out. For example, what if we want to print a bunch of data to exactly 4 decimal places? We can do this using formatted strings.\\n",\
    "\\n",\
    "Formatted strings share a syntax with the C **printf** statement. We make a string that has some funny *format characters* in it, and then pass a bunch of variables into the string that fill out those characters in different ways.\\n",\
    "\\n",\
    "For example,"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "print(\\"Pi as a decimal = %d\\" % math.pi)\\n",\
    "print(\\"Pi as a float = %f\\" % math.pi)\\n",\
    "print(\\"Pi with 4 decimal places = %.4f\\" % math.pi)\\n",\
    "print(\\"Pi with overall fixed length of 10 spaces, with 6 decimal places = %10.6f\\" % math.pi)\\n",\
    "print(\\"Pi as in exponential format = %e\\" % math.pi)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We use a percent sign in two different ways here. First, the format character itself starts with a percent sign. %d or %i are for integers, %f is for floats, %e is for numbers in exponential formats. All of the numbers can take number immediately after the percent that specifies the total spaces used to print the number. Formats with a decimal can take an additional number after a dot . to specify the number of decimal places to print.\\n",\
    "\\n",\
    "The other use of the percent sign is after the string, to pipe a set of variables in. You can pass in multiple variables (if your formatting string supports it) by putting a tuple after the percent. Thus,"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "print(\\"The variables specified earlier are %d, %d, and %d\\" % (a,b,c))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is a simple formatting structure that will satisfy most of your string formatting needs. More information on different format symbols is available in the [string formatting part of the standard docs](http://docs.python.org/release/2.5.2/lib/typesseq-strings.html).\\n",\
    "\\n",\
    "It's worth noting that more complicated string formatting methods are in development, but I prefer this system due to its simplicity and its similarity to C formatting strings.\\n",\
    "\\n",\
    "Recall we discussed multiline strings. We can put format characters in these as well, and fill them with the percent sign as before."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "form_letter = \\"\\"\\"\\\\\\n",\
    "\\n",\
    "          %s\\n",\
    "\\n",\
    "Dear %s,\\n",\
    "\\n",\
    "We regret to inform you that your product did not\\n",\
    "ship today due to %s.\\n",\
    "\\n",\
    "We hope to remedy this as soon as possible.\\n",\
    "\\n",\
    "          From,\\n",\
    "          Your Supplier\\n",\
    "\\"\\"\\"\\n",\
    "\\n",\
    "print(form_letter % (\\"July 1, 2013\\",\\"Valued Customer Bob\\",\\"alien attack\\"))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The problem with a long block of text like this is that it's often hard to keep track of what all of the variables are supposed to stand for. There's an alternate format where you can pass a dictionary into the formatted string, and give a little bit more information to the formatted string itself. This method looks like:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "form_letter = \\"\\"\\"\\\\\\n",\
    "\\n",\
    "          %(date)s\\n",\
    "\\n",\
    "Dear %(customer)s,\\n",\
    "\\n",\
    "We regret to inform you that your product did not\\n",\
    "ship today due to %(lame_excuse)s.\\n",\
    "\\n",\
    "We hope to remedy this as soon as possible.\\n",\
    "\\n",\
    "          From,\\n",\
    "          Your Supplier\\n",\
    "\\"\\"\\"\\n",\
    "\\n",\
    "print(form_letter % \{\\"date\\" : \\"July 1, 2013\\",\\"customer\\":\\"Valued Customer Bob\\",\\"lame_excuse\\":\\"alien attack\\"\})"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "By providing a little bit more information, you're less likely to make mistakes, like referring to your customer as \\"alien attack\\".\\n",\
    "\\n",\
    "As a scientist, you're less likely to be sending bulk mailings to a bunch of customers. But these are great methods for generating and submitting lots of similar runs, say scanning a bunch of different structures to find the optimal configuration for something.\\n",\
    "\\n",\
    "For example, you can use the following template for NWChem input files:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "nwchem_format = \\"\\"\\"\\n",\
    "start %(jobname)s\\n",\
    "\\n",\
    "title \\"%(thetitle)s\\"\\n",\
    "charge %(charge)d\\n",\
    "\\n",\
    "geometry units angstroms print xyz autosym\\n",\
    "%(geometry)s\\n",\
    "end\\n",\
    "\\n",\
    "basis\\n",\
    "  * library 6-31G**\\n",\
    "end\\n",\
    "\\n",\
    "dft\\n",\
    "  xc %(dft_functional)s\\n",\
    "  mult %(multiplicity)d\\n",\
    "end\\n",\
    "\\n",\
    "task dft %(jobtype)s\\n",\
    "\\"\\"\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "If you want to submit a sequence of runs to a computer somewhere, it's pretty easy to put together a little script, maybe even with some more string formatting in it:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "oxygen_xy_coords = [(0,0),(0,0.1),(0.1,0),(0.1,0.1)]\\n",\
    "charge = 0\\n",\
    "multiplicity = 1\\n",\
    "dft_functional = \\"b3lyp\\"\\n",\
    "jobtype = \\"optimize\\"\\n",\
    "\\n",\
    "geometry_template = \\"\\"\\"\\\\\\n",\
    "  O    %f     %f      0.0\\n",\
    "  H    0.0    1.0     0.0\\n",\
    "  H    1.0    0.0     0.0\\"\\"\\"\\n",\
    "\\n",\
    "for i,xy in enumerate(oxygen_xy_coords):\\n",\
    "    thetitle = \\"Water run #%d\\" % i\\n",\
    "    jobname = \\"h2o-%d\\" % i\\n",\
    "    geometry = geometry_template % xy\\n",\
    "    print(\\"---------\\")\\n",\
    "    print(nwchem_format % dict(thetitle=thetitle,charge=charge,jobname=jobname,jobtype=jobtype,\\n",\
    "                               geometry=geometry,dft_functional=dft_functional,multiplicity=multiplicity))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is a very bad geometry for a water molecule, and it would be silly to run so many geometry optimizations of structures that are guaranteed to converge to the same single geometry, but you get the idea of how you can run vast numbers of simulations with a technique like this.\\n",\
    "\\n",\
    "We used the **enumerate** function to loop over both the indices and the items of a sequence, which is valuable when you want a clean way of getting both. **enumerate** is roughly equivalent to:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def my_enumerate(seq):\\n",\
    "    l = []\\n",\
    "    for i in range(len(seq)):\\n",\
    "        l.append((i,seq[i]))\\n",\
    "    return l\\n",\
    "my_enumerate(oxygen_xy_coords)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Although enumerate uses **generators** (see below) so that it doesn't have to create a big list, which makes it faster for really long sequenes."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Optional arguments\\n",\
    "You will recall that the **linspace** function can take either two arguments (for the starting and ending points):"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.linspace(0,1)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "or it can take three arguments, for the starting point, the ending point, and the number of points:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.linspace(0,1,5)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can also pass in keywords to exclude the endpoint:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "np.linspace(0,1,5,endpoint=False)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Right now, we only know how to specify functions that have a fixed number of arguments. We'll learn how to do the more general cases here.\\n",\
    "\\n",\
    "If we're defining a simple version of linspace, we would start with:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def my_linspace(start,end):\\n",\
    "    npoints = 50\\n",\
    "    v = []\\n",\
    "    d = (end-start)/float(npoints-1)\\n",\
    "    for i in range(npoints):\\n",\
    "        v.append(start + i*d)\\n",\
    "    return v\\n",\
    "my_linspace(0,1)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can add an optional argument by specifying a default value in the argument list:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def my_linspace(start,end,npoints = 50):\\n",\
    "    v = []\\n",\
    "    d = (end-start)/float(npoints-1)\\n",\
    "    for i in range(npoints):\\n",\
    "        v.append(start + i*d)\\n",\
    "    return v"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This gives exactly the same result if we don't specify anything:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "my_linspace(0,1)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "But also let's us override the default value with a third argument:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "my_linspace(0,1,5)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can add arbitrary keyword arguments to the function definition by putting a keyword argument \\\\*\\\\*kwargs handle in:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def my_linspace(start,end,npoints=50,**kwargs):\\n",\
    "    endpoint = kwargs.get('endpoint',True)\\n",\
    "    v = []\\n",\
    "    if endpoint:\\n",\
    "        d = (end-start)/float(npoints-1)\\n",\
    "    else:\\n",\
    "        d = (end-start)/float(npoints)\\n",\
    "    for i in range(npoints):\\n",\
    "        v.append(start + i*d)\\n",\
    "    return v\\n",\
    "my_linspace(0,1,5,endpoint=False)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "What the keyword argument construction does is to take any additional keyword arguments (i.e. arguments specified by name, like \\"endpoint=False\\"), and stick them into a dictionary called \\"kwargs\\" (you can call it anything you like, but it has to be preceded by two stars). You can then grab items out of the dictionary using the **get** command, which also lets you specify a default value. I realize it takes a little getting used to, but it is a common construction in Python code, and you should be able to recognize it.\\n",\
    "\\n",\
    "There's an analogous \\\\*args that dumps any additional arguments into a list called \\"args\\". Think about the **range** function: it can take one (the endpoint), two (starting and ending points), or three (starting, ending, and step) arguments. How would we define this?"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def my_range(*args):\\n",\
    "    start = 0\\n",\
    "    step = 1\\n",\
    "    if len(args) == 1:\\n",\
    "        end = args[0]\\n",\
    "    elif len(args) == 2:\\n",\
    "        start,end = args\\n",\
    "    elif len(args) == 3:\\n",\
    "        start,end,step = args\\n",\
    "    else:\\n",\
    "        raise Exception(\\"Unable to parse arguments\\")\\n",\
    "    v = []\\n",\
    "    value = start\\n",\
    "    while True:\\n",\
    "        v.append(value)\\n",\
    "        value += step\\n",\
    "        if value > end: break\\n",\
    "    return v"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Note that we have defined a few new things you haven't seen before: a **break** statement, that allows us to exit a for loop if some conditions are met, and an exception statement, that causes the interpreter to exit with an error message. For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "my_range(60)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## List Comprehensions and Generators\\n",\
    "List comprehensions are a streamlined way to make lists. They look something like a list definition, with some logic thrown in. For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "evens1 = [2*i for i in range(10)]\\n",\
    "print(evens1)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You can also put some boolean testing into the construct:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "odds = [i for i in range(20) if i%2==1]\\n",\
    "odds"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Here i%2 is the remainder when i is divided by 2, so that i%2==1 is true if the number is odd. Even though this is a relative new addition to the language, it is now fairly common since it's so convenient."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**iterators** are a way of making virtual sequence objects. Consider if we had the nested loop structure:\\n",\
    "\\n",\
    "    for i in range(1000000):\\n",\
    "        for j in range(1000000):\\n",\
    "\\n",\
    "Inside the main loop, we make a list of 1,000,000 integers, just to loop over them one at a time. We don't need any of the additional things that a lists gives us, like slicing or random access, we just need to go through the numbers one at a time. And we're making 1,000,000 of them. \\n",\
    "\\n",\
    "**iterators** are a way around this. For example, the **xrange** function is the iterator version of range. This simply makes a counter that is looped through in sequence, so that the analogous loop structure would look like:\\n",\
    "\\n",\
    "    for i in xrange(1000000):\\n",\
    "        for j in xrange(1000000):\\n",\
    "\\n",\
    "Even though we've only added two characters, we've dramatically sped up the code, because we're not making 1,000,000 big lists.\\n",\
    "\\n",\
    "We can define our own iterators using the **yield** statement:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def evens_below(n):\\n",\
    "    for i in range(n):\\n",\
    "        if i%2 == 0:\\n",\
    "            yield i\\n",\
    "    return\\n",\
    "\\n",\
    "for i in evens_below(9):\\n",\
    "    print(i)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can always turn an iterator into a list using the **list** command:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "list(evens_below(9))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There's a special syntax called a **generator expression** that looks a lot like a list comprehension:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "evens_gen = (i for i in range(9) if i%2==0)\\n",\
    "for i in evens_gen:\\n",\
    "    print(i)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Factory Functions\\n",\
    "A factory function is a function that returns a function. They have the fancy name *lexical closure*, which makes you sound really intelligent in front of your CS friends. But, despite the arcane names, factory functions can play a very practical role.\\n",\
    "\\n",\
    "Suppose you want the Gaussian function centered at 0.5, with height 99 and width 1.0. You could write a general function."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def gauss(x,A,a,x0):\\n",\
    "    return A*exp(-a*(x-x0)**2)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "But what if you need a function with only one argument, like f(x) rather than f(x,y,z,...)? You can do this with Factory Functions:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def gauss_maker(A,a,x0):\\n",\
    "    def f(x):\\n",\
    "        return A*np.exp(-a*(x-x0)**2)\\n",\
    "    return f"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "x = np.linspace(0,1)\\n",\
    "g = gauss_maker(99.0,1.0,0.5)\\n",\
    "plt.plot(x,g(x))\\n",\
    "plt.show()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Everything in Python is an object, including functions. This means that functions can be returned by other functions. (They can also be passed into other functions, which is also useful, but a topic for another discussion.) In the **gauss_maker** example, the *g* function that is output \\"remembers\\" the A, a, x0 values it was constructed with, since they're all stored in the local memory space (this is what the *lexical closure* really refers to) of that function.\\n",\
    "\\n",\
    "Factories are one of the more important of the [Software Design Patterns](http://en.wikipedia.org/wiki/Software_design_pattern), which are a set of guidelines to follow to make high-quality, portable, readable, stable software. It's beyond the scope of the current work to go more into either factories or design patterns, but I thought I would mention them for people interested in software design."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Serialization: Save it for later\\n",\
    "*Serialization* refers to the process of outputting data (and occasionally functions) to a database or a regular file, for the purpose of using it later on. In the very early days of programming languages, this was normally done in regular text files. Python is excellent at text processing, and you probably already know enough to get started with this.\\n",\
    "\\n",\
    "When accessing large amounts of data became important, people developed database software based around the Structured Query Language (SQL) standard. I'm not going to cover SQL here, but, if you're interested, I recommend using the [sqlite3](http://docs.python.org/2/library/sqlite3.html) module in the Python standard library.\\n",\
    "\\n",\
    "As data interchange became important, the eXtensible Markup Language (XML) has emerged. XML makes data formats that are easy to write parsers for, greatly simplifying the ambiguity that sometimes arises in the process. Again, I'm not going to cover XML here, but if you're interested in learning more, look into [Element Trees](http://docs.python.org/2/library/xml.etree.elementtree.html), now part of the Python standard library.\\n",\
    "\\n",\
    "Python has a very general serialization format called **pickle** that can turn any Python object, even a function or a class, into a representation that can be written to a file and read in later. But, again, I'm not going to talk about this, since I rarely use it myself. Again, [the standard library documentation for pickle](http://docs.python.org/2/library/pickle.html#module-cPickle) is the place to go.\\n",\
    "\\n",\
    "What I am going to talk about is a relatively recent format call [JavaScript Object Notation](http://json.org/) (JSON) that has become very popular over the past few years. [There's a module in the standard library](http://docs.python.org/2/library/json.html) for encoding and decoding JSON formats. The reason I like JSON so much is that it looks almost like Python, so that, unlike the other options, you can look at your data and edit it, use it in another program, etc.\\n",\
    "\\n",\
    "Here's a little example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "# Data in a json format:\\n",\
    "json_data = \\"\\"\\"\\\\\\n",\
    "\{\\n",\
    "    \\"a\\": [1,2,3],\\n",\
    "    \\"b\\": [4,5,6],\\n",\
    "    \\"greeting\\" : \\"Hello\\"\\n",\
    "\}\\"\\"\\"\\n",\
    "import json\\n",\
    "json.loads(json_data)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Ignore the little u's before the strings, these just mean the strings are in UNICODE. Your data sits in something that looks like a Python dictionary, and in a single line of code, you can load it into a Python dictionary for use later.\\n",\
    "\\n",\
    "In the same way, you can, with a single line of code, put a bunch of variables into a dictionary, and then output to a file using json:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "json.dumps(\{\\"a\\":[1,2,3],\\"b\\":[9,10,11],\\"greeting\\":\\"Hola\\"\})"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Functional programming\\n",\
    "Functional programming is a very broad subject. The idea is to have a series of functions, each of which generates a new data structure from an input, without changing the input structure at all. By not modifying the input structure (something that is called not having *side effects*), many guarantees can be made about how independent the processes are, which can help parallelization and guarantees of program accuracy. There is a [Python Functional Programming HOWTO](http://docs.python.org/2/howto/functional.html) in the standard docs that goes into more details on functional programming. I just wanted to touch on a few of the most important ideas here.\\n",\
    "\\n",\
    "There is an **operator** module that has function versions of most of the Python operators. For example:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from operator import add, mul\\n",\
    "add(1,2)"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "mul(3,4)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "These are useful building blocks for functional programming."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **lambda** operator allows us to build *anonymous functions*, which are simply functions that aren't defined by a normal **def** statement with a name. For example, a function that doubles the input is:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def doubler(x): return 2*x\\n",\
    "doubler(17)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We could also write this as:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "lambda x: 2*x"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "And assign it to a function separately:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "another_doubler = lambda x: 2*x\\n",\
    "another_doubler(19)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**lambda** is particularly convenient (as we'll see below) in passing simple functions as arguments to other functions."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**map** is a way to repeatedly apply a function to a list:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "list(map(float,'1 2 3 4 5'.split()))"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "**reduce** is a way to repeatedly apply a function to the first two items of the list. There already is a **sum** function in Python that is a reduction:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "sum([1,2,3,4,5])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can use **reduce** to define an analogous **prod** function:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "from functools import reduce\\n",\
    "def prod(l): return reduce(mul,l)\\n",\
    "prod([1,2,3,4,5])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Object Oriented Programming"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We've seen a lot of examples of **objects** in Python. We create a string object with quote marks:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "mystring = \\"Hi there\\""\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "and we have a bunch of methods we can use on the object:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "mystring.split()"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "mystring.startswith('Hi')"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "len(mystring)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Object oriented programming simply gives you the tools to define objects and methods for yourself. It's useful anytime you want to keep some data (like the characters in the string) tightly coupled to the functions that act on the data (length, split, startswith, etc.).\\n",\
    "\\n",\
    "As an example, we're going to bundle the functions we did to make the 1d harmonic oscillator eigenfunctions with arbitrary potentials, so we can pass in a function defining that potential, some additional specifications, and get out something that can plot the orbitals, as well as do other things with them, if desired."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "class Schrod1d:\\n",\
    "    \\"\\"\\"\\\\\\n",\
    "    Schrod1d: Solver for the one-dimensional Schrodinger equation.\\n",\
    "    \\"\\"\\"\\n",\
    "    def __init__(self,V,start=0,end=1,npts=50,**kwargs):\\n",\
    "        m = kwargs.get('m',1.0)\\n",\
    "        self.x = np.linspace(start,end,npts)\\n",\
    "        self.Vx = V(self.x)\\n",\
    "        self.H = (-0.5/m)*self.laplacian() + np.diag(self.Vx)\\n",\
    "        return\\n",\
    "    \\n",\
    "    def plot(self,*args,**kwargs):\\n",\
    "        titlestring = kwargs.get('titlestring',\\"Eigenfunctions of the 1d Potential\\")\\n",\
    "        xstring = kwargs.get('xstring',\\"Displacement (bohr)\\")\\n",\
    "        ystring = kwargs.get('ystring',\\"Energy (hartree)\\")\\n",\
    "        if not args:\\n",\
    "            args = [3]\\n",\
    "        x = self.x\\n",\
    "        E,U = np.linalg.eigh(self.H)\\n",\
    "        h = x[1]-x[0]\\n",\
    "\\n",\
    "        # Plot the Potential\\n",\
    "        plt.plot(x,self.Vx,color='k')\\n",\
    "\\n",\
    "        for i in range(*args):\\n",\
    "            # For each of the first few solutions, plot the energy level:\\n",\
    "            plt.axhline(y=E[i],color='k',ls=\\":\\")\\n",\
    "            # as well as the eigenfunction, displaced by the energy level so they don't\\n",\
    "            # all pile up on each other:\\n",\
    "            plt.plot(x,U[:,i]/np.sqrt(h)+E[i])\\n",\
    "        plt.title(titlestring)\\n",\
    "        plt.xlabel(xstring)\\n",\
    "        plt.ylabel(ystring) \\n",\
    "        plt.show()\\n",\
    "        return\\n",\
    "        \\n",\
    "    def laplacian(self):\\n",\
    "        x = self.x\\n",\
    "        h = x[1]-x[0] # assume uniformly spaced points\\n",\
    "        n = len(x)\\n",\
    "        M = -2*np.identity(n,'d')\\n",\
    "        for i in range(1,n):\\n",\
    "            M[i,i-1] = M[i-1,i] = 1\\n",\
    "        return M/h**2"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The **__init__()** function specifies what operations go on when the object is created. The **self** argument is the object itself, and we don't pass it in. The only required argument is the function that defines the QM potential. We can also specify additional arguments that define the numerical grid that we're going to use for the calculation.\\n",\
    "\\n",\
    "For example, to do an infinite square well potential, we have a function that is 0 everywhere. We don't have to specify the barriers, since we'll only define the potential in the well, which means that it can't be defined anywhere else."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "square_well = Schrod1d(lambda x: 0*x,m=10)\\n",\
    "square_well.plot(4,titlestring=\\"Square Well Potential\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "We can similarly redefine the Harmonic Oscillator potential."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "ho = Schrod1d(lambda x: x**2,start=-3,end=3)\\n",\
    "ho.plot(6,titlestring=\\"Harmonic Oscillator\\")"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Let's define a finite well potential:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def finite_well(x,V_left=1,V_well=0,V_right=1,d_left=10,d_well=10,d_right=10):\\n",\
    "    V = np.zeros(x.size,'d')\\n",\
    "    for i in range(x.size):\\n",\
    "        if x[i] < d_left: \\n",\
    "            V[i] = V_left\\n",\
    "        elif x[i] > (d_left+d_well):\\n",\
    "            V[i] = V_right\\n",\
    "        else:\\n",\
    "            V[i] = V_well\\n",\
    "    return V\\n",\
    "        \\n",\
    "fw = Schrod1d(finite_well,start=0,end=30,npts=100)\\n",\
    "fw.plot()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "A triangular well:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def triangular(x,F=30): return F*x\\n",\
    "\\n",\
    "tw = Schrod1d(triangular,m=10)\\n",\
    "tw.plot()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Or we can combine the two, making something like a semiconductor quantum well with a top gate:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def tri_finite(x): return finite_well(x)+triangular(x,F=0.025)\\n",\
    "\\n",\
    "tfw = Schrod1d(tri_finite,start=0,end=30,npts=100)\\n",\
    "tfw.plot()"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "There's a lot of philosophy behind object oriented programming. Since I'm trying to focus on just the basics here, I won't go into them, but the internet is full of lots of resources on OO programming and theory. The best of this is contained in the [Design Patterns](http://en.wikipedia.org/wiki/Design_Patterns_(book)) book, which I highly recommend."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# IV. Speeding Python: Timeit, Profiling, Cython, SWIG, and PyPy\\n",\
    "\\n",\
    "The first rule of speeding up your code is not to do it at all. As Donald Knuth said:\\n",\
    "\\n",\
    "> \\"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.\\"\\n",\
    "\\n",\
    "The second rule of speeding up your code is to only do it if you really think you need to do it. Python has two tools to help with this process: a timing program called **timeit**, and a very good code profiler. We will discuss both of these tools in this section, as well as techniques to use to speed up your code once you know it's too slow.\\n",\
    "\\n",\
    "## Timeit\\n",\
    "**timeit** helps determine which of two similar routines is faster. Recall that some time ago we wrote a factorial routine, but also pointed out that Python had its own routine built into the math module. Is there any difference in the speed of the two? **timeit** helps us determine this. For example, **timeit** tells how long each method takes:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "%timeit factorial(20)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "The little % sign that we have in front of the timeit call is an example of an IPython magic function, which we don't have time to go into here, but it's just some little extra mojo that IPython adds to the functions to make it run better in the IPython environment. You can read more about it in the [IPython tutorial](http://ipython.org/ipython-doc/dev/interactive/tutorial.html).\\n",\
    "\\n",\
    "In any case, the timeit function runs 3 loops, and tells us that it took on the average of 583 ns to compute 20!. In contrast:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "%timeit fact(20)"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "the factorial function we wrote is about a factor of 10 slower. This is because the built-in factorial function is written in C code and called from Python, and the version we wrote is written in plain old Python. A Python program has a lot of stuff in it that make it nice to interact with, but all that friendliness slows down the code. In contrast, the C code is less friendly but more efficient. If you want speed with as little effort as possible, write your code in an easy to program language like Python, but dump the slow parts into a faster language like C, and call it from Python. We'll go through some tricks to do this in this section."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Profiling"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Profiling complements what **timeit** does by splitting the overall timing into the time spent in each function. It can give us a better understanding of what our program is really spending its time on.\\n",\
    "\\n",\
    "Suppose we want to create a list of even numbers. Our first effort yields this:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def evens(n):\\n",\
    "    \\"Return a list of even numbers below n\\"\\n",\
    "    l = []\\n",\
    "    for x in range(n):\\n",\
    "        if x % 2 == 0:\\n",\
    "            l.append(x)\\n",\
    "    return l"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Is this code fast enough? We find out by running the Python profiler on a longer run:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import cProfile\\n",\
    "cProfile.run('evens(100000)')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This looks okay, 0.05 seconds isn't a *huge* amount of time, but looking at the profiling shows that the **append** function is taking almost 20% of the time. Can we do better? Let's try a list comprehension."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def evens2(n):\\n",\
    "    \\"Return a list of even numbers below n\\"\\n",\
    "    return [x for x in range(n) if x % 2 == 0]"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import cProfile\\n",\
    "cProfile.run('evens2(100000)')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "By removing a small part of the code using a list comprehension, we've doubled the overall speed of the code! \\n",\
    "\\n",\
    "It seems like **range** is taking a long time, still. Can we get rid of it? We can, using the **xrange** generator:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def evens3(n):\\n",\
    "    \\"Return a list of even numbers below n\\"\\n",\
    "    return [x for x in range(n) if x % 2 == 0]"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "import cProfile\\n",\
    "cProfile.run('evens3(100000)')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This is where profiling can be useful. Our code now runs 3x faster by making trivial changes. We wouldn't have thought to look in these places had we not had access to easy profiling. Imagine what you would find in more complicated programs."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Other Ways to Speed Python\\n",\
    "When we compared the fact and factorial functions, above, we noted that C routines are often faster because they're more streamlined. Once we've determined that one routine is a bottleneck for the performance of a program, we can replace it with a faster version by writing it in C. This is called *extending* Python, and there's a [good section in the standard documents](http://docs.python.org/2/extending/extending.html). This can be a tedious process if you have many different routines to convert. Fortunately, there are several other options.\\n",\
    "\\n",\
    "[Swig](http://swig.org/) (the simplified wrapper and interface generator) is a method to generate binding not only for Python but also for Matlab, Perl, Ruby, and other scripting languages. Swig can scan the header files of a C project and generate Python binding for it. Using Swig is substantially easier than writing the routines in C.\\n",\
    "\\n",\
    "[Cython](http://www.cython.org/) is a C-extension language. You can start by compiling a Python routine into a shared object libraries that can be imported into faster versions of the routines. You can then add additional static typing and make other restrictions to further speed the code. Cython is generally easier than using Swig.\\n",\
    "\\n",\
    "[PyPy](http://pypy.org/) is the easiest way of obtaining fast code. PyPy compiles Python to a subset of the Python language called RPython that can be efficiently compiled and optimized. Over a wide range of tests, PyPy is [roughly 6 times faster than the standard Python Distribution](http://speed.pypy.org/)."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "## Fun: Finding Primes\\n",\
    "\\n",\
    "[Project Euler](http://projecteuler.net) is a site where programming puzzles are posed that might have interested Euler. [Problem 7](http://projecteuler.net/problem=7) asks the question:\\n",\
    "\\n",\
    "> By listing the first six prime numbers: 2, 3, 5, 7, 11, and 13, we can see that the 6th prime is 13.\\n",\
    "> \\n",\
    "> What is the 10,001st prime number?\\n",\
    "\\n",\
    "To solve this we need a very long list of prime numbers. First we'll make a function that uses the Sieve of Erastothenes to generate all the primes less than n."\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "def primes(n):\\n",\
    "    \\"\\"\\"\\\\\\n",\
    "    From python cookbook, returns a list of prime numbers from 2 to < n\\n",\
    "\\n",\
    "    >>> primes(2)\\n",\
    "    [2]\\n",\
    "    >>> primes(10)\\n",\
    "    [2, 3, 5, 7]\\n",\
    "    \\"\\"\\"\\n",\
    "    if n==2: return [2]\\n",\
    "    elif n<2: return []\\n",\
    "    s=list(range(3,n+1,2))\\n",\
    "    mroot = n ** 0.5\\n",\
    "    half=(n+1)//2-1\\n",\
    "    i=0\\n",\
    "    m=3\\n",\
    "    while m <= mroot:\\n",\
    "        if s[i]:\\n",\
    "            j=(m*m-3)//2\\n",\
    "            s[j]=0\\n",\
    "            while j<half:\\n",\
    "                s[j]=0\\n",\
    "                j+=m\\n",\
    "        i=i+1\\n",\
    "        m=2*i+3\\n",\
    "    return [2]+[x for x in s if x]"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "number_to_try = 1000000\\n",\
    "list_of_primes = primes(number_to_try)\\n",\
    "print(list_of_primes[10001])"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "You might think that Python is a bad choice for something like this, but, in terms of time, it really doesn't take long:"\
   ]\
  \},\
  \{\
   "cell_type": "code",\
   "execution_count": null,\
   "metadata": \{\},\
   "outputs": [],\
   "source": [\
    "cProfile.run('primes(1000000)')"\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "Only takes 1/4 of a second to generate a list of all the primes below 1,000,000. It would be nice if we could use the same trick to get rid of the **range** function, but we actually need it, since we're using the object like a list, rather than like a counter as before."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# VII. References\\n",\
    "\\n",\
    "## Learning Resources\\n",\
    "* [Official Python Documentation](http://docs.python.org/2.7), including\\n",\
    "    - [Python Tutorial](http://docs.python.org/2.7/tutorial)\\n",\
    "    - [Python Language Reference](http://docs.python.org/2.7/reference)\\n",\
    "* If you're interested in Python 3, the [Official Python 3 Docs are here](http://docs.python.org/3/).\\n",\
    "* [IPython tutorial](http://ipython.org/ipython-doc/dev/interactive/tutorial.html).\\n",\
    "* [Learn Python The Hard Way](http://learnpythonthehardway.org/book/)\\n",\
    "* [Dive Into Python](http://www.diveintopython.net/), in particular if you're interested in Python 3.\\n",\
    "* [Invent With Python](http://inventwithpython.com/), probably best for kids.\\n",\
    "* [Python Functional Programming HOWTO](http://docs.python.org/2/howto/functional.html)\\n",\
    "* [The Structure and Interpretation of Computer Programs](http://mitpress.mit.edu/sicp/full-text/book/book.html), written in Scheme, a Lisp dialect, but one of the best books on computer programming ever written.\\n",\
    "* [Generator Tricks for Systems Programmers](http://www.dabeaz.com/generators/) Beazley's slides on just what generators can do for you.\\n",\
    "* [Python Module of the Week](http://pymotw.com/2/contents.html) is a series going through in-depth analysis of the Python standard library in a very easy to understand way.\\n",\
    "\\n",\
    "## Badass IPython Notebooks\\n",\
    "* Rob Johansson's [excellent notebooks](http://jrjohansson.github.io/), including [Scientific Computing with Python](https://github.com/jrjohansson/scientific-python-lectures) and [Computational Quantum Physics with QuTiP](https://github.com/jrjohansson/qutip-lectures) lectures;\\n",\
    "* [XKCD style graphs in matplotlib](http://nbviewer.ipython.org/url/jakevdp.github.com/downloads/notebooks/XKCD_plots.ipynb);\\n",\
    "* [A collection of Notebooks for using IPython effectively](https://github.com/ipython/ipython/tree/master/examples/notebooks#a-collection-of-notebooks-for-using-ipython-effectively)\\n",\
    "* [A gallery of interesting IPython Notebooks](https://github.com/ipython/ipython/wiki/A-gallery-of-interesting-IPython-Notebooks)\\n",\
    "* [Cross-disciplinary computational analysis IPython Notebooks From Hadoop World 2012](https://github.com/invisibleroads/crosscompute-tutorials)\\n",\
    "* [Quantites](http://nbviewer.ipython.org/urls/raw.github.com/tbekolay/pyconca2012/master/QuantitiesTutorial.ipynb) Units in Python.\\n",\
    "    - [Another units module is here](http://www.southampton.ac.uk/~fangohr/blog/)\\n",\
    "\\n",\
    "## Packages for Scientists\\n",\
    "Important libraries\\n",\
    "\\n",\
    "* [Python](http://www.python.org) version 2.7;\\n",\
    "* [Numpy](http://www.numpy.org), the core numerical extensions for linear algebra and multidimensional arrays;\\n",\
    "* [Scipy](http://www.scipy.org), additional libraries for scientific programming;\\n",\
    "* [Matplotlib](http://matplotlib.sf.net), excellent plotting and graphing libraries;\\n",\
    "* [IPython](http://ipython.org), with the additional libraries required for the notebook interface.\\n",\
    "* [Sympy](http://sympy.org), symbolic math in Python\\n",\
    "* [Pandas](http://pandas.pydata.org/) library for big data in Python\\n",\
    "\\n",\
    "Other packages of interest\\n",\
    "\\n",\
    "* [PyQuante](http://pyquante.sf.net) Python Quantum Chemistry\\n",\
    "* [QuTiP](https://code.google.com/p/qutip/) Quantum Toolbox in Python\\n",\
    "* Konrad Hinsen's [Scientific Python](http://dirac.cnrs-orleans.fr/plone/software/scientificpython/) and [MMTK](http://dirac.cnrs-orleans.fr/MMTK/)\\n",\
    "* [Atomic Simulation Environment](https://wiki.fysik.dtu.dk/ase/)\\n",\
    "\\n",\
    "\\n",\
    "## Cool Stuff\\n",\
    "* [Moin Moin](http://moinmo.in/), a wiki written in Python\\n",\
    "* [Project Euler](http://projecteuler.net/), programming problems that would (?) have interested Euler. Python is one of the most commonly used languages there."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "# VI. Acknowledgements\\n",\
    "Thanks to Alex and Tess for everything!\\n",\
    "\\n",\
    "Thanks to Barbara Muller and Tom Tarman for helpful suggestions."\
   ]\
  \},\
  \{\
   "cell_type": "markdown",\
   "metadata": \{\},\
   "source": [\
    "This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/deed.en_US). The work is offered for free, with the hope that it will be useful. Please consider making a donation to the [John Hunter Memorial Fund](http://numfocus.org/johnhunter/).\\n",\
    "\\n",\
    "![CC BY SA](http://i.creativecommons.org/l/by-sa/3.0/88x31.png)\\n",\
    "\\n",\
    "![Sandia](http://upload.wikimedia.org/wikipedia/commons/thumb/3/32/Sandia_National_Laboratories_logo.svg/200px-Sandia_National_Laboratories_logo.svg.png)\\n",\
    "\\n",\
    "Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company, for the United States Department of Energy's National Nuclear Security Administration under Contract DE-AC04-94AL85000.\\n",\
    "\\n",\
    "<img src=\\"https://upload.wikimedia.org/wikipedia/commons/8/81/Seal_of_the_United_States_Department_of_Energy.png\\" alt=\\"DOE\\" style=\\"width: 120px;\\"/>\\n",\
    "\\n",\
    "Jian Tao would like to thank [Texas A&M Engineering Experiment Station](http://tees.tamu.edu/) and [Texas A&M High Performance Reseach Computing](https://hprc.tamu.edu/) for the continuous support.\\n",\
    "\\n",\
    "<img src=\\"https://brandguide.tamu.edu/downloads/logos/TAM-Stack.png\\" alt=\\"TAMU\\" style=\\"width: 150px;\\"/>\\n"\
   ]\
  \}\
 ],\
 "metadata": \{\
  "kernelspec": \{\
   "display_name": "Python 3",\
   "language": "python",\
   "name": "python3"\
  \},\
  "language_info": \{\
   "codemirror_mode": \{\
    "name": "ipython",\
    "version": 3\
   \},\
   "file_extension": ".py",\
   "mimetype": "text/x-python",\
   "name": "python",\
   "nbconvert_exporter": "python",\
   "pygments_lexer": "ipython3",\
   "version": "3.6.3"\
  \}\
 \},\
 "nbformat": 4,\
 "nbformat_minor": 1\
\}}