Glacier Peak Excel Data Main (1) Final.xlsx
Quote:
Originally Posted by *Rachelle*
We've considered using Tableau as well, it's actually on my laptop, I just haven't dedicated the time to learning it proficiently enough for competition use.
Not to mention we do not have enough students to have one specifically set on data input, I did it for two years and found that we could analyze the handwritten sheets much more effectively. It is mostly a tally system with a section for driver skill, so while we may not have the graphs, it is still quantitative.
My first question would be how long do your scouting night meetings generally take with the help of Tableau? Oftentimes when teams are talking about how they scout most efficiently I can't tell if efficient to them is 1, 3, or even 6 hours of hashing out the data.
Our current system in the last two years has been great for us, I'd be interested in seeing what your match scouting sheets look like as well. Would you mind sharing?
Congratulations on the win in Glacier Peak, those finals matches were fun to watch!
|
Hi Rachelle,
First of all, I'd like to say that we loved your team at Auburn. We were really bummed when we couldn't pick you, but even if you hadn't become a captain, you probably would have been snapped up well before it came to be our turn again. You were so fast, reliable, and a great defender. Good luck at your next competition!
I uploaded our Scouting Form and our Excel data from Glacier Peak. On the scouting form, the shooting location is on the left, the breaching,shooting, and end game information is in the middle, and the data entry column is on the right. Scouts fill in the middle and left sections, then rewrite their answers on the right, hopefully legibly, for ease of data entry.
The Excel data form includes all of our quantitative data from Glacier Peak. It does not include the qualitative data, which is handwritten. As always, I caution against using quantitative data only. It includes the majority of our information but doesn't completely account for driver skill, smart play, and other important variables. The qualitative data on your team bumped you up considerably on our lists - much more so than if we had just looked at quantitative data. Our analyst, Alli, is planning to fill all of the Excel boxes up with zero next time and our scouts will change the values when there is something to enter. You can upload our data into your own Tableau file to play around with it.
I would be happy to send you our Tableau packaged workbook from Glacier Peak so you can see what it looks like. I wasn't able to upload it here because it is the wrong file type. I could email it to you or your team if you'd like. It's a read-only, but you can make your own based on it.
You mentioned you do a handwritten tally/driver skill sort of data collection. This is what I use for qualitative information. I don't worry too much about getting all of the data - I do a rough approximation since we have quantitative data covered - but I write enough to remind myself of the robot capabilities. I focus on adding many one word comments such as "struggled, died, fast, smart, wandered, hit partner," etc. I think a handwritten approach like you discussed is a nice option for teams with limited scouting resources. You may miss some things, but you get the gist of it.
In terms of our scouting meetings/preliminary alliance selections after the first day of scouting: it takes us about two to three hours. While we could probably do it faster, my goal is to get my analyst team (4 veterans and 2 first-timers) to understand and think about the robots. Alliance selections is a much tougher task in my mind than match strategy. We make our lists first - top 24 of auto, shooting, breaching (static and manipulative defenses), challenge, scaling, defensive - and then go through each list, raising and lowering teams based on qualitative data. This takes the most time. Then we talk about who we would pick, who we would decline, who we want to lobby, and who is on our do not pick list. We also do mock drafts at that time, looking at likely seeding. We end the night by determining lobbying strategies and noting which robots we want to learn more about the next day. The next morning, we send our lobbying team out, we watch more robots and finalize their position, and make our final lists.
This is probably more information than you wanted but I am hoping others might find it helpful, too. Each team needs to do what works best for them and we are always looking to improve.
Good luck to you!
[ATTACH]
Glacier Peak Excel Data Main (1) Final.xlsx[/ATTACH]