[jajabinx124]

Originally Posted by evanperryg

Good qualitative data should explain how a team is doing something, their strengths and weaknesses, a unique, defining trait of the robot, etc. If that's what this scouter is doing, then odds are your aggregated info for most of the teams would look a little like this:
"bad bad bad bad bad bad bad bad bad bad bad"
which is hardly helpful at all.

Agreed. Watching a match and just saying that robot played terribly or bad isn't gonna be helpful. If you want a basis for comparison between 2 or more robots learn how summarize the match for the robot you are scouting(It's strengths, weaknesses, traits, etc. that you observed).

Here is an example of good qualitative data,

Team XXXX, Match XX

Auto: Attempted 3 tote stack in auto but failed
Teleop: Did coop, was fast at creating 2 non-capped stacks of 3 from the landfill area, stopped randomly and didn't move for the rest of the match

Our team has scouted quantitatively in the past, but recently we've been telling some of our more experienced scouts to scout qualitatively as well because we find qualitative data to be useful during strategy meetings(we find them useful because it provides another basis of comparison between teams after comparing teams regarding how they performed quantitatively, overall it's another topic to discuss about during our strategy meeting which makes our picklists stronger).