View Single Post
  #33   Spotlight this post!  
Unread 17-02-2006, 19:55
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: Post-ship S/W (& H/W) development restrictions

Quote:
Originally Posted by David Brinza
(Historically, Team 980 has been able to substantially improve robot performance during previous competition seasons, all in accordance with FIRST Q&A interpretation of the rules regarding software development and upgrade parts fabrication).
I want to clarify the above statement - in prior years, we added capability to our robot consistent with the rules and FIRST Q&A interpretation in those years. Last year, we modified our code and tested it on our practice robot. At the following competition site, we would manually enter changes to the version of code that was on the competition robot. This was entirely consistent with last year's Q&A regarding "cease software development":
Q: Does <R14>, particularly "cease all software development", preclude teams from changing code (variable values, PID gains, "broken" code, new functionality, etc.) after the Fix-It Window on our now-legal practice robot (per Q&A #1026).
A: You may do whatever on your practice robot but you must recreate your "fixes" onsite at a competition.
This year, our post-ship coding and testing will be restricted solely to FIX-IT WINDOWS and at the competitions...
__________________
"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