Your dream strategy system

Hi:)

As we work on developing our scouting and strategy systems for the upcoming season, I’d love to hear your insights!

What are the features you’ve always wanted in a scouting or strategy system? Or, if you’ve developed your own system, what game-changing features have you included?

If you haven’t created a system yourself, what features in the systems you’ve used have stood out as particularly useful or impactful?

Thanks!

1 Like

The biggest game-changing feature I’ve seen is Lovat’s path viewer. A nice feature i like is included match scouter scheduling; it prevents two scouters from watching the same robot.

4 Likes

So if we really are going for DREAM system boy do I have one.

A calibrated camera set up in the stands that uses AI tracking to understand the relative position of each robot on the field.

Humans then just have a button of “intake” or “shoot”, perhaps misses? and they press each button when that thing happens (of course this would be tailored according to the game)

Then based on when the button was pressed, that data would be matched up with the position data. Now all of a sudden you have full tracking of auto routines, accuracy of shots from different positions, places they intake from, cycle times and more. Essentially its the ultimate data hoarding technique, that you can then pull almost any data point from.

2 Likes

Similar (but different i think) thread here :

2 Likes

If you can track robots, you can track game pieces - at least every game piece is identical. So you wouldn’t need humans.

1 Like

We experimented with time stamping all activites tracked in our scounting app. This would provide data necessary to get firm cycle times and such.

In '24 we were specifically focused on when teams reached the center line game pieces in auto so we could respond accordingly with our auto routine. The concept was sound. Did it work? We won the automonous award on the Newton field and scored 51 in auto first match of elims against 254. In practice, our operator prescouted every team at all our events to know our opponents tendancies in auto so we could gain a material advantage in auto. For worlds, he pre-scouted 75 teams.

This year, something more automated would be ideal.

4 Likes

That’s really cool. I think I came across a tool on a CD thread that might do something similar.

The challenge comes when you need to position a camera in a location where you have to ensure people don’t pass through, as relying on the streams can be unreliable - at least in my area.

Technically, it’s a bit complex but definitely doable. I remember seeing a tool that accepts an endpoint and generates robot trajectories based on it, but I haven’t been able to find it again.

I’ve been working on our own scouting app for the last few months, and here are the killer features that I am really proud of so far:

  1. Configure the scouting metrics to be tracked within the web gui so they can easily be changed without needing to touch code
  2. Ability to swap the team nickname and number in the match schedule. I can’t remember everyone’s numbers all the time.
  3. Record practice runs/matches at home using the same metrics you record matches with, and then view metrics on that
  4. Picklist of teams, that you can drag into a different order than just sorting by a stat. Then save it and check those teams off as they are picked during alliance selection.
  5. Have a Scout Coordinator role that manages scouters so they can be scheduled for blocks of time, and see if scouters are missing match reports.
  6. When submitting a match report, automatically go to the next match, scouting the team on the same alliance/position. This will help with not accidentally having two people scout the same team, and not scout a team.
3 Likes

My ideal would be on the backend — take the data from quals and then run Monte Carlo simulation on every possible set of alliances. Then as selections are made all the alliances made impossible by the selection are dropped. When it is our turn to choose we should see the best remaining alliances possible for us in front of us. An additional refinement would be to use the data to predict the optimal choices for other teams to mark those alliances as unlikely to be available by the time our 2nd pick comes up.

Our scouting system has a match planning tool built into it. All the teams playing in your next match are listed along with some key stats to inform your strategy. There is a whiteboard of the field that you can draw on. Positional stats recorded by the scouts appear on it (and can be removed with check boxes).

You can use this link to play with the actual product.

  • The X are shooting locations. The green team could probably be defended by blocking the front of the speaker. The other two blue teams are likely to be passing.
  • The squares show where bots have started to give you an idea of how you can choose starting positions on your own alliance.
  • You can draw on the whiteboard to illustrate your match strategy to the drive teams from your alliance before the match starts.
  • You can click of the bot photos that were collected during pit scouting to get a reminder of what that bot looks like or to see what mechanisms it has.
1 Like

Scouting, Strategy and Drive team should all be on the same page. The biggest issue with scouting is keeping students interest up. Ideally you want to figure out what each team does. How a team approaches that goal of maintaining interest (= quality Intel) , interest= buy in, and knowlege that can be used is a fine balance.