How to Scout Recycle Rush?

[GeeTwo]

Originally Posted by tindleroot

A good scouting system will use both objective and subjective data in order to get the "whole scoop" on a team, but objective data should be used to compare every single team in the same way (i.e. # of totes, # of stacks, landfill feeding vs. human feeding), while subjective data is used to detect anomalies (i.e. team "9000" can stack totes with one robot while a tethered robot carries the stack to score )

Originally Posted by Fauge7

You want to pick bots that complement your bot! For example in this year if you have a feeder station bot, you want a bot that can work well in the "alley", if you have a 3 tote auto you want a bot that can do a 3 rc auto

I just thought those two were worth repeating.

This is the real reason I posted - I like the general format of this form, but have a few suggestions:

Originally Posted by Basel A

We're still making changes, but here's how we're scouting teleop:


The 1-6 is what level the [tote|RC|etc] was scored at. We like scantron-like scouting sheets, makes it much easier for our data entry guys. We also like shapes.

I presume you'll have six of these sheets for each match?

I like the gray totes and RC areas for tele-op; other than adding a few more in case of powerhouse teams, I don't see what to add..

However, for the litter, level does not matter, and this does not take into account either HP littering of the other side of the field, nor "processing" litter (this last is likely to be minimal anyway). There will also probably be cases where one team gets the litter in the RC and another team stacks it who gets this credit?

It looks like autonomous and coopertition need a bit of work:

• For yellow totes, why 4 and 2? It would seem to me that 3 for autonomous and 3 (or possibly 4, of which 3 could be checked) for coopertition would make more sense.
• There is no mention of how many RCs were moved to autozone during autonomous, nor whether the robot moved itself.
• This also does not address robots that can pull RCs off the step.

Also, there should probably be a "clumsiness" spot to indicate stacks that were knocked over by the robot (especially if it did not score them in the first place).

[Basel A]

Originally Posted by GeeTwo

I presume you'll have six of these sheets for each match?

I like the gray totes and RC areas for tele-op; other than adding a few more in case of powerhouse teams, I don't see what to add..

However, for the litter, level does not matter, and this does not take into account either HP littering of the other side of the field, nor "processing" litter (this last is likely to be minimal anyway). There will also probably be cases where one team gets the litter in the RC and another team stacks it who gets this credit?

It looks like autonomous and coopertition need a bit of work:

• For yellow totes, why 4 and 2? It would seem to me that 3 for autonomous and 3 (or possibly 4, of which 3 could be checked) for coopertition would make more sense.
• There is no mention of how many RCs were moved to autozone during autonomous, nor whether the robot moved itself.
• This also does not address robots that can pull RCs off the step.

Also, there should probably be a "clumsiness" spot to indicate stacks that were knocked over by the robot (especially if it did not score them in the first place).

We do single sheet for a team over the whole event. Got six of these match blocks on each side.

We're competing week 1, so the amounts of each are for this week. I'm sure we'll have to add more for MSC.

As I mentioned in my above post, this is teleop; we have a separate block (right next to this one) for autonomous. I omitted it just because it takes a minute of explanation, and wasn't relevant to the discussion above. So "yellow totes" here is coop (could probably add a third level one pentagon, that may be necessary).

I agree with you that litter doesn't need to be done by level, it just worked out better to package it this way. Still thinking about changing it. Stacks knocked over was already on our to-do list as well. Thanks for the input!

[saikiranra]

From a qualitative data stand point, I would pay attention to how well your team and the teams you are scouting work can together. If your robot only picks up bins/containers right side up, while another team knocks them over in autonomous, write that down. Additionally, note any interesting strategies other teams are attempting, and their flaws as well. This information is useful to your drive coach in working with other alliances.