typo in the FRC Manual

[Sparkyshires]

Don't mean in this in a mean way at all, just noticed that under 3.1.4 pedestal is spelled PEDASTAL. Sorry if you think this is kinda silly, but has anyone else noticed any silly typo's/errors in the manual? And yeah I know I have way too much time on my hands.

[pfreivald]

"typo's"?

Surely you mean, "typos"....

[jvriezen]

Originally Posted by Sparkyshires

Don't mean in this in a mean way at all, just noticed that under 3.1.4 pedestal is spelled PEDASTAL. Sorry if you think this is kinda silly, but has anyone else noticed any silly typo's/errors in the manual? And yeah I know I have way too much time on my hands.

Most typos are not worthy of noting, but since this is a glossary term and one fro which someone may want to search for all occurrences, it is worth noting.

[Caleb Sykes]

Section 3.2.3.6 and section 3.2.4.2 are both labeled as G16. 3.2.3.6 should probably be G14. I would appreciate it if someone noted this on the Q and A so that they can change it, just because 3.2.3.6 is too important of a rule to be labeled incorrectly. I can see it now:
Referee: "Your team violated G16."
Team member: "What? Our drivers certainly did not step over the STARTING LINE in AUTO."
Referee: "What? No, you forced another alliance to incur a penalty, which is illegal"
Team member: "How did our driver stepping over the line in AUTO cause the other alliance to get a penalty?"
Referee: "No, your drivers didn't step over the line in AUTO."
Team member: "Then what was our penalty for?"
etc...

Also, potentially correct but certainly confusing is the last paragraph in the blue box beneath G12:

A BALL that becomes unintentionally lodged on a ROBOT will be considered
POSSESSED by the ROBOT. It is important to design your ROBOT so that it is
impossible to inadvertently or intentionally POSSESS an opponent’s BALL.

Emphasis mine.

How do you design your robot so that it is impossible to intentionally POSSESS an opponent's BALL? I don't think that any teams are going to have a red/blue sensor on their pickup device to make sure that, even if the drivers really want to pick up the opponent's BALL intentionally, the robot will not allow them to do so.

No. I'm pretty sure it is supposed to be unintentionally.

[pfreivald]

Originally Posted by inkling16

No. I'm pretty sure it is supposed to be unintentionally.

I'm quite certain it isn't.

Inadvertently = unintentionally.
Intentionally = on purpose.

The rule reads exactly as it's supposed to read: whether intentional or not, you'll get a penalty for possessing your opponent's ball.

[Ian Curtis]

Originally Posted by pfreivald

The rule reads exactly as it's supposed to read: whether intentional or not, you'll get a penalty for possessing your opponent's ball.

In that case, our software team will spend the next 6 weeks designing a system that will only allow our possessor to operate on one color of ball. Hope we don't forget to change the big switch from BLUE to RED when we change alliances!

(I think this a level of semantics we can safely agree it's not worth arguing over. There's robots to build!! )

[pfreivald]

Originally Posted by Ian Curtis

In that case, our software team will spend the next 6 weeks designing a system that will only allow our possessor to operate on one color of ball. Hope we don't forget to change the big switch from BLUE to RED when we change alliances!

That's one way to do it....

[Alan Anderson]

Originally Posted by Ian Curtis

In that case, our software team will spend the next 6 weeks designing a system that will only allow our possessor to operate on one color of ball. Hope we don't forget to change the big switch from BLUE to RED when we change alliances!

Your software team will probably know this already, but your alliance color is communicated to the robot by the field system. No switch would be necessary if you wanted to implement the anti-opponent-ball-possession system.

[Bill_B]

Or you could make a dual sensor system that compares the ball color to your own bumper color. If different, don't pick it up!