Fixed the weird bug that I couldn't comprehend for the longest time -
but after adding a mathjax view to display the parameter values (branch
mathjax) I figured out that I was passing the per-x-y-float-pair index
to the Matrix mapPoints routine when it wanted the index of the float
that started the x-y pair.  Finally lookin' pretty smooth :)