Team UPDATE - 2013-03-05

[Joe Ross]

General Rules
G16

TEAMS and/or ROBOTS may not employ strategies that use DISCS to either aid or inhibit a ROBOT CLIMB.
Violation: TECHNICAL FOUL. If the DISC(S) inhibits an opponent’s CLIMB attempt, the opponent ROBOT’S ALLIANCE is awarded points for a successful Level 3 CLIMB will be granted credit for a Level 3 CLIMB at the end of the MATCH.


ROBOT Actions
G27

ROBOTS may not contact or otherwise interfere with their opponents’ PYRAMID. Inconsequential contact will not be penalized.
Violation: TECHNICAL FOUL. If an opponent’s CLIMB is affected,

RED CARD, and
Each affected opponent ROBOT will be awarded points for a successful Level 3 CLIMB granted credit for a Level 3 CLIMB at the end of the MATCH.

ROBOT-ROBOT Interaction
G30

Regardless of who initiates the contact, a ROBOT may not contact an opponent ROBOT

contacting its PYRAMID or
touching the carpet in its LOADING ZONE.

Violation: FOUL. If purposeful or consequential, TECHNICAL FOUL. If an opponent's CLIMB is affected, each affected opponent ROBOT will be awarded points for a successful Level 3 CLIMB granted credit for a Level 3 CLIMB at the end of the MATCH.



Game Manual

General Announcements
A required update has been released for C++ (http://firstforge.wpi.edu/sf/frs/do/viewRelease/projects.wpilib/frs.2013_frc_update_for_c.mandatory_update_rev_362 2). This update fixes an error in the implementation of Network Tables feeding information to the SmartDashboard. It also fixes an issue with LiveWindow code causing crashes for teams using threads. Full release notes can be found on the 2013 Software Notes page (http://wpilib.screenstepslive.com/s/3120/m/8559/l/92653-2013-software-notes). Our thanks to the teams and volunteers that helped us identify and troubleshoot the issues and solutions during Week 1 Events.


General note: TEAM Members may not lift other TEAM Members in the ALLIANCE STATION (either up on shoulders or otherwise) as this is a safety issue and will yield a Yellow Card per Section 5.5.4.


Q141 Change
After additional review, we are changing our answer to Question 141 (https://frc-qa.usfirst.org/Question/141/showquestion) on the Q&A. Once a robot has been awarded points for a Level 3 climb as the result of a penalty, it will no longer be eligible for additional climb points. The applicable rules are being changed to improve clarity.
Q: Per G16 and G27 a robot is awarded points for a Level 3 climb if their climb is interfered with. If the disrupted robot attempts another climb after the incident, is it eligible for additional climb points?
A: Yes. No.

C++ teams, make sure you install the update.

[Kevin Sevcik]

Climb rule updates make sense, same as the balancing interference penalty last year. I was always assuming that's how it worked anyways, so I suppose it's good the GDC has come around to my way of thinking in time for our first regional.

[GaryVoshol]

Given that there's no way in the scoring system to assign more than one climb level per robot, it only makes sense.

[Lil' Lavery]

Given that there's no way in the scoring system to assign more than one climb level per robot, it only makes sense.

They could just add 30 more foul points.

Moot point now.

[Chris is me]

General note: TEAM Members may not lift other TEAM Members in the ALLIANCE STATION (either up on shoulders or otherwise) as this is a safety issue and will yield a Yellow Card per Section 5.5.4.

Wow, so if someone gives a teammate a "lifting hug", they get a yellow card? There's a rule for everything now.

On the bright side, this is probably the most benign Week 1 update in awhile.

[GaryVoshol]

They could just add 30 more foul points. But foul points and climb points contribute differently to the rankings.

Moot point now.Agree

[Donut]

Wow, so if someone gives a teammate a "lift "ing hug", they get a yellow card? There's a rule for everything now.

I'm hoping the referees don't call this one to the letter as it's written, though I suppose "lift" needs to be properly defined. I can understand why they would want to discourage something like a human pyramid from being built by the drive teams but a bear hug could bring about a yellow card if "lift" is interpreted as simply "no longer contacting the floor".

At that point why not just discourage jumping too? Then the drive teams can stand calmly and watch as the MC does a flip during their team intro.

[JohnBoucher]

I'm hoping the referees don't call this one to the letter as it's written, though I suppose "lift" needs to be properly defined. I can understand why they would want to discourage something like a human pyramid from being built by the drive teams but a bear hug could bring about a yellow card if "lift" is interpreted as simply "no longer contacting the floor".

At that point why not just discourage jumping too? Then the drive teams can stand calmly and watch as the MC does a flip during their team intro.

Clarify this during the drivers meeting.

[Chris is me]

Frank clarified on FRC Blog. (http://www.usfirst.org/roboticsprograms/frc/blog-week-1-and-what-no-hugs) Wow, FIRST's ability to monitor community opinion is impressive! I feel kinda bad for making them respond to my cranky 6-AM-on-the-day-of-an-exam observation.