![]() |
Re: Drive Team
We are not taking the technical specialties of our drive team into account when choosing the drive team. We always use a student as coach - who we chose early. He's been mentored all fall in the fundamentals of strategy and we've worked to show ways those fundamentals have applied in the past to FRC games. He's been involved intimately in the design of the robot from the beginning and has been the primary "rules" student. He's spending lots of time on YouTube and Chief Delphi learning all he can about this year's game.
WE are in the process of choosing the rest of the drive team. All active students can apply. They first must show a full knowledge of the rules by taking a test. Thereafter, we choose six to "train" daily as drivers. Of those six, we'll choose three to join the coach. |
Re: Drive Team
Our team decided to not have the students from last year pilot the robot again this year because they are seniors, but nobody seems to be interested in actually driving this thing.
I usually spend my time in robotics reading what other people's strategies are and forming my own from reading the rules, and help out with electrical and programming. |
Re: Drive Team
In #383 the drive team is independent of other team positions. We try to find the most talented driver, and after that the guys that work better with that driver...
As last year (2015 TBD): *driver - electric *"operator" - mechanical *human player - mechanical *coach - electric |
Re: Drive Team
IMHO, in addition to having a proper mindset (very important), a complete understanding of all the rules of the game, and experience, a Drive Team should have:
-someone who knows the robot inside and out and can improvise on the spot, in terms of mechanical/electrical fixes -someone who knows the software/control system inside an out, and can readily diagnose and fix most FMS/software problems. |
Re: Drive Team
We take a pretty simple approach to choosing a driver. We take our practice robot, set up some trials on a mock field, and see who does the best. Whatever age or background that person has, they become the driver. Driving is so important, so we're not going to not choose the best person simply to add diversity to the drive team.
That being said, here is where our drive team currently stands: Driver: Mechanical Co-Pilot: Software Human player: Mechanical Coach: Strategy Lead (Student) |
Re: Drive Team
Our drive team last year was two builders (HP and gunner), a programmer (driver), and a programming mentor as drive coach.
This year it's shaping up to be two programmers as driver/gunner, the same mentor, and a student from the build side (or maybe media? Who knows) as HP. |
Re: Drive Team
Our team has driver tryouts and usually the best candidate gets the position.
We have requirements though to tryout. You have to be able to attend all competitions (which means keeping your grades up) and you have to have been a contributing member of your subteam. No showing up just to drive. The other requirement is knowing how the robot works (this can be learned after you have been chosen as a member of the drive team). But if you need a quick fix before a match starts, someone on the drive team needs to know what to do. Our drive coach as always been an adult, at least for regular season events. |
Re: Drive Team
last year our drive team was:
Driver: Junior Designer Co-Driver: Senior Electrical Lead HP: Sophomore Strategy/Scouting Lead Coach: Junior Programmer Driver alt: Sophomore Programmer Co-driver alt: Freshman Build Team We base who drives primarily on a written rules test that is timed and observed. We want drive team that knows the rules not a drive team that needs to think about the rules. We also test drivers with the robot and hp with their tasks. The coach is more or less subjected to a psych evaluation to see how they will interact with other coach's and how well they can orate commands and make snap decisions. The coach must also be able to complete a task without getting tunnel vision to the task. Our drive team are typically the "die hard" students whom have the most hours in at the build site as well. Evaluation and testing have given us good/unbiased results for picking a drive team over the past 5 years. Once together its important to practice, practice, practice. we also make the drive team sit/eat/ride together at team functions so that they get familiar with each other. |
Re: Drive Team
Our driving team consisted of the following last competition:
1st Driver: CAD/Mechanical 2nd Driver: Mechanical (myself) Human Player: Team member Coach: Mentor As a rule of thumb, the 1st (main) driver is always the captain. The 2nd driver is someone who knows the robot inside and out, can instruct the driver through strategy, and acts as a second pair of eyes. The human player is typically a non-specialized team member that showed extraordinary worth that year. On our team, the coach does strategy, but on a more broad basis than the second driver. |
I find it interesting that we all seem to be level on the idea of crashing robots out of durability...
Guess my mindset is a bit off, on the field I expect them to do their best to try their hardest to give it everything. Last year shoving was okay and I approved of it but I would absolutely chew out a driver when the driving was overly aggressive. So a random crash not okay no spite no hate.. just competition. That being said there are certain lines that I take as courtesy when competing. If a robot is dead on the field you don't kick em while they are down... Rivalries are what we have on field, refreshments and relaxation time is what we have off of it. |
Re: Drive Team
Quote:
|
Quote:
|
Re: Drive Team
It is my belief that the drive team should consist of the people who have earned it the most over the build season and over the years. These are the people who have logged the most hours in the shop and are on task and most productive. It is viewed as a privilege for our most dedicated members. Of course, their ability to drive the robot well is important too.
Edit: my point is that it does not matter where they come from |
Re: Drive Team
I'm the Captain of the "Robot"side of the team. The robot side consists of Design, drive train, fabrication, electrical, programming, and anything else that is directly part of the robot.
Last year we held driver try outs and we chose the following drive team to start. Driver= Field build captain Operator= Programming Captain Commander= "Robot/Pit Captain" (me) Human Player= Our crazy Ginger Field Build member After the first two matches at our regional we made a change to the drive team after unsuccessful matches due to driver error. The new Drive team was as follows Driver= "Robot/Pit Captain" (me) Operator= Chasis/Drivetrain Captain Commander= Design Captain Human Player= Our crazy Ginger Field Build member Due to graduations and additions to the team this year, my best guess for this years drive team will be as follows Driver= "Robot/Pit Captain" (me) Operator= Team Co-Captain Commander= Programmer/rules expert Human Player= Our crazy Ginger Field Build member |
Re: Drive Team
Our 2 drivers have been from Programming and Electronics for a while. Drive team coach is usually one of our Systems Engineers.
|
| 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