25-06-2015, 11:41
|
|
Mentor
AKA: Steve Peterson
 FRC #3081 (Kennedy RoboEagles) Team Role: Mentor
|
|
Join Date: Mar 2012
Rookie Year: 2011
Location: Bloomington, MN
Posts: 581
|
|
|
Re: On the quality and complexity of software within FRC
What effects would this change to the rules have on software quality?
Quote:
R15 Teams must stay “hands-off” their bagged ROBOT elements during the following time periods:
A. between Stop Build Day and their first event,
B. during the period(s) between their events, and
C. outside of Pit hours while attending events.
Additional time is allowed as follows:
D. After Kickoff, there are no restrictions on when software may be developed.
E. On days a team is not attending an event, they may continue development of any items permitted per R17, including items
listed as exempt from R17, but must do so without interfacing with the ROBOT.
F. Teams attending 2-day events may access their ROBOTS per the rules defined in the 2015 Administrative Manual Section 5.6: ROBOT Access Period - for Teams Attending District Events.
G. ROBOTS may be exhibited per 2015 Administrative Manual Section 5.5.3: Robot Displays.
H. Teams may operate their ROBOT for the purpose of testing software updates.
|
I purposely left out fixing the robot in the new language.
__________________
2016-17 events: 10000 Lakes Regional, Northern Lights Regional, FTC Burnsville Qualifying Tournament
2011 - present · FRC 3081 Kennedy RoboEagles mentor
2013 - present · event volunteer at 10000 Lakes Regional, Northern Lights Regional, North Star Regional, Lake Superior Regional, Minnesota State Tournament, PNW District 4 Glacier Peak, MN FTC, CMP
http://twitter.com/MrRoboSteve · www.linkedin.com/in/speterson
|