Hello everyone,
This is the Beta Version of our scouting spreadsheet for the 2017 STEAMWORKS game. If anyone finds any bugs or thinks of any improvements please share them in this thread.
It is designed to work at any regional or at the World Competition. Follow the directions given in the “Customization” tab.
Thanks!
https://drive.google.com/file/d/0B_6jpD4TeQ4wUzF5QkZKa3dyQnM/view?usp=sharing
This may be useful, however we cant figure out where this mystical “D” button is. And we keep getting and ERROR in J and U when we enter values. Any clarification would be appreciated. Thanks!
This is an awesome design! Looking forward to seeing what you add to this.
Certain things in the data entry form could be calculated by the spreadsheet though. Namely, “Nothing”,“Rotors Turning”,and “40 kpa”.
I believe the D column button only shows up if it is downloaded as an Excel Document. Try that 
As for the errors, the spreadsheet tests to see if each alliance has the same amount of various objectives that should be the same. For example, the number of Rotors Turning at the end of teleop (column T) should be the same for each robot in the alliance. So if T4, T5, and T6 are not equal it alerts the user as an error.
As for automating some of the data entry slots, for fuel, the idea behind not automating it is that it will be difficult to estimate the amount of fuel going into the boiler. Therefore it will be more reliable to insert that data in separately after the match is over instead of relying on estimations for Ranking Points.
Additionally, the number of rotors turning could be automated easily but I would personally prefer getting three numbers from three different scouters. If the three numbers are the same then the data is correct and if they are different then Blue Alliance can be consulted. Meanwhile totaling three different robot’s gear totals leaves more room for error on the scouting end. If one gear total is incorrect then that can alter a teams’ ranking drastically in the spreadsheet.
I hope I addressed all questions and comments. Thank you all for your support and advice!
As for automating some of the data entry slots, for fuel, the idea behind not automating it is that it will be difficult to estimate the amount of fuel going into the boiler. Therefore it will be more reliable to insert that data in separately after the match is over instead of relying on estimations for Ranking Points.
Oh, well that brings up two questions.
Why does it matter if an alliance reaches 40kpa if you’re evaluating individual robot performance?
Why are you going to have your scouts write down match result information, and then record that information into your sheet 3 times per alliance? Copying match from TBA is 2 clicks and a drag away.
To be clear, from Kpa and rotors turning you’re adding ~1000 data points to data entry for ~360 points of data.
I agree that not including things like rotors and kPa could save time and effort - especially since those things may not be completely tabulated until the end of the match (I know theoretically, but in the past it has not always worked out that way), and then that can leave scouts scrambling to set up for their next team. That data can be pulled from TBA if you need it, but I’m not sure why you would.
In terms of why you need your data, how do you actually use the information here? At least personally, with alliance selection, I care a lot more about unique characteristics: in Steamworks, this could be having a great intake or picking up a gear. Have you thought about including those stats? If you have, why did you choose not to include them? It does look great, I’m just curious.
Great questions and conversation is happening here.
Good points about the 40 kPa and the Rotors Turning. Either could be automated or eliminated at a team’s preference. The idea behind having them is to evaluate the consistency of a robot getting 40 kPa. Fuel, by itself, isn’t worth many points so having the % of matches a team reaches the 40 kPa mark would be useful information (since it is worth extra points in Eliminations).
As for including robot qualities (example: having a good intake), this spreadsheet is intended for what KING TeC refers to as Quantitative Scouting. We also do Qualitative Scouting (notes on robot quality, driver performance, etc.) and Pit Scouting.
The intended use of this sheet is to give teams easy data to be able to compare various robots throughout a competition on a variety of tasks using numbers alone.