2012 Scouting Form

[wilsonmagnet]

Attached is a draft of a scouting form for 2012 Rebound Rumble.

Feedback welcome.

Paul Daniels, Rochester Engineering Centre.

[EricLeifermann]

I like the top half of the sheet. I don't like the ranking system at the bottom as its very subjective and its hard enough to track all the stuff you want to know at the top of the page for 1 robot let alone try and watch all 6 robots to find which one is the best in those 6 or 7 categories you have.

I like to have the ability to have 3-4 matches per team on one sheet of paper so you don't end up with 150+ sheets of paper to try and decipher usable info from. I attached something from a previous year to show what I am talking about. In the attached file if we did it right we could get 6 matches per 1 side of paper for 1 robot...

[Zephyr Foxworth]

A couple questions:
A: Would each form be for one individual to use per match?

The form is asking for the scout to pay attention to a lot of details at once. While the first half asks for details of a single robot, the ranking would have required watching all robots at once during the match.

B: What is the purpose of the Court Map in the middle of the page?

I would interpret it to be location and reason for fouls, but you may have another answer to this.

[Basel A]

I agree with Eric in that you could probably fit more than one team-match onto one sheet. We've always done 3 per sheet, but it depends on how much data you're collecting.

Remember that your sheet should include all information you'll need for match strategy and alliance selection - and nothing else. I'm not sure why you'd need to know how many shots were scored on the right and left baskets instead of just the middle row. You may want to include both shots made and shot attempted; that'll give you a better idea of robot effectiveness. There's other examples, but I think you get the point.

Finally, the bottom section is entirely subjective. Objective data is simply more reliable. The section depends both on the scouter's opinion and the quality of the other robots in the match, neither of which have anything to do with the robot in question. In the end, that data probably won't be very useful.

P.S. Note that fouls will not be announced to the crowd; only technical fouls and cards will be.

[Wizzard of Izz]

May I suggest Cowscout? www.cowscout.com

[Wizzard of Izz]

This might be of use to you.
http://www.chiefdelphi.com/forums/sh...ad.php?t=96313

[mynameislenni]

no

[the_zanman]

Hey, I really like the scouting sheet - reminds me of the one my team used last year.

If you have any Android devices though, you may want to consider this in addition to this well-formatted form
http://www.chiefdelphi.com/forums/sh...d.php?t=101682

[Siri]

Originally Posted by Basel A

P.S. Note that fouls will not be announced to the crowd; only technical fouls and cards will be.

Yes and no--fouls will be signaled to the crowd, but not discussed/announced afterwards. And of course the score will change, but only after the signal is given. You'll definitely know if you're looking, but I am a little worried about my scouts catching them while watching the robot. This is challenge enough as a coach, and I've met may coaches who miss such things.

Also, you'll only be "told" which rule the foul is on for the "most common" fouls. Our at least our best guess at the most common fouls. The rest will take some deduction on the part of the scouts. Something to consider depending on the experience/knowledge/attentiveness of your scouts.


With regards to the rest of the sheet, I have to agree about including more than one match. Also, while your top information is mostly good to have, the format will not necessarily be easy for the scouts. Consider a more compact but distinctive block that minimizes writing for simple questions. Scouts will tend to "memorize" the layout in order to fill things out faster, and the series of "nnnnn_____" makes things run together a little more than is necessary.

The bottom section is still highly subjective and would require cross-referencing with the other robots in the match in many cases. (And even in the act of cross-referencing, you don't learn a whole lot.) It also puts another huge burden on the scouts in watching the other robots in the match as well, which will likely impact data quality. If you want to know more, you could leave a comments section or some descriptive adjectives to circle for each. Still, remember this is only really useful if your scouting team does well with subjectivity (some do, most don't).

[XaulZan11]

I always try to make my team's scouting sheets extremely easy to pick up and understand how to fill it out. I have some difficultly with what goes in some of your blanks (for example: Autonomous, Teleoperated, Adj. Angle, bump, bridge...). Some other things I would include are the match number and a space for general comments.

[ChristopherSD]

Here's my in-game sheet.

6 matches per side.

[Patrick Chiang]

We made a program for this. Attached screenshot.

Left dropdown box for allowing comparison of a team's autonomous vs. teleop / day 1 vs. day 2 / balance vs. shooting statistics. Right dropdown box allows sorting teams by 1 of the 23 possible options that we've implemented (Best middle basket shooter, best single balancer, most average points, most consistent team, best autonomous mode scorer...etc)

The current version (not on my computer) also has a grapher on the right that compares all the teams OR graphs a specific team's performance (also, another dropdown box to select from a number of options to compare by).

There will be a team of scouts (aka freshman and sophomores) going around and recording this stuff at the match. The recording sheet is very subjective and only about match data (which basket scored in which mode, total score, balancing...etc). (Our team's scouts subscribe to the belief that performance is key; a good looking robot in the pits =/= a good looking robot in the arena)

May release before competitions when we clean it up.

[wilsonmagnet]

Revised 2012 Scouting Form

[ChristopherSD]

Originally Posted by Patrick Chiang

We made a program for this. Attached screenshot.

Left dropdown box for allowing comparison of a team's autonomous vs. teleop / day 1 vs. day 2 / balance vs. shooting statistics. Right dropdown box allows sorting teams by 1 of the 23 possible options that we've implemented (Best middle basket shooter, best single balancer, most average points, most consistent team, best autonomous mode scorer...etc)

The current version (not on my computer) also has a grapher on the right that compares all the teams OR graphs a specific team's performance (also, another dropdown box to select from a number of options to compare by).

There will be a team of scouts (aka freshman and sophomores) going around and recording this stuff at the match. The recording sheet is very subjective and only about match data (which basket scored in which mode, total score, balancing...etc). (Our team's scouts subscribe to the belief that performance is key; a good looking robot in the pits =/= a good looking robot in the arena)

May release before competitions when we clean it up.

Please tell me this comes on Windows.

[EricLeifermann]

Why do you need to know where they take each shot? You want your scouters to be able to collect data fast and accurately. Having your scouters looking up and down from the field to the paper will decrease both. The less the scouters need to focus on the better the data you are going to get.

What you really want to know this year is

How many baskets scored
Any penalties
Did they balance on the bridge
Final score of match
did red or blue win
and a place for comments. Such as they only can only score while touching the fender, etc.

It doesn't matter what basket they score on. I am going to pick the robot that scores the most points. Do i want the robot who scores 100 balls on the low basket or the robot who scores 10 balls on the top basket?