View Single Post
  #68   Spotlight this post!  
Unread 26-04-2015, 22:16
Goldenspeedster's Avatar
Goldenspeedster Goldenspeedster is offline
Registered User
AKA: Patrick Ubelhor
FRC #2338 (Gear It Forward)
Team Role: Programmer
 
Join Date: Feb 2013
Rookie Year: 2013
Location: Aurora, Illinois
Posts: 5
Goldenspeedster is on a distinguished road
Re: 2015 Lessons Learned: The Negative

Quote:
Originally Posted by Anupam Goli View Post
This is not true at all. Driver control is only so useful. Lots of teams take advantage of sensors to automate stacking and scoring routines, feedback control is very useful in giving a smooth driving experience, and providing an easy to use interface for the drivers to use is essential for top teams.
Even still, semi-autonomous actions only get so complex. 90% of the time spent making a PID loop is really just tuning three variables, since it's not even a dozen lines of code (using WPIlib, that is). I would agree that programming needs more emphasis, seeing as autonomous is the one time programmers get to take risks. I also think some of the point values were a bit low. Only 8 points for a container set?

Autonomous in 2013 and 2014, in my opinion, were nearly satisfactory, but a bit more complexity might be nice.

Quote:
Originally Posted by Chris is me View Post
The tournament structure, specifically average scores with no forgiveness for any mistakes, was atrocious. It's robotics - things go wrong. Consistency should be important, but if the first second of the first match can make your entire elimination run completely worthless, something needs to change. I never want to see the morale of a team so quickly killed again. I never want to have to make students play a match that they know is utterly pointless again. This must not be the new norm.
Although this may be true for quarterfinals, you should take a look at the 1st alliance in semifinals on Archimedes: Semis 2, 4, and 6

Last edited by Goldenspeedster : 26-04-2015 at 22:28.
Reply With Quote