Go to Post We can read about torque and speed in books, we can build a robot and drive it, but determination and character are built by time and encouragement, not just by studying. - Eugenia Gabrielov [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #22   Spotlight this post!  
Unread 04-12-2006, 17:39
ntroup's Avatar
ntroup ntroup is offline
WildStang!
None #0111 (Wildstang)
Team Role: Engineer
 
Join Date: Oct 2002
Rookie Year: 2002
Location: Schaumburg
Posts: 52
ntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud ofntroup has much to be proud of
Re: Ethics 101: To re-use or not to re-use?

As it seems that this should somehow make a difference, I, as well, write software for a living.

With that said, I have to agree with those agree that software is different than other components. Yes, I agree that software is a part of the robot, and, in fact, it is a integral and critical component. But it is fundamentally different than hardware.

I see a few arguments to that. One being that re-typing the code allows one to support this rule. But how is that really any different than copying/pasting, or checking out a version from your favorite source-code repository. There isn't a difference, other than potentially introducing typos that require more time to debug. This doesn't seem like a productive use of time for teams.

If you have a known good design/algorithm/function, why try to re-invent it. You only have to invent the wheel once, then you use it, because you know how it works. The same goes for Omni-Wheels, Transmissions, etc.

As said before, if the argument is that it is faster for teams to copy/paste or checkout a version than rookie teams, then how is it fair for teams to have CAD files that will generate all the components needed for a mechanical design at a moment's notice.

The rule says this:
Quote:
However, the specific lines of code must be customized for each robot each year.
Since no game is going to be the exact same each year, this is going to always be true. The code will have to be customized for that game. As Jack eluded to, I doubt there will be PoofBall throwing robots next year. BUT, I can definitely foresee teams needing to track lighted objects on the field. To have to completely re-write that from scratch, as others have inferred, would be pointless AND difficult.

Each year is a learning experience. And each year, teams learn and perfect various pieces of their robot. To have to force team's to re-perfect any component each year, be it hardware or software, seems like a step backwards in where this program is aiming to go... to create those that go one step beyond.

-Nate
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

Similar Threads
Thread Thread Starter Forum Replies Last Post
Robot Ethics? negfrequency General Forum 33 01-06-2006 18:55
Does anyone else NOT use a long arm to place a tetra on top of the Goal? mad_cloversc General Forum 29 08-03-2005 00:44
Accelerometer Use Doug G Programming 2 15-12-2004 09:06
can we use? Allie Kit & Additional Hardware 5 13-02-2002 15:54


All times are GMT -5. The time now is 10:03.

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