UPDATE: I have changed how I setup my Python environment. These instructions are no longer up to date and may not work on newer versions of the Mac OS.
I use a Mac computer for most of my research, with the exception of running large climate models, which is usually done on clusters that are built from Linux machines. For most of my work, the Mac OS X operating system provides me computational foundation I need to develop and run planetary climate models. I am not a fanatic follower of Apple and I will use Windows machines when the task demands it, e.g. CAD design on Solidworks or mapping on ArcGIS. For me, a computer OS is just another tool, like Fortran, Python, a spectrometer, or a soldering iron. I have a toolbox and I put the tools in for the job. The trick is setting up the tools right.
Since I am using the Unix underpinnings of Mac OS X, my setup requires a number of steps that the average Mac owner does not need in order to be productive. Most of these additional steps involve installing and configuring software for writing my modeling and analysis code. This is essential for my research. The rest of the additional steps are there just to make my life easier.
Once you dive into the Unix engine under the hood, you are no longer working with Mac OS X software installers. Instead, you are often in the realm of package managers, compiling your own code, and customizing the paths and configurations. Not being a computer scientist, I was intimidated at first. Fortunately, a number of people posted their own experiences in setting up their own systems1. Over time I strung together disparate instructions and suggestions that resulted in a working system for me. In the spirit of paying things forward, I am providing this description of my setup2 in case it might be useful to another scientist out there facing the same problems that I already faced.
Wrangling BASH preferences: my new dotfiles system
I use a number of machines at work and home, with a roughly 50/50 split between Macs and Linux machines. I like to have the Unix environment set up the same on all of the machines. Ideally, this means using a bash shell with a custom prompt, colored ls output, and all of my standard aliases in place. Historically, I have gone through a tedious process with every new machine in which I manually recreate the set up that I already have on my other machines. With my most recent new computer, I have adopted a more systematic and automated way of maintaining syncing my environments on different machines: I have created a 'dotfiles' system using a simple script and GitHub.
This method is based on Michael Smalley's dotfiles setup, which he described at his blog. I built on his script and setup to create my own dotfiles system. The code in my repository organizes my various dotfiles, including
.vimrc, and others. The repository is cloned into the home directory of any of my machines such that the path is
makesymlinks.sh setup script creates symlinks of the dotfiles from the home directory to the files in
~/dotfiles/. The setup script is smart enough to back up my existing dotfiles into a
~/dotfiles_old/ directory thus giving me a means of reversing any changes. By hosting the code on GitHub, I can clone and setup this system on any Unix based machine that I work on. Right now, the files are designed to be universal, but eventually I will add some smarts to the system so that I can have some customizations setup for different flavors of Unix (Linux or Mac OS X) and possibly for different shells (csh, tcsh, zsh, etc.).
iTerm and Solarized
I use iTerm2 for my Mac terminal. After years of fighting with terminal color schemes, I have settled on a scheme created and used by many software engineers: Solarized. I am a bit indifferent to the specific colors, but the scheme overall works really well and gives me two consistent and easy to apply colors schemes, one light color scheme and one dark color scheme. Also, the color scheme is available to a number of other programs. For example, I used Solarized for my vim apps as well.
Alright, it is time to get started on configuring Mac Mavericks for scientific research. First, we need to be sure that we have XCode installed. XCode provides a number of tools that a scientific programmer will likely not need, but the Command Line tools included in XCode are critical for scientific programming. So, if you don't already have XCode, get it from the App Store.
Once you have installed XCode from the App Store, then you need to install the command line developer tools. Using the command line, enter:
This will generate a pop-up message asking to install the command line developer tools. Go ahead and install. Once that is successfully done you will then have a number of command line tools that we will be using throughout the rest of this setup.
Mac OS X no longer comes with a pre-installed X-Window manager for use with the terminal and command line tools. Therefore, you need to be sure you have X11/XQuartz installed. Visit http://xquartz.macosforge.org/trac/wiki and download and install the most recent version. Just follow the instructions at the XQuartz site. You might need to fix the symlink it makes by entering the following command in the terminal:
Package Manager: Homebrew
To install and manage many of my tools I use Homebrew. There are other package managers for OS X, including MacPorts and Fink, but I have found Homebrew to be the most usable and useful. Needs and preferences will vary.
A fresh installation of Homebrew
To install Homebrew from scratch, run the following command:
This will both download and install the Homebrew software. After installing, run 'brew doctor' to insure that everything was installed correctly. If everything is working well, then you can start installing packages. For example, I install HDF5, NetCF, ack, and the Silver Searcher (ag), among others. The Homebrew website provides details on how to use Homebrew. As well, typing
man brew at the command line will bring up the manual page for Homebrew.
Updating Homebrew from a previous version of OS X
Since I actually had Homebrew installed for Mountain Lion before my upgrade to Mavericks, I took the following steps to make sure everything was still working properly.
I started with the command:
which told me what packages I have installed. Many of these packages were installed in support of others, but I generally know which ones I intentionally installed. For these, I tried running each package. If the command worked, then I was all set and left things along. If a particular package did not run, then I needed to remove it and reinstall, using the following commands:
These instructions are based on step 5 from myobie's Gist.
Installing NetCDF Operators (NCO) using homebrew-science
The baseic Homebrew database does not include formulas for all of the scientific software that I need. Instead, we need to use an additional Homebrew database, 'homebrew-science'. From homebrew-science we have instructions for installing software from this alternative database. First, we need to tell brew to use this alternative database. This is done by 'tapping' the database. The command to do this for homebrew-science is:
Now that homebrew-science is 'tapped' we can start install software from that database. The command is similar to any Homebrew install command:
If the formula conflicts with one from the master database or another tap, you can install with this version of the install command:
You can also install via URL:
To get the NetCDF Operators, I then entered the following command:
That's it. I now have NetCDF Operators like ncks and nccat installed along with NCView for viewing NetCDF files. Since most climate models output the simulations results as NetCDF files, I am not ready to inspect the climate simulation output of almost any moedl.
Installing GrADS using homebrew-science
The GrADS tool is useful for plotting climate data and can read in NetCDF files. Though I primarily use Python for plotting, GrADS has its place in my scientific workflow. In order to get GrADS, we will need to access an alternative Homebrew database. Similar to homebrew-science we need to tap homebrew-binary to get GrADS:
I want a copy of GrADS, so I type at the command line
If the formula conflicts with one from mxcl/master or another tap, you can
You can also install via URL:
Again, that's all there is to it. Now I have a copy of GrADS on my machine.
Installing Homebrew Python3
Plenty of arguments are given on the web for not merely using Apple's installation of Python (e.g. Hacker Codex's discussion), but for me, it's mainly because I want all of my packages to play well together within Homebrew.
Getting Python 2.7.6 installed is pretty straightforward. The command is:
This will also install package management tools like pip, which we'll need later. For my scientific work, I only need Python 2.7.x. Most scientific and mathematical packages have not yet moved to Python 3.x.
Installing the SciPy Superpack
Although the Enthought Python distribution provides an all-in-one, turnkey solution to getting SciPy and matplotlib installed, EPD does not play well with Homebrew, my preferred package manager on the Mac. Therefore I am trying a different route, namely the SciPy Superpack.
Now it was time to install the SciPy Superpack, developed by Chris Fonnesbeck . I used his very simple instructions to get this code installed. First, there was a curl command:
Then, I move the script to my bin directory, at ~/bin/ . I then ran the script by typing:
Once this script was done, I had installed Numpy, SciPy, Matplotlib, iPython, Pandas, Statsmodels, Scikit-Learn, and PyMC.
Just another pretty interface: qtconsole
I decided to take everyone's (on the internets) suggestion and install qtconsole to provide an aesthetically pleasing interface for iPython4. This was the trickiest step yet. First I had to install the Qt software. Unfortunately, the newest version, 5.0, comes packaged with quite a bit of stuff (e.g. the "Creator") that I do not want. I just want the console. So I went to https://qt-project.org/downloads and downloaded the Qt Library for version 4.8. Once I ran the installer, the basic Qt software was in place.
Next I downloaded the PySide libraries and used the package installer to install the libraries. Just follow that link and the PySide libraries should start downloading. Then, using pip5, I installed pygments through the command:
Finally, I installed pyqt by typing:
Once I did all of this, I was able to verify that I had a working qtconsole by executing the following commands:
The last command produces the following output: <!-- _includes/image.html --> <!-- From: http://codingtips.kanishkkunal.in/image-caption-jekyll/ -->
<img src="/images/qtconsole_screenshot.png" alt=""/>
So now I have a pretty iPython console with inline plotting.
NetCDF4: the only way to read and write climate data
For my climate modeling work I need the netCDF-python package installed. Fortunately, because of the Python Package Index (PyPi) and the pip command, this is one of the easiest steps in the installation process.
Here's the command:
And that's it. This set up works with the Homebrew Python, HDF5, and NetCDF4 as well as with the SciPy Superpack.
In conclusion . . .
At this point, I have a Mac that is ready for some scientific heavy lifting. I can compile scientific code, inspect and analyze climate model output, and manage my data with the tools that I have now installed and configured. Of course, this means that the fun has only begun, because it's time to do some science!
For example, see Hacker Codex's instructions for configuring Mavericks and installing Homebrew Python and other tools. As well, both Nathan and Lowin Data have good instructions for various configurations. ↩
These instructions apply to Mac OS X Mavericks. These instructions may or may not work with earlier versions of Mac OS X. ↩
See the articles "Installing python, numpy, scipy, matplotlib, and ipython on Lion" and "Installing the IPython qtconsole in Mac OS X" and "Setting up Mountain Lion". This is more than an aesthetic upgrade; the
qtconsoleprovides additional functionality when working with iPython. The iPython website points out that: " This is a very lightweight widget that largely feels like a terminal, but provides a number of enhancements only possible in a GUI, such as inline figures, proper multiline editing with syntax highlighting, graphical calltips, and much more." ↩
pip was installed as part of the Homebrew Python installation. ↩