Go to Post Too often we like to forget that it takes an insane amount of hard work to even have a chance to overcome raw talent. - Paul Copioli [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

 
 
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #3   Spotlight this post!  
Unread 13-04-2014, 19:46
pabeekm's Avatar
pabeekm pabeekm is online now
Master of typos
AKA: Patricia
FRC #0900 (Zebracorns)
Team Role: Alumni
 
Join Date: Mar 2014
Rookie Year: 2012
Location: Pasadena, CA
Posts: 121
pabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond reputepabeekm has a reputation beyond repute
Re: Data Scouting

Congrats on getting to Worlds!

Our team keeps track of robot performance during each match by filling out a paper form with three main sections.

The first is a small section for autonomous where scouters fill out whether the robot started with a ball, whether they got mobility points, the goal they tried to score in, and if they made it. (In the rare case of a double ball auto, scouters specify the outcome in the notes section).

The second is a big notes section for jotting down qualitative assessments and miscellaneous observations (had awful partners this match, got pushed easily, fast driving, played killer defense, incurred a pinning foul, etc.)

The third section is a fill in the blank about what the robot did with the ball during each cycle, and how long they possessed the ball. For example:

1. role = middleman*, goals = truss, shots = 2, score = 10, time = 10s
2. role = inbounder/scorer**, goals = high/low, shots = 3/1***, score = 1****, time = 45s
3. role = defense
4. role = inbounder, time = 8s

*passed between two alliance partners
** got inbound and went straight to score
*** 3 high goal shots, one low low goal shot
**** made the low goal after missing the high goal shots

This process requires six scouters (one for each robot) and takes up a lot of paper (one half-sheet form per robot per match), but the completeness of the data really helped us evaluate the competing robots' capabilities and helped a ton in strategizing for our matches and picking our winning alliance.

What variables did you guys watch for? Was it just quantitative or also qualitative? I'm always interested in what other teams are looking at.

Last edited by pabeekm : 13-04-2014 at 19:48.
 


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:05.

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


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