https://github.com/rlabbe/ThinkBayes

Jupyter Notebooks derived from Allen Downey's book Think Bayes.
https://github.com/rlabbe/ThinkBayes

Last synced: about 2 months ago
JSON representation

Jupyter Notebooks derived from Allen Downey's book Think Bayes.

• Host: GitHub
• URL: https://github.com/rlabbe/ThinkBayes
• Owner: rlabbe
• Fork: true (AllenDowney/ThinkBayes)
• Created: 2015-08-04T14:08:01.000Z (almost 9 years ago)
• Default Branch: master
• Last Pushed: 2016-02-25T15:34:31.000Z (over 8 years ago)
• Last Synced: 2024-01-27T07:38:57.209Z (5 months ago)
• Language: Jupyter Notebook
• Homepage:
• Size: 42.6 MB
• Stars: 395
• Watchers: 33
• Forks: 191
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Lists

• pycrumbs - Jupyter Notebooks derived from Allen Downey's Think Bayes

README

        
ThinkBayes

==========

Launch now and run interactively by clicking this badge,

then navigate to the \notebooks directory and open the

notebook corresponding to the chapter you want to read: 

[![Binder](http://mybinder.org/badge.svg)](http://mybinder.org/repo/rlabbe/ThinkBayes)

This material was adapted from Allen Downey's Think Bayes 

Github repository by Roger Labbe. 

Mostly I took his code and tex file and converted them into

a series of Jupyter notebooks. This was sometimes problamatic.

Allen uses a lot of Python classes, and his exposition splits

the code across multiple paragraphs. It's a great pedagogical

technique, but does not cleanly work in notebooks, where you have

to specify the entire class in one cell. Furthermore, most of 

his code is in .py files. 

I made this work as best I could, but sometimes there were

authorial decisions that I do not feel comfortable making. 

The code just doesn't run in those spots. Sometimes I left

the code in markdown cells rather than putting it in code

cells, and then imported the class from the .py file. I kind

of figured this out as I proceeded, so perhaps there are

stylistic differences in the back vs the front of the book.

He generates many graphs, but does not supply the source code.

Maybe the code is in the /code subdirectory? In a few places 

I took the liberty of supplying the Python, but in many places

I did not. Maybe somebody else will feel like doing that; 

I don't really have time right now. Pull requests accepted!

There are several places in the text where it was not clear

to me where he got his datasets. Rather than making something

up, I just let the code cells fail to execute. I hope Allen

will help me rectify these situations. If not, and there is

enough interest, we can make some decisions and get the cells

working.

I put his code in a /code subdirectory. I did not fix the references

in the book, which specify going to his home page to get the code.

Again, I wanted to make as few editorial decisions as possible.

I did alter most of the code to work with Python 3. Mainly by using

    from __future__ import print_function

    

but in a few places I had to fix things like removing `xrange` or

`iterkeys()`. I only did just enough work to get it working.

His original README is:

https://github.com/AllenDowney/ThinkBayes

Code repository for Think Bayes: Bayesian Statistics Made Simple

by Allen B. Downey

Available from Green Tea Press at http://thinkbayes.com.

Published by O'Reilly Media, October 2013.