Programming Master Task List

Task	Assigned To	Description
Test Ball_Manipulator Class	Calvin	Test on the real robot once controls and robot are built.
Debug outputs, sensors	Cristian	Need to add debugging output based on DS inputs.  One button debugs one (or one small set of) sensors by printing useful information (decoder ticks, revolutions per min, etc).  Use unused drive joystick buttons (on the base only) or spare toggle switches.  If we run out, use a spare toggle switch to enact "debug" mode and change the meaning of other inputs.
Explore use of the camera	-	End goal: get camera to track either our own trailer colors or the opposition trailer colors (we want both to work eventually). Start by looking at the examples. Once you are familiar with the examples, try integrating the relevant classes into our code.
Field control system	-	Develop a graphical application for controlling the field for Rally (does not use robot code, obviously! we'll be doing this probably in Java).
Mouse Interaction	-	After the mouse electronics are explored, if we need any sort of driver class, write one. Either way, a class should be written to track movement, providing meaningful X-Y movement in normal distance measurements (inches, feet, etc -- NOT ticks).
Autonomous: bump our empty trailer	-	If one of our alliance partners doesn't show, we want to be able to move their trailer out of the way of the nearby enemy payload specialist.