Quote:
Originally Posted by Boltman
Best way to scout is "eyes on bots", excel sheets , pen and paper note taking. I use a cheap thin spiral binder and highlighters . My awesome scouts also take copious notes. I started the scouting department from scratch last year. Scouting is equal to engineering and drive team IMO and the entire team agrees with me they love it. Not only for winning games but building alliances to have the best chance at a win.
A field of 60 with 10-12 games is not indicative of a high level of need for data analysis and is highly susceptible to schedule pairings more than raw data from stats. Eyes first, notes second and data on first night to see if there are any you missed. Usually not the case...might be one or two but then you watch on day 2 and go "hmm wonder how they got that stat?" eyes don't lie like stats do.
I don't get alliance captains that don't already know their second picks instantly of a pick list, other than they must not scout at all and ultimately they exit in QF.
|
I could agree with the "eyes over stats" idea IF you have experienced scouts* that know what to look for and IF you have enough experienced scouts to get eyes on a majority of matches for every team. You realistically need at least four experienced scouts to literally watch 90% of matches. Since most FIRST teams do not have these resources, putting together a stats-based system (where any freshman can contribute) is best for most teams.
* By experienced scout, I mean a scout that can remember basic information about nearly all teams and put teams in tiers or rough picklist. In the roughly 10 years I've scouted, there are probably 3-5 students who I'd consider capable of doing this for an entire 60+ team event.