switch to cubic interpolation

was avoiding this before I was doing interval intersection, since, where
the intervals weren't overlapping (and the data was partially made-up),
the made-up values were pretty unuseful

I think this is fine though now that I only show the interval in which
everything is overlapping (though it might still get wacky if there are
gaps within the range from a bucket/node)