View Single Post
  #4   Spotlight this post!  
Unread 23-01-2005, 16:26
jgannon's Avatar
jgannon jgannon is offline
I ᐸ3 Robots
AKA: Joey Gannon
no team
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Pittsburgh, PA
Posts: 1,467
jgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond repute
Re: Organizing a programming team.

Quote:
Originally Posted by scitobor 617
What exactly is the role of the tester? I normally test as I write.
So, I just wrote some new driving code. It has three modes of operation: pivot in place, go straight, or arc. Ideally, I write up the code, and someone reads through it to make sure that it makes sense. Then I compile it, and send it to the RC. Another person hooks up the OI, and tests the various operations to make sure that it works as intended, and that the controls are manageable. (When coding a control system, it often makes sense in your head, but comes out far too sensitive for the drivers.) Robot programming is not like computer programming, where you can instantly test little parts of code with some printf (or cout, or System.out.println, depending on your favorite flavor) commands on a console window. I've found that it's much more efficient to write large things all at once, because it's very time-consuming to compile the code, power up the robot, download the code with IFI Loader, and test the code. That's why it's nice to have someone else around to take over the whole process.
__________________
Team 1743 - The Short Circuits
2010 Pittsburgh Excellence in Design & Team Spirit Awards
2009 Pittsburgh Regional Champions (thanks to 222 and 1218)
2007 Pittsburgh Website Award
2006 Pittsburgh Regional Champions (thanks to 395 and 1038)
2006 Pittsburgh Rookie Inspiration & Highest Rookie Seed

Team 1388 - Eagle Robotics
2005 Sacramento Engineering Inspiration
2004 Curie Division Champions (thanks to 1038 and 175)
2004 Sacramento Rookie All-Star

_