started implementing virtual discovery, BUGS
VirtualRobot now instantiates a new MazeMap to give to the Robot element.  Added the hooks necessary to color walls differently depending on whether or not the in-maze robot has seen it.  Program segfaults at the beginning though which is a problem
stopped crashing, disabled flood fill
Flood fill cannot be calculated until all the walls have been found.  Therefore it cannot be calculated in the constructor of the VirtualRobot
getting closer, difference noticed
still doesn't render properly...
fixed the problem
turns out I was using the graphical X and Y positions instead of the row and column positions in the maze.  This could have caused a very annoying bug.
moved rotation_to_direction into MazeMap
this is more an inherent operation of the maze map itself than the robot.  I needed to use this function outside the Robot class so this makes sense
added hook for reading in raw sensor data
My current plan is that in the interrupt handler for data transmission, the information about adjacent walls will be saved into a global variable which will be used when doing the maze scan algorithm.  I currently don't see any reason to change this.
cleaned up Robot class
removed commented out code and old functions that aren't useful
mostly there, VirtualRobot plugs in MazeMap data
On the start of VirtualRobot::run(), "sensor data" from the real maze gets placed in the mazemap of the Robot struct....
closer.. malgo_explore_suggest return Rotation
This makes more sense because the algorithm will tell the robot which direction to turn instead of the absolute bering to go.  The robot_run() function makes sure to check that there is not a wall in front before moving.  In theory this could happen for the basic algorithms...
got proper right hand rul to work, BUGGY
still doesn't color the maze properly, guess I'll have to look into that one
changed invisible wall to .25f color
easier to tell the difference between discovered and undiscovered walls
removed Wall vector, draws fresh every time
Since the color needs to be updated anyways, it is just easier to rebuild teh geometry on every draw call.  Then, we can compare the mazeMap with the robotMazeMap on the spot.  This works!
added clarification comment
removed posHistory, added isExploring
isExploring will keep track of whether or not the robot is trying to explore the maze.  If this is true, it will run the exploration suggestion algorithm.  Otherwise, run flood fill.  When this changes, flood fill should be computed.
changed MazeMap elements to a WallState type
this allows an UNKNOWN state.  This is so we can scan if the robot has discovered all the walls
robot now yellow when exploring, red when solving
VirtualRobot checks the robot->isExploring flag when drawing
added sublime project files to gitignore
fixed crash bugs relating to WallState enum
Previous code assumed that these variables were bools but they aren't anymore!
fixed set_wall WallState bug, now correctly solves
When everything has been discovered, the robot will enter the solve state
now draws flood fill on exploration complete