Preprocessing

Preprocessing is done (sorta, kinda, good enough).

Input:
- Some sort of image (see driver.m)

Output:
- Cell array of features, where each cell contains data for a pixel grouping. Features include:

> Width, Height, Pixel Count, Midpoint (by pixel density), X, Y

This closes #4 and contains most of the shit needed for #7 .

As discussed before, I need two people to check this pull request. First person can comment approval, second person comments & merges.

Enjoy!!

Yes. It always starts the boundary checking with the top-left pixel. Since none of our inputs will be clipping the boundaries, this eliminates the outer-boundary problem.

(For those who don't know, bwboundaries will count the surrounding boundary of the image as a section as well, since it includes holes).