I’ve been testing my C++/HTML/JavaScript/CSS/design capabilities to make one excessively powerful scouting system, thus, names ÜberScout](https://github.com/yash101/UberScout). It’s been chugging along rather quickly. I now need to know about what is needed.
My scouting platform is rather scalable. It uses the filesystem for the database, and is designed for cross-platform usage, though the Windows-specific code will be checked at the end of the basic platform design.
Since I am using the filesystem, I can store a lot of different things, such as images, videos and much more.
Now, comes the critical question – What is needed? What should I create vanilla implementations for?
I have planned the following things so far:
Scores
Robot Features
Starting Position
Shooting/Scoring Position (subject to change as the game is released)
Graph-based team side-by-side comparison
The platform is still incomplete and only supports team listing, addition and deletion. I have a demo here, which illustrates what has been accomplished so far.
You can’t rely upon having internet access at competitions. I think this is designed to run a local server over a small wired network, then connect to it via web browsers.
Precisely. That’s why I give the source code to compile, and hopefully binaries in the future.
I have been to only one competition where there was a school WiFi router in the library across the hall from our pit. It was, too, slow.
This application is also to test the limits of what can be done with scouting, and make real-time comparison fun, instead of tiring, cumbersome and difficult!
Also, note that the entire installation is automated, except the creation of the assets folder. I may work on a way for the server to automatically download the assets from my server. The entire web interface is about 2 MiB of code.
I started building something like this right before state competitions last year, then abandoned it when the robot code called for help. You can see the incomplete version here: http://flatmountainscout.appspot.com. Fyi the login system is not connected to anything, so you can do whatever you want with it.
It runs from a google app-engine server, which has a development server you can run locally. The eventual goal was to have some laptops networked together for scouters, with one server, but then be able to export all of the data to a flash drive. You would then run the flash drive back to another server setup in the pits and import the data there. It would also have the ability to export to the web version, and import from tba, if internet were available.
After reading through this thread, I believe one essential feature to add would be an automated export capability so that say your team has a VPS of some sort. When you get back to the hotel, you just type in a command or push a button and the entire database will be packed up and sent to the server. I can see how that won’t be much more than some ZLib magic
Note that the link that’s above is actually linked to my VPS. It provides many cloud features that are unbeatable, especially the fact that you can run any application that you want without asking the provider
