When we get around to actually setting our standard, we need to know what we should collect. Since it is XML, this is not set in stone, as we can add elements as time progresses.
Just to get ideas out there, start a list of things that we should be able to collect. Break them up into two categories, the robot itself, and what it does.
When you suggest something to watch, please also suggest how it should be measured (i.e. Yes\No, one through five, etc…)
I’d like to get a draft of the standard out by the end of the 2nd week of January, so everyone has time to get their databases and programs working before they are actually needed.
pick up boxes yes/no
go under the 14 inch bar yes/no
speed (ft/sec, or maybe on 1-5 scale)
can dominate the top yes/no (or maybe how effective from 1-5)
has a transmission system yes/no
power of robot (scale of 1-5)
attack/defense capabilities of the robot (1-5, or maybe what % of the time they attack/stack, and what % they defend the stack)
reliability (does this robot go out every time and work?–probably measured in number of “failure” times)
besides the robot, you might also want to keep this in mind
friendliness (will they agree with you, or are they bossy and want their own ideas-- yes/no)
driver abilities (1-5, does the driver look like he/she is well prepared?)
finally, give it on a scale of 1-5 or 1-10 how well you think that team is
you might want to add something about autonomous behaviors, special subsystems they might have, and even something about appearance (in case you want to ally with this robot in the finals and you don’t have all the info you need to find it…maybe missing a team number or something…)
Good ideas all. Could you continue posting your ideas in the offical Scouting Standard forum? - Things decided in there will be what data is collected / how it is collected.