Quote:
Originally Posted by A_Welsh
Thanks for looking into it!
We set out to create a Scouting System that would eliminate the use of a printer (as the one we currently had took approximately 6 minutes per page, give or take), and would process the information automatically so as not to require constant updating. Last year's model (for lack of a better term) was able to be run by about two people, and the version we're testing requires.... ehhh, let's say half a scouter, in addition to, you know, the people inputting data. But back to the point; we developed it to "harvest" data from a comglomerate of teams in order to produce the most accurate reports possible for each team. The client end is completely customizable both in terms of how our codes work, as well as being open-source, thus letting other teams build upon what we created to better suit your team.
About the wireless access, what we did was tether our cellphones to laptops via charging cable, and set the connection to USB only, so as not to produce the illegal public wi-fi network.
Hopefully this cleared everything up, if not, I'm open to all questions, comments, concerns, scrutiny and the like.
-A_Welsh
|
Seems like you've created something explicitly tailored to your team, which is exactly what you should do when doing something like this. I'd like to hear what advantages your scouting system had over ours:
We used a custom created app that ran on windows and mac, built by our head mentor. We decided to put the limitation in that one laptop was scouting one team on the field. We'd download the schedule from TBA the morning of, and then store it offline. We hand out the schedule in a database through flash drives to the four teams we were scouting teams (school district alliance). We'd have shifts of 5-10 matches of six scouters, and then we'd export the data to a flash drive for the main scouting computer. This had the advantage of not having clumsy USB cables running to each device, and since we all already had plethora of not-quite-powerful-enough computers for programming due to a district grant, this worked great. The app, in the end, didn't work as well for us due to some bugs, but the general concept worked great.
You've said that you intend to implement multi-conglomerate team scouting. How do you plan on keeping the data flowing smoothly throughout these teams, especially if the stands don't allow them to sit nearby each other?
Also, some more videos, pictures, or more proof of concepts would be great. This all sounds great on paper, but I'd love a video of a demo. Also, I don't plan on using this long term. I appreciate what you guys are doing here, trying to extend the ability to scout for everyone, but we've already developed our own. If that changes your answers, then be it. I hope our experiences of our two teams can change our two scouting systems for the better.