![]() |
Annual Reminder--Please Read the Manual!
To: All FRC participants
From: More experienced FRC participants, your inspectors, your referees, and your field crews Date: 1/4/2014 (published a couple days early on 12/31/13) Topic: The Manual, and Other Resources We know that on the date shown above, you will see the 2014 FRC game for the first time. So will we. It's natural that you'll have some questions about it. That's great, so will we. But when you see the game and immediately go onto Chief Delphi asking "Can we use CO2 on the robot?", "Where do the bumpers have to be placed?", "Can we use another battery?", "Is there a design for X device?", and "How many robots can we tip before we get a penalty?", please expect a tough response from us. It's not that we don't like you; on the contrary, we'd very much like to get to know you better (and some of us probably will!). In fact, it's that your questions have probably been answered already, very clearly. This typical very clear answer can typically be found by a quick reading of the Game Manual. You just have to find the right section. Of those 5 questions above, 4 answers will be in the Robot section, 1 in the Game section, and one will get a response something like "you'll learn more by designing it yourself", as it is not in the Manual. Can't find what you're looking for? Ctrl-F brings up a find feature, or there's a search box on the Manual page. Search a couple of key words, and you'll probably get all the answers you need for those "obvious" questions. Generally, if you've looked, and/or you show evidence you've looked, the responses won't be quite so harsh as if you just post "hy guys can we us3 a engine on the robot thx". Now, on occasion, you'll see something in the Manual and have a question. Chances are some other folks did too, probably the rest of us participants and officials at some point. A quick Chief Delphi search will help show what if anything we've discussed about the topic; if nothing crops up, start a thread and see what develops. Bear in mind, however, that ANYTHING you see on Chief Delphi is NOT official. I'll repeat that: NOT official. If Dean Kamen, Woodie Flowers, Dave Lavery, AND Frank all got onto Chief and said something, it still wouldn't be official. CD is not the Manual, and it is not the official Q&A system. (Al Skierkewicz on inspection items? Not official yet, but probably will be once you see the officially-released documentation.) The official communication channels for rules-related items are: The Game Manual, including any Updates up to the latest one, gives the rules. The Q&A answers questions about those rules and gives interpretations. FRC Blog? Not a rules source, but if Frank says something it's reasonable to assume that a Q&A or Update will address that shortly--but it still isn't a rule. Short version: Please read the Manual before asking questions on CD, and bear in mind that no CD answer is ever official. P.S.: For anybody ANSWERING rules questions, please, please, please put the rule number in your post, so that others can track it down! Quoting the rule verbatim is also a good idea--but then others won't have the fun of finding it in the Manual and maybe noticing some other rule that affects their design. :p |
Re: Annual Reminder--Please Read the Manual!
Great post. This is definitely something essential for all teams to do. I've seen teams show up to events and have to redesign/remove entire components year in and year out. Bumpers being the most common problem for teams. Now how do we get everyone to read this post?!
|
Re: Annual Reminder--Please Read the Manual!
Eric, thanks for posting this reminder: reading through it was good for me! It's definitely an important one that needs to be given every year... hopefully the folks who especially need the reminder will see this thread!
The reminder to people answering rules questions is perhaps even more important though... it's one thing for someone to ask "what are the robot dimensions?" It's an even bigger issue when someone answers with "28x38... what they've been for at least a decade". So, to all the rules experts... make sure you're really an expert on the relevant rules before you answer a question! :-) |
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
Anyways, can we get this posted on the FRC blog or something more noticeable like that. Maybe have it announced at the kickoff broadcast :rolleyes:. Although people still probably wouldn't listen. |
Re: Annual Reminder--Please Read the Manual!
tl;dr :yikes:
|
Re: Annual Reminder--Please Read the Manual!
Are we allowed to tell people RTFM? (Read the FRC Manual) :rolleyes:
|
Re: Annual Reminder--Please Read the Manual!
Best you don't, some may misinterpret the F ::rtm::
Ultimately, The Manual answers All Questions. Use it wisely. Bad information is worse than no information. Please avoid spreading bad information. |
Re: Annual Reminder--Please Read the Manual!
Quote:
My favorite trick for remembering if I've got the rule right when I answer a rules-based question is to check the Manual right before, exception being if I've answered the same question 47 times in the last week or so, in which case I've probably got the rule in short-term memory pretty solidly. |
Re: Annual Reminder--Please Read the Manual!
![]() |
Re: Annual Reminder--Please Read the Manual!
Also, read the Tournament section of the Manual in addition to the Game, Robot, and Arena sections. You'll never know when FIRST will decide to mix up the ranking algorithm...
|
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Is the manual even out coded so that we can download it pre kickoff?
::rtm:: |
Re: Annual Reminder--Please Read the Manual!
Quote:
While this happens every year, I have a hard time telling a team that their assembly was ruled illegal in Team update #16 only to find out that they had faithfully copied and bound all team updates except #16. Thanks Eric for starting this thread. Teams if you have specific questions that you think may compromise your strategy, you may PM me for an opinion until such time as the Q&A is answered. While the Q&A team tries to respond quickly, correct answers are important to them. That may require more input from the team before a response is made public. Please be patient. |
Re: Annual Reminder--Please Read the Manual!
Also, do NOT use FIRST Q&A to find an answer that IS in the manual. This wastes their time when they could be answerring a legitimate question (and it makes them cranky :rolleyes: ).
|
Re: Annual Reminder--Please Read the Manual!
Quote:
And generally, if a question involves electronics of some sort (ie. electronics, custom circuits, lasers) the rules/specifications/safety concerns are explicitly laid out in the manual! |
Re: Annual Reminder--Please Read the Manual!
Quote:
It's fine by me if the Q and A isn't intended for pre-vetting a extremely specific design, but if questions like "can we hang off the side of the bridge" won't be answered there, then I'm confused as to how the Q and A really serves a purpose. |
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
My favorite answer -"Carbon Fiber is not wood." Last year, somebody asked about the bump. The reply "there is no bump on the field" I do remember there being some funny ones in the old Q and A though, like what's underneath the scoring table, and the answer went all the way to the center of the earth. I'll see if I can find it. |
Re: Annual Reminder--Please Read the Manual!
Quote:
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
Obviously, a picture can be flawed, and the judgment given based on a flawed picture will be flawed. That said, is the proper way to address that really to take a blanket approach of "we will not give rulings on the legality of specific designs?" I think that this cannot possibly be the best solution. |
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
Basically, I feel that the line should be drawn at analyzing pictures/actual designs. Obviously, in the case of 118, that was a fault of the GDC's in my opinion, because the GDC didn't expand on the definition of "grab, grasp, grapple". Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Quote:
EDIT: If you mean the regular robot inspectors, no. If you mean overall safety of the event...that's different. |
Re: Annual Reminder--Please Read the Manual!
Quote:
|
Re: Annual Reminder--Please Read the Manual!
Guys,
I included judges to the extent that the judged awards are part of the manual series. As to rulings on robot design, the GDC (and the Q&A) cannot make a ruling based on a description given by the team. The description in most cases is flawed (in favor of a positive response) and thus a decision based on that description will be flawed as well. I can tell you that over the years, teams have sent me pictures of assemblies on their robot that look nothing like the picture when viewed in person and in context with the rest of the robot. Making a decision in person is often difficult until the robot is viewed from all angles. Think about the team that takes a picture of their mounted bumper and asks if it meets the robot rules. From the picture all looks fine but we cannot see that 20" of the bumper is unsupported by robot frame because we can't see behind the bumper in the picture. Just think about the daunting task faced by those who must respond to the Q&A and take a look at how many questions that you can answer actually are asked by teams. |
Re: Annual Reminder--Please Read the Manual!
Quote:
Safety advisors wear green shirts. |
Re: Annual Reminder--Please Read the Manual!
Now that we all have the manual in our (digital) hands, I'd like to bump this thread up. Ctrl+F should be your best friend right now.
|
| All times are GMT -5. The time now is 08:41. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi