|
As far as what data to collect it rely depends on next year's game but there's standard stuff:
Pitt Scouting:
- Team #
- Type of drive (2 whl, 4 whl, tank, crab, ...)
- Drive motors used
- info about transmission (have/don't, brake?, how many gears, ...)
- # of modules/attachments
- capabilities (ex. stack)
Match Scouting
- Team #
- Partner
- Opponents
- Match score
- QP score
- Other alliance's match score
- Other alliance's QP score
- If they won
- Speed
- Traction
- Evaluation of capabilities (ex. how well they stack)
If they have auto. next year
- What it does
- How well it works
With the match and QP scores you could just fill in the match scores and whether or not you won and let the QP score be a calculated field. Or you could just enter Alli he info.
I agree that evaluating capabilities gets very subjective. As said before just using # 1 to 5 doesn't work because one person's 5 may be another's 3. This year my team got around the number thing we had a list of choices N/A, not functioning, marginal, successful, and amazing. This worked pretty good but you couldn't average or total scores. So I've been thinking why not use percentages! They're universal a 90% in Michigan is the same as a 90% in California. Also, everyone knows what the numbers mean: 60's - below average/not working well, 70's - average/works, 80's above average/works great ... With percentages you need to explain the everyone knows what they mean, they're great!
Just my latest crazy idea
Lindsey
|