code cleanup

[jeremymanning]

Before releasing this toolbox, we need to do a substantial code cleanup. This includes:

• [x] ensuring that all function names are clearly named and/or documented

• [x] ensuring that all variable and function names use consistent conventions

• [x] ensuring that the code is written as clearly and succinctly as possible

• [x] creating some test datasets and a battery of unit tests (one for each intended use case) that we can use to verify that nothing is broken in future updates, and that users can use to verify that their install is correct.

• [ ] testing the installation on several "clean" systems (e.g. fresh OS X install, NeuroDebian, etc.). As a sub-issue of this, we need to decide whether to support Windows. (I'm leaning towards no, unless it's easy to get the toolbox working on Windows and we can track down a system to test it on.)

[andrewheusser]

re the last bullet, travis ci is capable of testing on multiple platforms / python versions so once that is hooked up, ill close this issue

[andrewheusser]

im going to close this issue, and open a new one for travis-ci integration