Quote:
Originally Posted by ATH1RSTYM00SE
Mostly to restate what other people have said in an organized list, this is what it seems like is the role of the analyst:
Watching the clock and shouting out times
Checking to make sure drivers don't incur penalties
Pointing out tubes that are at an odd angle for driver or coach to see
Hold signs up to direct feeder
Pass decisions on from teams in the alliance
Call out scores of yours or opposing teams
Make reassuring call-outs such as good job or nice hanging
Don't get in the way of anybody
and finally they could try to extract as much data on the other teams as they remember because they have an extremely good view of the field.
Feel free to add to the list if i missed something
|
I'd just like to add that you should really ask your alliance, especially coaches and Feeders pre-match which of these they'd find helpful. If they say they don't want help in a certain area, you're probably best-off leaving it alone, even if you think they need it mid-match. Feeders have it hard enough isolated cross-field without trying to interpret something you didn't discuss pre-match. Coaches also have a lot to watch, listen to, process and communicate, especially when something goes wrong, without trying to understand previously undiscussed help. (And drivers certainly have enough to process with just the one robot and one coach!)
As an example, I find most analysts know this--drivers usually have it intuitively and coaches tend to figure it out right quick--but I usually ask not to say anything that doesn't need to be said. No score calls except as discussed for strategy, usually none at all if we can see the screen, no time until when we asked for the minibot race, no robot-centric stuff ( pickup, alignment), no other call-outs.