|
One problem with scouting is that, I think, modularity may conflict with some stuff. Like you have 'ability to go under bar' or something. Well...what if they add/remove something that stops them from going under the bar. Maybe change it to Yes|No|Sometimes.
---
HP: 1 stack, 2 stack, 3 stack, 4 stack
AP: Nothing, Under bar to defend, search and distroy stacks, knock down wall (If they do go to knock down the wall, we should have a field saying if they knocked it down first, or if the other alliance knocked it down first)
CP: Defended stacks, stacked bins, knocked down stacks, stole bins, sat on platform, little/nothing
---
I don't quite understand what you're doing with HP...by saying 'stack', do you mean how many bins in a stack? or how many stacks? If the first, you can have 8 bins in a stack, if the latter, you can have 8 boxes not in a stack.
For AP, you could add something like 'prepare'...I'd imagine that there may be some teams who seem to do nothing but position themselves to be in an ideal places.... Maybe I'm stretching.
You could also add 'remove boxes from field' Quite possibly a robot could be designed just for that purpose.
Drivetrain knowledge is also nice. 2wd or 4wd?
Add 'dead reckoning' or whatever to sensors. And possibly a rating on how well their Autonomous mode works.
Does it look like it could get DQ'd by anything?
Durability is also nice to know. Most people can get an idea after looking at it in practice. I've seen robots that say they can do everything (and probably can)...but they tip over before they have the chance to. Also...how well does the bot take hits?
Just a list of ideas of changes/additions. There's way too much to include on a scouting form, but I'm just throwing out some ideas to see if anyone else finds importance in them.
__________________
I'm a professional web developer. I'm good with PHP, Perl, Java/JSP, some RoR, XML, Javascript (AJAX as well), (x)HTML, CSS, etc.. Validated code is good; fully cross-browser code is better (you comply to your users and the software they use, not the other way around. Sorry!)
|