|
Re: Understaffed scouting
If nothing above works, then you could consider this reduction. I've never tried it, and I kind of just dreamed it up right now, but it might put you on the right track. It technically requires two people for the simplest form, but gets worthwhile with three.
Take a look at the scouting sheets being published for a single team and adapt them to a whole alliance. # of totes an alliance stacks, autonomous points for the whole alliance, total points of the whole alliance, litter thrown, etc. Then, you'd plug the data collected for one alliance into each robot on the alliance's individual sheet (in your data collection program), and get a very rough approximation. It's basically the same concept as OPR, but without calculation and being more specific than straight points. You wouldn't even need to make a system different from one for single robots, the data would just be bigger. You could see a general trend that "Oh, when team yyyy is on the field, the highest bin scored is generally higher." Like OPR, that trend might be totally off base, but you could see a trend and corroborate it with a "common sense check".
If you're not doing data entry, the drive team needs to come up to the stands and get the data themselves. You'll have to just stick everything in a binder, put the match schedule on front, and hope they can find what they're looking for. I can see some terrible times trying to deal with that at competition*. In other words, if you intend to do it this way, it looks like data entry will be almost essential.
* "Hey coach, let's go up to the binder and look through 100 matches to find some numbers on our two alliance partners for this last qualification match!" = Not Fun.
|