Quote:
Originally Posted by Mr V
Kinnect, it essentially made the GDC look as if they were for sale. On a related note the Innovation in control award which at least at the events I attended was based on being the only team using the Kinnect.
|
At VCU the Innovaction in Control award went to the only team to get Vision Tracking working due to the magnificently bright advertisements on the arena's walls. How did they do it? They went to the fender and made some lights blink based upon Vision Tracking status. It wasn't automated aiming at all :/ I only know because I asked them how they were able to get vision tracking working with the lights behind the field.
That brings up something that's kind of irked me for a couple of years.
Judges could CARE LESS if the programmers on a team built a custom display app out of Java or C++ that displays data to the drivers. They either dismiss is as "oh, anyone can build a web page" or "the driver's display means your stuff isn't automated". What a load of crap.
Building a Java app with a custom layout tailored for the drivers is the closest thing a team will get to a full software development cycle in FRC (including Systems Engineering, Coding, I&T phases). It also requires some technical prowess to debug things in order to ensure the system runs smoothly while on the field. It's also more realistic since there isn't a single automated
dynamic interactive system in the world that doesn't have some sort of human-in-the-loop control. Eventually our second driver will move solely to the app on a touchscreen panel when open-architecture tablets become reasonably priced. Maybe then the judges will think something of it
