OCCRA
Go to Post It's a club if you have a bunch of people who hang out and do nothing - It's a team if all you all work together and cooperate to win. - Tytus Gerrish [more]
Home
Go Back   Chief Delphi > Competition > Rules/Strategy > Scouting
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 02-19-2018, 09:35 AM
aagalicki aagalicki is offline
Registered User
AKA: Andy Galicki
FRC #6081 (Digital Dislocators)
Team Role: Mentor
 
Join Date: Feb 2018
Rookie Year: 2012
Location: Grass Lake, MI
Posts: 1
aagalicki is an unknown quantity at this point
Scouting Metrics

Hey everyone!

I'm wondering how everyone is doing with their scouting systems this year. What kind of metrics have you decided upon? What format are you using? (paper, apps, excel, etc.) Overall, how are things shaping up for your scouting teams?

Personally, we (6081) are planning on using FRC Krawler this year. I've been very satisfied with the way that it is handling the data based on the metrics that we've chosen to use. (Shout out to 2052 for such an awesome system woohoo!)

As for metrics, we've locked down metrics for both autonomous and the endgame, but struggled a bit with coming up with ideas for tele-op. The students and I ultimately decided that solely keeping track of the number of cubes that a team can run wouldn't be quite as effective, seeing as the necessary number of cubes in any given location has the potential to vary wildly from match to match. What we decided to do is keep track of where the cubes can be placed by any given team, and then give the team an efficiency rating for the tele-op portion. This should hopefully more or less operate as an estimated cycle time, without having to time each cube placed. HOWEVER, we realized that it may be worth tracking the number of cubes that a bot can place in the exchange, because it's the only location where the opposing alliance won't be placing cubes.

Overall, we're quite satisfied with the way our testing up until now has turned out, and we're hoping that it continues to prove successful!
Reply With Quote
  #2   Spotlight this post!  
Unread 02-19-2018, 09:51 AM
Billfred's Avatar
Billfred Billfred is offline
Never look back, no, never say die
AKA: Always attack with the warrior's cry...
FRC #1293 (Pandamaniacs); FTC #11444 (Garnet Squadron)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: The Shadow Realm
Posts: 9,487
Billfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond reputeBillfred has a reputation beyond repute
Re: Scouting Metrics

Quote:
Originally Posted by aagalicki View Post
As for metrics, we've locked down metrics for both autonomous and the endgame, but struggled a bit with coming up with ideas for tele-op. The students and I ultimately decided that solely keeping track of the number of cubes that a team can run wouldn't be quite as effective, seeing as the necessary number of cubes in any given location has the potential to vary wildly from match to match. What we decided to do is keep track of where the cubes can be placed by any given team, and then give the team an efficiency rating for the tele-op portion. This should hopefully more or less operate as an estimated cycle time, without having to time each cube placed. HOWEVER, we realized that it may be worth tracking the number of cubes that a bot can place in the exchange, because it's the only location where the opposing alliance won't be placing cubes.
I agree, the success rate of placing in a given area (including the exchange) is important. We're behind on our scouting (like everything else...), but some other things I'd want to track:

* Fouls
* Robot deaths/no-shows
* Blown pickups (where they grab, miss or drop it quickly, and have to stop to grab again). I suspect this will make it clearer when a team has a weak robot versus a weak strategy.
* Defensive moves (painted broadly and subjectively) Over eight or ten matches, you'll see some standouts.
* If a fast climb is significant to you, maybe some stat for "time spent screwing around in the platform zone".
__________________
William "Billfred" Leverette - Gamecock/Jessica Boucher victim/Owner/Director of Bricks 4 Kidz in Columbia, SC.

2004-2006: FRC 1293 (D5 Robotics) - Student, Mentor, Coach
2007-2009: FRC 1618 (Capital Robotics) - Mentor, Coach
2009-2013: FRC 2815 (Los Pollos Locos) - Mentor, Coach - Palmetto '09, Peachtree '11, Palmetto '11, Palmetto '12
2010: FRC 1398 (Keenan Robo-Raiders) - Mentor - Palmetto '10
2014-2016: FRC 4901 (Garnet Squadron) - Co-Founder and Head Bot Coach - Orlando '14, SCRIW '16
2017: FRC 5402 (Iron Kings) - Mentor, Coach (oh, and I worked at AndyMark during this time)
2018-: FRC 1293 (Pandamaniacs) - Mentor

113 events (more than will fit in a ChiefDelphi signature), 15 seasons, over 74,500 miles, and still on a mission from Bob.
Rule #1: Do not die. Rule #2: Be respectful. Rule #3: Be safe. Rule #4: Follow the handbook.
Reply With Quote
  #3   Spotlight this post!  
Unread 02-19-2018, 09:56 AM
Boltman Boltman is offline
Strategy/Rules/Scouting/Volunteer
AKA: Tom Byrne
FRC #5137 (Iron Kodiaks)
Team Role: Mentor
 
Join Date: Apr 2014
Rookie Year: 2014
Location: San Diego
Posts: 1,362
Boltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant futureBoltman has a brilliant future
Re: Scouting Metrics

KISS...

Cube acquire time scoring placement time (secs)
climb? Y/N
auto? Y/N

In the end that covers 90% the other 10% driver smarts
Be careful of scouting information overload.
__________________


Iron Kodiaks Team #5137 San Marcos, CA
2018 Orange County Elimination Alliance (5477.5209) QF
2017 Ventura Captain 3 (8, 3882) QF
2016 Central Valley Captain 2 (973, 2135) SF
2015 Ventura Elimination Alliances (696, 1836) SF
2014 San Diego Rookie All-Star Galileo Division
San Diego (Home regional/practice days) : Not chosen '18 Elimination Alliances:'17 (399, 968) SF ,'16 (1159, 812) SF , '15 (3021, 1772) QF

Volunteer @ Orange County 2016, 2017, 2018 Ventura 2018

Last edited by Boltman : 02-19-2018 at 10:02 AM.
Reply With Quote
  #4   Spotlight this post!  
Unread 02-19-2018, 10:12 AM
blazingbronco18 blazingbronco18 is offline
Registered User
FRC #3200 (Raptacon)
Team Role: Mentor
 
Join Date: Mar 2015
Rookie Year: 2011
Location: Colorado
Posts: 73
blazingbronco18 is an unknown quantity at this point
Re: Scouting Metrics

Quote:
Originally Posted by Boltman View Post
KISS...

Cube acquire time scoring placement time (secs)
climb? Y/N
auto? Y/N

In the end that covers 90% the other 10% driver smarts
Be careful of scouting information overload.
I would argue this doesn't give you enough information to determine the strategies that teams are performing. For example, there is a difference between putting a cube on the scale or on the switch. Having just a cube cycle time doesn't tell me where the cubes are being placed. I agree with the KISS principle, but there needs to be a balance between getting the data that helps a team make calculated decisions while keeping the scouting simple.
Reply With Quote
  #5   Spotlight this post!  
Unread 02-19-2018, 12:31 PM
mjc49's Avatar
mjc49 mjc49 is offline
Coach - Team 3042
AKA: Mike
FRC #3042 (Cobalt Catalyst)
Team Role: Coach
 
Join Date: Aug 2013
Rookie Year: 2013
Location: Minnesota
Posts: 78
mjc49 is an unknown quantity at this point
Re: Scouting Metrics

Quote:
Originally Posted by aagalicki View Post
Hey everyone!

As for metrics, we've locked down metrics for both autonomous and the endgame, but struggled a bit with coming up with ideas for tele-op. The students and I ultimately decided that solely keeping track of the number of cubes that a team can run wouldn't be quite as effective, seeing as the necessary number of cubes in any given location has the potential to vary wildly from match to match. What we decided to do is keep track of where the cubes can be placed by any given team, and then give the team an efficiency rating for the tele-op portion. This should hopefully more or less operate as an estimated cycle time, without having to time each cube placed. HOWEVER, we realized that it may be worth tracking the number of cubes that a bot can place in the exchange, because it's the only location where the opposing alliance won't be placing cubes.
With so many possible scenarios, I agree that this is a hard game to scout in Teleop. That said, a good drive team will be making things happen on the field so I believe if a team is playing offense, then the total # of cubes placed somewhere is important. The circumstances may dictate a change in tactics, but a robot should be doing something at all times IMO if it isn't having technical difficulties.

We plan to use tablets to scout and dump that data along with the FRC event data into excel and generate reports.
__________________
---------------------------------------
(2013-Current) FRC Team 3042 Cobalt Catalyst, MN, FTC 8473 Blue Lightning, FTC 9182 Short Circuits, FTC 9183 Storm Warning and FTC 11621 Light Speed
2017-2018 LRI: MN North Star Regional
Reply With Quote
  #6   Spotlight this post!  
Unread 02-28-2018, 10:46 AM
ClercDruster's Avatar
ClercDruster ClercDruster is offline
Registered User
AKA: Drew
no team
Team Role: Programmer
 
Join Date: Apr 2017
Rookie Year: 2017
Location: Philadelphia
Posts: 8
ClercDruster is an unknown quantity at this point
Re: Scouting Metrics

This year I decided that we'll be using pen and paper, because the wifi at our events usually sucks, and a lot of our team doesn't always have access to cell data. We have a spreadsheet tracking climbing, cubes, if it delivers properly in auto, defense, and the lovely "other comments" column.
Reply With Quote
  #7   Spotlight this post!  
Unread 02-28-2018, 02:51 PM
Theultracorgi's Avatar
Theultracorgi Theultracorgi is offline
Registered User
AKA: Kenneth
FRC #0930 (Mukwonago BEARs)
Team Role: Scout
 
Join Date: Jan 2017
Rookie Year: 2013
Location: Wisconsin
Posts: 11
Theultracorgi is an unknown quantity at this point
Re: Scouting Metrics

Quote:
Originally Posted by mjc49 View Post
With so many possible scenarios, I agree that this is a hard game to scout in Teleop. That said, a good drive team will be making things happen on the field so I believe if a team is playing offense, then the total # of cubes placed somewhere is important. The circumstances may dictate a change in tactics, but a robot should be doing something at all times IMO if it isn't having technical difficulties.

We plan to use tablets to scout and dump that data along with the FRC event data into excel and generate reports.

I totally agree. This year it was HARD to determine what metrics will actually be valuable. In addition, CD wasn't super helpful this year, because the bulk of responses sound like this. (directed at no team in particular)

Qualitative data is important, we have been doing qualitative for years, and we love this game. And it's gonna be super important, so we're gonna record qualitative data.

great... I like qualitative data as well, but that doesn't give me any specifics to go off of.

So after weeks of thinking/discussion, we finally decided on having individual scouts watch one robot and scout.....

AUTON:

Autoline Crossed(y/n)

# of attempts to place cubes on Switch
# of successfully scored cubes on Switch

# of attempts to place cubes on Scale
# of successfully scored cubes on Scale

(scored/attempts will give us success rate, which is helpful to see improvement due to driver practice)

TELEOP:

# of attempts to place cubes on Switch
# of successfully scored cubes on Switch

# of attempts to place cubes on Scale
# of successfully scored cubes on Scale

# of cubes placed in exchange

Endgame Position(Not scoring, Parked, Climbing)

POST MATCH:

Whether they were disabled or not at any point

Comments(notes on driver skill, speed, haiku about scouting)
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 02:07 AM.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi