Go to Post 100% of the robots on Einstein in 2009 had hard plastic wheels for their drive train. - efoote868 [more]
Home
Go Back   Chief Delphi > Competition > Rules/Strategy
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
View Poll Results: How many times are necessary to determine consistency?
Defenses: 1-3 1 1.35%
Defenses: 4-6 14 18.92%
Defenses: 7-10 18 24.32%
Defenses: 11-20 18 24.32%
Defenses: All 27 36.49%
Climbing: 1-3 4 5.41%
Climbing: 4-8 27 36.49%
Climbing: All 33 44.59%
Multiple Choice Poll. Voters: 74. You may not vote on this poll

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #13   Spotlight this post!  
Unread 27-01-2016, 03:05
Knufire Knufire is offline
Rose-Hulman Institute of Technology
no team
Team Role: College Student
 
Join Date: Sep 2009
Rookie Year: 2010
Location: Terre Haute, IN
Posts: 745
Knufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond reputeKnufire has a reputation beyond repute
Re: How many times is enough to prove consistency?

Remember, quantitative data is ALWAYS better than qualitiative. You have a goal in mind (measuring the consistency of robots crossing defenses). How can you measure this with a hard, factual number?

If you have a bunch of qualitative ratings that scouters can choose from, the robot will be at the mercy of the scouter's opinion. Different scouters on your team might have different standards as to what a "good" vs "struggle" crossing is.

I also don't see that many "unsuccessful" crossings happen. An unsuccessful crossing can only happen two ways; you either fail to get over the obstacle and back up, or you get stuck. If you're stuck, you're done for the match unless a partner comes and helps you out, and that probably only counts as one (albeit massive) failure. If you have to back up and try again, you'll probably get the same result (re. definition of insanity) unless you try to Duke of Hazzard it over.

My initial thought was to record not whether the robot crossed or not, but the time it took the robot to cross. Having the average time to cross each obstacle for every team at a tournament would be an extremely valuable piece of data. Downside is that this is probably only practical to record with some sort of electronic scouting system. For this method, I'd also define crossing per the manual definition of a CROSS for clarity.
__________________
Team 469: 2010 - 2013
Team 5188: 2014 - 2016
NAR (VEX U): 2014 - Present
 


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 On
HTML code is Off
Forum Jump


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

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