Quote:
Originally Posted by thatprogrammer
Thanks for the code release, some of the code is really nice! That said,I'm not following how your vision works. It appears your X and Y values are being fed to you by smartdashboard somehow (Is your operator manually entering the defense position they are on?).
|
Vision processing is done on the dashboard side (which was written in LabVIEW). It just uses the example vision code from NI.
It's not the prettiest code as it was a plan C backup after the JetsonTK1 (with power issues) and GRIP (which doesn't work for USB cameras), so I don't think we'll reuse it next year. Either way, I've attached it if you want to look at it.
Quote:
Originally Posted by TimTheGreat
You guys should take a look at autonomous selectors, just to get rid of clutter. You have everything neatly organized into classes, why not go that extra step and make each separate autonomous it's own class as well?
|
Agreed, this was my first year with Java in FRC, and the team's first year with FRC and Java in general, we'll definitely split auto into separate classes next season.
Quote:
|
Also, looking through some of your intake update method, it seems to always be running, since you don't have a stop mode. Am I reading this right? Seems a little dangerous.
|
The intake is stopped in the "has ball" state.