Go to Post 4's company, 5's a crowd, and 6 is someone off-sides. - HyPhire111 [more]
Home
Go Back   Chief Delphi > Competition > Team Organization
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
  #6   Spotlight this post!  
Unread 11-06-2011, 20:41
BJC's Avatar
BJC BJC is online now
Simplicity is Complicated!
AKA: Bryan Culver
FRC #0033 (The Killer Bees)
Team Role: Alumni
 
Join Date: Jan 2010
Rookie Year: 2009
Location: Kettering/Greenville
Posts: 706
BJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond reputeBJC has a reputation beyond repute
Re: How do you make design decisions as a "team"?

I'll try to give what little knowledge I have regarding design..

1. Figure out what your design goals are before anyone comes up with any designs. It is natural to immidiatly begin to jump to the idea stage after being presented with a problem. Refrain from this, redefine and specify the problem.

2. Make a list of priorities based on your redefined problem. A list of priorities in 2011 for tube hanging would have been: -drive around -aquire tube -get tube into scoring position -release tube Notice how being able to release a tube is useless without being able to effectivly aquire one. Thus aquiring comes first. Many teams fall into the trap of mixing up their priorities and end up with a robot that can't effectively play the game as a result.

3. Refine your problem again. Ok done? Now do it again. This is the most important part of the process. Even the best designed robot performs poorly if its solving the wrong problem.

4. At this point it's time to break out the Weighted Objective Tables. Yaaay! But seriously, use them, they help prevent "my-own-design-is-the-best-osis" and often make seemingly close and difficult choices obvious. USE THEM!

5. At this point you hopefully have a design thought out. Now go and make sure that your still staying true to the origional problem you defined. It probably isn't; fix it so it is. The design will become simpler as a result--that's a good thing.

6. Alright, your done! You have a successful design. Just kidding! Now do this again three times.

Doing these things as a team makes for a very successful robot. Good Luck!
__________________
robot robot robot? Robot. Robot? Robot!
-----------------Team 33------------------

Last edited by BJC : 11-06-2011 at 20:50.
Reply With Quote
 


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 01:17.

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