|
Re: Drive Team
Our drive team consists of whoever can drive the robot the best in an overall scenario. This past year I (programming lead) ended up driving the manipulator because I had so much experience when I automated the processes for it. And when in eliminations our batteries slowly became less powerful (we only have 6 chargers) it was extremely helpful because i knew the manual overrides like the back of my hand, and anyone else would not have had much experience with the process needed to manually run the fire sequence.
Our driver (we call the drive train operator the driver) was the lead mechanic, because at the end of a long day, it would often be the two of us left in the shop with one mentor, and while I was rebuilding and deploying code, he would run the robot through its paces and developed a strong chemistry with me controlling the manipulator.
Overall, the best drive team is the one that works together seamlessly. Our mentor who coaches every year commented to us this year that we were one of the quietest drive teams he remembers, because other than me calling out defensive targets, we were so used to working together that we rarely had a need to talk, it was running the motions over and over. We worked together as one, and however you can make this interaction is your best drive team.
__________________
I program a robot. Which means I write code and everyone gets mad at me when something doesn't work, even if I am the only one that knows it doesn't work. The key part to know is that the robot never works.
|