View Single Post
  #21   Spotlight this post!  
Unread 13-02-2006, 23:59
David Brinza's Avatar
David Brinza David Brinza is offline
Lead Mentor, Lead Robot Inspector
FRC #0980 (ThunderBots)
Team Role: Mentor
 
Join Date: Feb 2003
Rookie Year: 2003
Location: Glendale, CA
Posts: 1,379
David Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond repute
Re: cease all software development?

Quote:
Originally Posted by dlavery
That was an answer to a question about the 2005 rules. It does not apply to the 2006 rules.
Here is the 2005 rule:
<R14> Prior to the competitions: After the close of the “FIX-IT WINDOW” and prior to the competition, the team must put down their tools, cease fabrication of robot parts, and cease all software development. Take this opportunity to rest, recover from the build season, and relax. Teams may scout other teams, gather and exchange information, develop game-playing strategies, collect raw materials, prepare tool kits, plan how to make repairs, etc. in preparation for the upcoming competitions. But no construction or fabrication is allowed.
Compare with the 2006 rule:
<R18> Prior to the competitions: After the close of the “FIX-IT WINDOWS” and prior to the competition, the
team must put down their tools, cease fabrication of robot parts, and cease all software development. Take
this opportunity to rest, recover from the build season, and relax. Teams may scout other teams, gather and
exchange information, develop game-playing strategies, collect raw materials, prepare tool kits, plan how to
make repairs, etc. in preparation for the upcoming competitions. But no construction or fabrication of any
hardware, or development of any software, is allowed.
The difference is in the last sentence, where the phrase "or development of any software" now appears.

So, as was discussed last year, there needs to be some clarification about what constitutes software development (i.e. conceptual design, flowchart, algorithm, coding, test, any or all of these). Since "any software" is stated, dashboard code may also be subject to this restriction.


Time for a new Q&A post!
__________________
"There's never enough time to do it right, but always time to do it over."
2003 AZ: Semifinals, Motorola Quality; SoCal: Q-finals, Xerox Creativity; IRI: Q-finals
2004 AZ: Semifinals, GM Industrial Design; SoCal: Winners, Leadership in Controls; Championship: Galileo #2 seed, Q-finals; IRI: Champions
2005 AZ: #1 Seed, Xerox Creativity; SoCal: Finalist, RadioShack Controls; SVR: Winners, Delphi "Driving Tomorrow's Technologies"; Championship: Archimedes Semifinals; IRI: Finalist
2007 LA: Finalist; San Diego: Q-finals; CalGames: Finalist || 2008 San Diego: Q-finals; LA: Winners; CalGames: Finalist || 2009 LA: Semifinals; Las Vegas: Q-finals; IRI: #1 Seed, Finalist
2010 AZ: Motorola Quality; LA: Finalist || 2011 SD: Q-finals; LA: Q-finals || 2013 LA: Xerox Creativity, WFFA, Dean's List Finalist || 2014 IE: Q-finals, LA: Finalist, Dean's List Finalist
2016 Ventura: Q-finals, WFFA, Engineering Inspiration