Scouting program in the works, need ideas!

[Sean Raia]

Originally Posted by Bomberofdoom

Before I jump in to the advanced stuff, I think you need to have more control/list boxes for Ball control (including shooting and possesing/herding mechanisim), Drive train (Mecanum, six-wheel drive, SPIRIT etc...), and End-game (Hanging mechanisim, suspension mechanisim (what allows other robots to hang on him)).

In order to store information the information in a database - I say SQL FTW, if you're into it.

Last year, I wrote my own "database" for my (first) scouting application, including serializing the info into byte-size code and saving them into text files which were later deserialized etc...

I'd sugest having two main databases - One is for general information about the team and the robot (usually information gathered in the practice days, about what mechanisims are built into the robot), the second being information about robot preformance in every match.

Eventually, information for tactics for upcoming games need to be given to the drive team very quickly, for the intervals between games are quite short. Having your scouting system having an automated analasyis-of-information system will allow you to give a summarized version of the teams preformance.

But as I see your current application state, I'd say this is an addition you could work on after you've done with the basics.

EDIT: Also for elimination (or even for the quals) - put a "Role" indicator, where you write you analysis about the team's ability to play a certain role in the field (defense, mid-field, scorer, lifter etc..)

Thanks for the ideas, i think i will make a small addition that tells you which team is the best and a little about their robot. Although using excel for the read out is possible... im still going to add my own little comparison feature so it can run without excel.