Re: The use of the Kinect and Cheesy Vision in 2015 and beyond
 

I'm not sure about that. I think the human control element allowed for nuances that were critical and could not have been incorporated into easily the auto routines.

Re: The use of the Kinect and Cheesy Vision in 2015 and beyond
 

We programmed our auto the same way 254 did, as a switch in the autocode for going left/right. We just used the kinect instead. We have done vision processing in the past; but looking at what was going on with the field and the way the vision sensors were placed, I'm glad we didn't.

If these systems are prohibited, then here's what we need:
(1) fields that operate as stated, the lights this year were significantly off. I don't know about the vision targets; but the yellow lights were routinely switching at 5.5 to 6 seconds or later. I don't know about other teams, but this was routinely causing our first ball in our two ball auto to be "early".

(2) Targets that are useful. We were considering using the lights around the goal over the vision targets due to their placement. With the kinect being available and so easy to implement, it became a no-brainer to use the mark 1 human eyeball. The vision targets this year were not in a good spot.

(3) An auto that eliminates the usefullness of having a human in the loop.