View Single Post
  #20   Spotlight this post!  
Unread 02-01-2013, 18:35
jspatz1's Avatar
jspatz1 jspatz1 is offline
Registered User
AKA: Jeff
FRC #1986 (Team Titanium)
Team Role: Mentor
 
Join Date: Jan 2008
Rookie Year: 2007
Location: Lee's Summit, MO
Posts: 836
jspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond reputejspatz1 has a reputation beyond repute
Send a message via AIM to jspatz1
Re: 2013 KB on steriods

Quote:
Originally Posted by 1493kd View Post
Why is this so? We have had sub par results in our 10 years of doing it the way that we have. We dont have enough resources to devote time to custom things and would be better served using the provided frame. The rest of the team felt that this would be a good approach. I am reaching out to the chiefdelphi community asking for advice. Before I face palm in frustration could you please explain to me how my fundementals need to be rethought?
I am refering to the idea of "deciding" or "convincing" your team what drivetrain you will use, or any other detail about your robot, before anything about the game is known. Making design decisions before any of the criteria are known. That is the approach I am advising rethinking. What if the KBoS is entirely inappropriate for the game? Bumps, ramps, obstacles, stairs, platforms, climbing, etc., etc. Design is the process of meeting and reacting to a challenge. Design decisions before the challenge is even known are just a shot in the dark. What is more likely to succeed, a decision based on the challenge, or one made before the challenge is even known?