![]() |
Scouting Sheets- 5099
Hi guys,
I was wondering if there was any other questions I should be asking in these scouting sheets. The balls appear to be pretty subjective to scout this year. Any questions or comments, let me know. https://docs.google.com/document/d/1...it?usp=sharing https://docs.google.com/document/d/1...it?usp=sharing Thanks, G |
Re: Scouting Sheets- 5099
I would rethink some of your pit scouting.
EDIT: Also, I just noticed, on the match scouting sheet, I noticed that you asked for the match score. This can be very easily obtained from the FRC Events API or The Blue Alliance API. If you're inputting data to a spreadsheet, you can automatically pull that data into the sheet. |
Re: Scouting Sheets- 5099
If you're going to question accuracy you should just have it be a fill in the blank and have your scouters write down what the team says. No body is going to say "almost all of them" they are going to say 80%.
Same thing for your balls/sec. Your numbers are too low for this particular game. If you've followed any of the threads on CD you'll have noticed lots of teams are trying for somewhere between 10 and 20 balls/sec. Other notes: I like that you don't ask how many wheels the robot has. |
Re: Scouting Sheets- 5099
Here are my thoughts:
Note that by collecting so much objective scoring info via pit scouting, your data will likely fall prey to what I like to call the "pit scouting effect". People tend to remember what their robot can do, not what it typically does. I'm not saying they lie, it's just what they remember. Keep this in mind when analyzing pit scouting data. |
Re: Scouting Sheets- 5099
Hi I am a scout master from team 5431. I really like the things that you put on here, but I would add something to both. In both of the scouting forms, there should be a part for some qualitative data such as notes and other things. This allows your team to find out more about the team that the numbers alone don't tell. Also I would make the blanks smaller for the quantitative data as that does not need a lot of space. For the pit scouting, add things that have to do with the team such as the pit its self and the people in it. Also for this one, include instructions about asking the teams.
-Jeremy |
Re: Scouting Sheets- 5099
Quote:
And as Brian said, you really need to know where they load from. That will influence cycle times and defensive maneuvers. Adding a place for generic notes is crucial. If a scout notices something crazy cool or crazy bad they need a place to record it. |
Re: Scouting Sheets- 5099
Hey! Good start with the scouting sheets you put you :) The biggest suggestion I can make is that most of your questions are very broad and subjective qualitative points. For example, when you're talking accuracy (from your "Stands" scouting sheet), you divide it up into 3 categories: 1/4 of the shots, 1/2 of the shots, and almost all of the shots. Each of these categories is very unspecific. For example, your "almost all shots make it" could include robots that score 60%, 70%, 80% and so on of their shots, when in reality, these are very different levels of accuracy. Having more, specifically labeled options (say, 10% intervals) will allow you to group teams more effectively. That said, it is a tough question. The "how are we going to count balls" questions is one every team is asking; to which my best answer is "Do whatever you think your scouts can handle."
My second suggestion is for your pit scouting; the unfortunate truth of pit scouting is that most team's will not give you an accurate representation of their robot's ability. Because of this, I prefer to leave the qualitative, broad notes to pit scouting. I can't remember what our's has on it off the top of my head, but questions like "What kind of drive system do you have?", "Where can you acquire balls from?", or "What is your ball capacity?" were definitely in the discussion. Good luck with your scouting and at the competitions! If you're looking for any more input, shoot me a PM or something, I'm happy to help. |
| All times are GMT -5. The time now is 20:14. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi