Quote:
Originally Posted by Gregor
We have the exact same system. Lead scouting mentor and student come down and discuss with our drive team what our alliance should be doing. Time permitting, they come to the pre-match alliance meeting, but are normally quiet unless they drive coach misses something (which isn't uncommon, I miss things  ).
|
What I wouldn't give to have a scouting mentor...
Quote:
Originally Posted by Citrus Dad
Our system is similar. We wish we had it built by Week 4... 
|
It helps when one of your best programmers is spending ~75% of his time working on the app

Much of our data processing spreadsheets (now replaced by a combination of Access and Tableau, I'm going to post that eventually) were made by just changing some column titles.
Quote:
Originally Posted by Kevin Leonard
Smart strategy and scouting can take a weak robot and get it into eliminations.
Smart strategy and scouting can take a mediocre robot and make it a regional contender.
Smart strategy and scouting can take a decent robot and turn it into a regional lock.
Smart strategy and scouting can take a good robot and make it a sure bet to win a regional.
Smart strategy and scouting can take a great robot and bring it to einstein.
And smart strategy and scouting is essential for an elite robot to win a World Championship.
|
Quote:
Originally Posted by connor.worley
2nd round picks win worlds...
|
Nothing on CD has ever been this true.
Quote:
Originally Posted by jajabinx124
The definition of pit scouting in my book is asking teams questions about their robot that can't be answered through match scouting. Limit pit scouting to data your actually going to use(anything that can't be answered through match scouting) or in other words like you said, keep it simple(actual questions can be complex, but not redundant to what your match scouters are observing). Don't ask teams questions you can answer through match scouting because It'll be a waste of time and It'll be a pain on Friday night going through redundant pit scouting data.
|
I'll bite.
Having intensive pit scouting data can make filtering teams by their abilities easier, which is the only reason we still do extensive pit scouting. It has no other use besides giving us criteria to sort quantitative data by. Therefore, most questions we ask are either something they can't lie about (i.e. if they have can pullers, cause I'm standing in front of the robot and I can see if they have them) or something they wouldn't have a reason to lie about (their preferred starting position).
Quote:
Originally Posted by EricH
Just about any key data point that you could pick up in the pit--like the ones you mentioned--can also be picked up on the field,
|
Drivetrain type can be impossible to pick up on from matches, especially if you're trying to differentiate between a really bad swerve and a really good mecanum. Number of motors in drivetrain, another important one when you're looking for defensive bots. Weight, impossible to get from matches. Available autonomous modes, as opposed to your preferred auto mode. Whether a robot can upright a container.
Quote:
Originally Posted by Michael Hill
We also ask questions about what the intent of the robot (specifically worded to extract intent of the design). That way, we are able to juxtapose that with how they are doing (and if they are performing to expectations).
|
I'm not sure how that would give you an idea for how good a team actually is. Some teams have very low expectations, others have unreasonably high expectations.