View Single Post
  #12   Spotlight this post!  
Unread 01-03-2008, 18:38
TheOtherGuy's Avatar
TheOtherGuy TheOtherGuy is offline
Unregistered User
AKA: Kevin Forbes
FRC #4183 (Bit Buckets)
Team Role: Engineer
 
Join Date: Jul 2006
Rookie Year: 2006
Location: Tucson, AZ
Posts: 408
TheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond repute
Re: NDS Overdrive Scouting System

Hmm.. Interesting! I've heard from several people that making a program that lists the best robots would be useful. I'm not too deep into programming with C++, but if I work at it, I may be able to make a program like this.

I was thinking along the lines of a program where you insert the data in a formatted way into a text file which you place on the root of the SD card. When you open the program, you can sort the data by team # and select certain teams that you could then view the data of. It would also be nice to be able to sort the teams depending on certain criteria, such as best hurdler, best lap runner, etc. Only thing is, this can already be done in Excel.

So it would be nice if this thread was put to use and people explained how they would use the DS and what benefits they would get from using it. I've heard of pit scouting, alliance selection, etc., and it would be nice if people expanded on their suggestions. I'm also trying to think of a way to scout several robots at once, reducing the number of DSs required for scouting (because I know some teams don't happen to have 6 DSs lying around!), and if anyone has an idea on how to do this, it would be greatly appreciated!

If there's anything you can do to help, that would be great! I was planning on making an API so teams could simply create their own programs. This API would have screen and data handling capabilities, including (hopefully) text input, buttons, checkboxes, etc. You would simply include a library and work from there.

So, we'll see where this goes. I'm sure by next year we can have something that is flexible and modular and suits many teams' needs!
__________________

Last edited by TheOtherGuy : 01-03-2008 at 18:40.