Celtic Robotics members
Scouting
Record what you learn about other teams at an event: talk to them in their pit, and watch their matches. Everything is pooled and sorted on the Teams tab, ready for match planning and alliance selection. Only our own team members can see this page.
Click a column heading to sort. Click a team for everything we know about it.
Scouted averages come from our match scouting. Reliable is the share of watched matches with no breakdown, tip-over or lost connection. OPR is FTCScout's estimate from official scores (without fouls), shown once the event has matches.
The schedule and results come from FTCScout, which copies them from FTC Events within a few minutes. During the event this page checks for updates every two minutes. Press Plan to see what we know about the four robots in a match.
| Match | Time | Red | Blue | Score |
|---|
Two kinds of scouting
Pit scouting means visiting a team in their pit and asking about their robot: what it can do, how it drives, what it does in autonomous. Match scouting means watching their matches and recording what actually happened. Pit answers tell us what a robot can do; matches tell us what it does. When they disagree, trust the matches.
Visiting a pit
- Best time: before qualification matches start, while teams are setting up and getting inspected. After that, go during gaps when they aren't queuing or about to play.
- Wait to catch someone's eye, say who you are and which team you're from, and ask if now is a good time. If they're fixing something, come back later.
- Keep it to three to five minutes and thank them. Ask before taking a photo of their robot.
- Be ready to answer the same questions about our robots honestly. Gracious Professionalism works both ways.
- Late in the day, revisit teams we're interested in and ask kindly whether anything has broken or changed.
Watching matches
- Each scout watches one robot for the whole match. With four scouts, one per robot; with fewer, pick the robots that matter most.
- Tap the counters as things happen, then fill in the rest straight after the match while it's fresh.
- Write comments about the robot, never about students. Assume the other team might read them.
What we're looking for
- Reliability first. FTC alliances are two robots with no backups, so a partner that breaks down loses the match.
- A repeatable autonomous: LEAVE, launching into the CELL, PARK.
- Launching into the CELL: HIVE TIPS are worth 20 points each and drive both POLLINATOR ranking points.
- LEAVE and PARK in auto and at the end: together they decide the SWARM ranking point.
- Endgame FLOWER play, and whether their style fits ours, so two robots aren't fighting for the same job.
What we're looking for
- Reliability first. FTC alliances are two robots with no backups, so a partner that breaks down loses the match.
- A repeatable autonomous: LEAVE, launching the preloaded artifacts, and ideally collecting more from the spike marks.
- Artifacts scored: classified artifacts are 3 points each, and 36 through the square earns the Goal ranking point.
- Motif order and the gate: pattern points need artifacts on the ramp in motif order, and emptying the ramp through the gate makes room for more.
- LEAVE and base: together they decide the Movement ranking point (16 points).
Alliance selection
At FTC events, the top-ranked teams each invite one partner, in ranking order, a few minutes after the last qualification match. Rankings aren't a pick list: use the Teams tab, sorted by what matters to us, and the Pick tags (first pick, good partner, avoid) to build our list during the day. Only one or two named people should speak to other teams about alliance selection.
Game details are from each season's Competition Manual. Check the latest Team Update for any rule changes.