It’s 2024. Stop have your scouts select whether or not a robot moved in auto. The API provides us this data, and even a Schmo like me is able to figure out how to access it.
For the thirdyear, ScoutLess will provide per-robot data made available in the FIRST API to you in a Google Sheet.
Included Data
For 2024, the following per robot data points are available in the API and will be surfaced in ScoutLess:
Robot Leave in Auto: Yes/No
Robot Endgame: Left/Right/Center/Park/No
What’s not included
Actual game piece data (this is not counted per-robot, so the extent that this data would be useful would be for some sort of component OPR calculation – others do that better than me).
Whether scores are awarded as the result of a penalty (all I can do is report what the refs enter).
Whether a robot showed up to a match, stopped moving during a match, etc.
The quality of the robot.
The point of this…
Is that you will stop making your scouts collect data they don’t have to
AND
For you to take this stupidly simple spreadsheet and expand on it. It’s really easy to copy and paste my methods into your own system, or for you to bring your other data in here, to have a single pane of glass.
There is A LOT of great data out there, both collected by teams and provided from official (FIRST) and community (TBA, Statbotics, etc.) sources. I encourage you to explore what’s out there and decide what’s best for your team.
Usage instructions
IMPORTANT:
This has not yet been tested with 2024 data since there have been no official events.
There are likely to be some changes after the official Week0 event this weekend. These changes could range from minor cosmetic ones to the sheet being completely nonfunctional during week0.
It is recommended that you either wait to make a copy until after I release a post-week0 update or you not take the results seriously and replace your copy later.
1. Make a copy of the spreadsheet using a Google account
4. Click authenticate API (you’ll only need to do this once per copy, per account). You will see some popups about an app from an unidentified developer. Click links to proceed (labeled “unsafe” – it’s not, I promise, and you can check!) and authorize.
How much do you trust the data that is team-based? I knew in 2022 my team wanted to track if the robot left the starting area with TBA but found that FMS would not give the right robot credit but rathered cared that the right amount of robots got credit. With this being a potential problem my team tends only to use TBA for alliance data.
Good morning and happy Week0! I’m pleased to share that ScoutLess mostly works as pre-released a few days ago.
In typical Jared fashion, the complicated API stuff was all doing exactly what it needed to do, but two of the columns were missing the formula that totals them. This is fixed now!
Go and head and make a copy, try it with some 2024week0 data, and get ready for your events!
Have fun, teams!
And of course, please let me know if I missed anything else not doing what it’s supposed to do.
I would also like to ask about the refresh constantly button. I’m not quite sure how it works, or I’m not waiting long enough? Could you explain it a little bit more in depth.
