Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Rules/Strategy (http://www.chiefdelphi.com/forums/forumdisplay.php?f=6)
-   -   Good vs. Great Drive Teams (http://www.chiefdelphi.com/forums/showthread.php?t=98172)

IndySam 08-12-2011 21:42

Re: Good vs. Great Drive Teams
 
The one thing I don't see mentioned here is passion.

A good driver must have passion for the game and the sport. This is the most important thing I look for in a driver, second is dedication.

Andrew Lawrence 08-12-2011 21:42

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by IndySam (Post 1089695)
The one thing I don't see mentioned here is passion.

A good driver must have passion for the game and the sport. This is the most important thing I look for in a driver, second only to dedication.

I second that. "Passion for the game and the sport." Love it! :D

apalrd 08-12-2011 22:27

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by SuperNerd256 (Post 1089691)
Or if your team used vision to track the targets on top of the goals for targeted shots in 2010, it would be a lot easier to have your robot use its sensors to align itself, and use the distance away from the target to change the kicking power to ensure that every time you press the fire button, you get a for sure shot in the goal.

We looked at vision in 2009, 2010, and 2011. All three times, we looked far enough to decide we didn't like it:

-In 2009, we had so many issues with CPU load of using the camera that we just gave up because we had other problems to solve. By the end of the season, our Hotbot design didn't even have a turret or camera, and the problem became irrelevant.

-In 2010, we were still having lag issues, and it was hard to get a fast enough PID loop as the sensor was so slow. We supplemented it with a gyro, but eventually gave up because the driver was so much faster at alignment. And our operator got good enough (With a linearization algorithm for the kicker power) to set the kick distance correctly.

-In 2011, we gave up on the Axis cam almost immediately, once again due to lag, but attempted some tracking with the CMUcam from the 2005 KOP (the same one in the 2006 and 2007 KOP's). We got it at a decent framerate (I think we got something like 15 fps), but it was still slower than a driver so we saved the weight and complexity of making it work and just practiced more.

That said, we do all kinds of automation on the elevator system, handling state-transition and control loops to offload driver work. That kind of automation is great, as it can do something a driver can already do faster, but fixing something that is impossible to drive or doing vision tasks because they show you how in the default code isn't usually a good thing.

Andrew Lawrence 08-12-2011 22:30

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by apalrd (Post 1089704)
We looked at vision in 2009, 2010, and 2011. All three times, we looked far enough to decide we didn't like it:

-In 2009, we had so many issues with CPU load of using the camera that we just gave up because we had other problems to solve. By the end of the season, our Hotbot design didn't even have a turret or camera, and the problem became irrelevant.

-In 2010, we were still having lag issues, and it was hard to get a fast enough PID loop as the sensor was so slow. We supplemented it with a gyro, but eventually gave up because the driver was so much faster at alignment. And our operator got good enough (With a linearization algorithm for the kicker power) to set the kick distance correctly.

-In 2011, we gave up on the Axis cam almost immediately, once again due to lag, but attempted some tracking with the CMUcam from the 2005 KOP (the same one in the 2006 and 2007 KOP's). We got it at a decent framerate (I think we got something like 15 fps), but it was still slower than a driver so we saved the weight and complexity of making it work and just practiced more.

That said, we do all kinds of automation on the elevator system, handling state-transition and control loops to offload driver work. That kind of automation is great, as it can do something a driver can already do faster, but fixing something that is impossible to drive or doing vision tasks because they show you how in the default code isn't usually a good thing.

Well, never actually using the axis camera yet, I have to say thanks for telling me that! I was gonna try to use it this year. I've seen other teams successfully using vision. How do they do it?

apalrd 08-12-2011 23:04

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by SuperNerd256 (Post 1089705)
Well, never actually using the axis camera yet, I have to say thanks for telling me that! I was gonna try to use it this year. I've seen other teams successfully using vision. How do they do it?

I don't know.

We haven't found a pressing need to use vision since 2006 and 2007, where it was easy to use and didn't add a huge processing requirement.

smurfgirl 11-12-2011 11:22

Re: Good vs. Great Drive Teams
 
The most important aspect of a drive team that will make them successful is by far the amount of practice time they get. A great drive team has drivers that instinctively know how to do anything with their robot, without thinking about it. A great drive team acts as a set of four hands which get commands from one brain (the coach). It takes a lot of practice to make this happen. The more closely you can simulate a competition, the better - practice with loud music on, with old robots on the field (bonus - you also can get multiple people practice at once this way), and invite other teams over to practice with you if you can. Once operating the robot and strategy decisions become natural, your team will perform a lot better overall.

MysterE 11-12-2011 14:04

Re: Good vs. Great Drive Teams
 
I think this is one of the training areas that I am the most unsure of. How do you train a Drive Coach - or better yet - how can you train yourself to be the Drive Coach.

Chris is me 11-12-2011 14:08

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by MysterE (Post 1090185)
I think this is one of the training areas that I am the most unsure of. How do you train a Drive Coach - or better yet - how can you train yourself to be the Drive Coach.

Practice makes perfect!

A good candidate for a drive coach is a natural leader - they already have some of the key skills needed. After that, it's all about practice and experience, which takes awhile but will help tremendously.

plnyyanks 11-12-2011 15:06

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by Chris is me (Post 1090188)
Practice makes perfect!

Ditto. Watch lots of match videos, remember the type of game strategy you designed your robot to do, and practice as much as you humanly can.

Ninja_Bait 11-12-2011 15:08

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by Chris is me (Post 1090188)
Practice makes perfect!

A good candidate for a drive coach is a natural leader - they already have some of the key skills needed. After that, it's all about practice and experience, which takes awhile but will help tremendously.

Practice driving, too, so you know what you're talking about when you're not the one on the sticks.

Chris is me 11-12-2011 15:17

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by Ninja_Bait (Post 1090200)
Practice driving, too, so you know what you're talking about when you're not the one on the sticks.

Fun fact: It is impossible to get me to voluntarily give up the controls to our 2011 robot. :)

Gdeaver 11-12-2011 16:49

Re: Good vs. Great Drive Teams
 
The one most critical trait that I look for in a driver is situational awareness. Most drivers have a terrible case of myopia when it comes to driving in a FIRST competition. Let me try to explain. Most first games are highly dynamic and with 6 bots on the floor it tends to be very chaotic. The large majority of drivers I have worked with tend to lock on to their robot, the field piece and the chosen action they perceive to be the next choice for action. They do not perceive the rest of the field and the dynamic actions that are taking place. They are locked onto the current action and can not see or disconnect to take advantage of another opportunity that has suddenly presented it's self on the field outside of their narrowed field of vision. Then every once in awhile there is that one individual who has this perceptual brain functionality. Many times they are written off by the team because other drive candidates have better control finesse. Practice can make any individual a good driver from a control perspective. Situational awareness - I believe you are born that way. The real problem is that the dynamics that happen at a real competition can not be duplicated while practicing at home. We have tried having a second bot on the floor to play PITA to the primary bot. It doesn't come close to the real thing. Off season comps are are great time to search for this elusive person.

Andrew Lawrence 11-12-2011 17:28

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by Gdeaver (Post 1090210)
The one most critical trait that I look for in a driver is situational awareness...

I read this as situational awesomeness. :p

Drivencrazy 11-12-2011 21:46

Re: Good vs. Great Drive Teams
 
Quote:

Originally Posted by Gdeaver (Post 1090210)
The one most critical trait that I look for in a driver is situational awareness.

In my opinion it would be the coaches responsibility to have this situational awareness and it would be more important for the driver to have a cool head and the ability to execute maneuvers. I think the coach should be the one to pay attention to the field and give the driver instructions. If you have your driver look for scoring opportunities while also trying to do something else with the robot you will get mediocre results on both fronts.

Find a coach that knows the game, your strategy, and your robot's capabilities. And as far as the driver goes, practice practice practice. There is nothing that can make up for drive time. A driver with a good robot and a lot of practice can easily keep pace with a better robot and a driver with little practice.


All times are GMT -5. The time now is 09:43.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi