![]() |
Re: Drive Team
Our drive team consists of:
Build team co-captian Both team co-captians As well as a Programming member We are all well versed on electronics as well. |
Re: Drive Team
Quote:
|
Re: Drive Team
Here's the drive team for 1466:
driver 1 - senior team captain driver 2 - junior mechanical team member coach - senior team captain human player - random freshman AKA noodle jesus |
Re: Drive Team
the one position that began as an informal tradition about five years ago and is now almost a formal requirement is that the programming lead is the secondary driver. The reasoning behind this is that my coach wants to also have a programmer behind the glass, so he/she knows whats going on in the code if something goes wrong, and what better position to put him/her on than at control of all the safeties and overrides they built into it? I know that it's saved our butts on at least two counts, if not more.
But aside from that the human player is our manufacturing lead, and our main driver is our design and engineering lead, and our coach is an alumni/mentor. |
Re: Drive Team
Quote:
|
Re: Drive Team
I use a weighted table to choose positions on the team. Some of the considerations are time spent during build, time spent on the team in general, skill level, teamwork skills and initiative, and results of a rules/game test.
Our drive team is made up of the three students who put in (by far) the most time and effort on the team. They are also the build leader (driver), main programmer (operator), and Chairman's/business lead (human player.) The two drivers are the team captains. They have the most invested in the robot and the team and its performance; they also know the most about it. |
| All times are GMT -5. The time now is 15:26. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi