REALLY IMPORTANT REMINDERS...
NO REALLY, YOU SHOULD READ ALL OF THIS:
Payment for your qualifiers is due by FRIDAY!!! By Friday your team must have done one of the following, or risk being dropped from your events:- Mailed a check to Coconino High School
- Address is on your invoice
- Please send an email to ftc.arizona@gmail.com letting us know when the check was mailed
- Paid with a credit card to Carrie in the CHS bookstore
- Directions for paying by credit card are on your invoice
- Sent a copy of your PO request to ftc.arizona@gmail.com
Please remember to include your team number with all email and phone correspondence.
Dean's List Nominations for Glendale, Tucson, and Phoenix are due by 11:59 PM Eastern Time on Thursday. See the Dean's List page for more details on how to nominate students.
Your Team Name that is registered with FIRST is the one that the scoring system will use for displays and matches. We DO NOT have a way to change this manually in the scoring computer. Please check your team information on your dashboard at least 1 week prior to your event and confirm your name is spelled exactly how you want it displayed at the event!
Important Game Play Information from your Head Referees
Congratulations to all teams completing this past weekend in the White Mountain Qualifier! I wish I could have joined in the fun, and am looking forward to the rest of the season! Here a few items of note that we would like to pass along to teams as the competition season gets rolling along…
Latching and Deployed Situations:
Latching and Deployed Situations:
If a team has any questions or is not sure about what constitutes Deployed or Latched for this year’s challenge, please review the following:
Game Manual II, Section 1.4 – Game Definitions for “Deployed” and “Latched” Note there is specific wording on what constitutes a “Latched” robot – “completely supported…” “and is not in contact…” is key to the sentence in the definition.
Game Manual II, Section 1.5.1 Pre-Match – 1 “Latched to the Lander” – This is very clearly worded on pre-match starting condition for a latched robot.
Game Manual II, Section 1.5.4 End Game – 1 “Robots Latched” – Note that the first sentence specifies “…Deployed during pre-match setup or in the course of game play…” see definition of “Deployed” (i.e. a robot starting the match on the field in the alliance landing zone under the bracket is deployed and eligible for the endgame latching score, and a Robot starting in a latched configuration, that deploys during Driver Controlled period is eligible for the end game latching score, but a robot starting in a latched configuration that does not move or cannot deploy due to some issue is NOT eligible for the end game latching score.
Game Manual II, Section 1.6.3 Game-Specific Rules - Remember there are specific rules affecting blocking , interfering and latching see <GS5>, <GS6> and <GS7>.
FTC Forum Q&A: There are a number of good scenario questions, so make sure to stay updated on the forum posting, but specific to this topic, I would direct attention to the forum Game Rules – End Game Q&A #4 dated 11-05-18 with Subject “Latched Robot - <GS5> Blocking Access to Scoring in the Lander and <GS6> Interfering with Scoring at the Lander” There is some good feedback on how situations will be called in this post. Please take time to read through it.
Landing Situation:
Game Manual II, Section 1.4 – Game Definitions for “Deployed” and “Latched” Note there is specific wording on what constitutes a “Latched” robot – “completely supported…” “and is not in contact…” is key to the sentence in the definition.
Game Manual II, Section 1.5.1 Pre-Match – 1 “Latched to the Lander” – This is very clearly worded on pre-match starting condition for a latched robot.
Game Manual II, Section 1.5.4 End Game – 1 “Robots Latched” – Note that the first sentence specifies “…Deployed during pre-match setup or in the course of game play…” see definition of “Deployed” (i.e. a robot starting the match on the field in the alliance landing zone under the bracket is deployed and eligible for the endgame latching score, and a Robot starting in a latched configuration, that deploys during Driver Controlled period is eligible for the end game latching score, but a robot starting in a latched configuration that does not move or cannot deploy due to some issue is NOT eligible for the end game latching score.
Game Manual II, Section 1.6.3 Game-Specific Rules - Remember there are specific rules affecting blocking , interfering and latching see <GS5>, <GS6> and <GS7>.
FTC Forum Q&A: There are a number of good scenario questions, so make sure to stay updated on the forum posting, but specific to this topic, I would direct attention to the forum Game Rules – End Game Q&A #4 dated 11-05-18 with Subject “Latched Robot - <GS5> Blocking Access to Scoring in the Lander and <GS6> Interfering with Scoring at the Lander” There is some good feedback on how situations will be called in this post. Please take time to read through it.
Landing Situation:
Note Game Manual II Section 1.5.2 Autonomous Period – 1. Landing.
Specifically, to score a landing, contact with the lander support bracket is a critical piece of the score. Team need to make sure it is clear to the referees that there is “no contact” with the bracket. Since we do not enter the field to check scoring conditions, we must rely on what we can see from outside the playing field. If it “looks” like the robot is touching a bracket to a referee, chances are the landing for autonomous points will not count.
I hope this helps clarify some of the questions that may be in your minds as the qualifiers begin.
Questions/clarification: And as always, please feel free to contact me should you have any questions or concerns. When you are at a tournament, please remember that if you have a question about a call or an issue that arises during the tournament there is a protocol for addressing your concern – send a youth team member to the Question Box to discuss the issue with the Head Referee. Please do not seek out the Tournament Director or the Affiliate Partner to discuss game rule interpretations, remember they are very busy with the tournament operations at the Big Picture Level, and will send you to the Question Box...
I look forward to seeing teams at Gilbert this weekend and wish all safe travels and a wonderful Thanksgiving Holiday!
I hope this helps clarify some of the questions that may be in your minds as the qualifiers begin.
Questions/clarification: And as always, please feel free to contact me should you have any questions or concerns. When you are at a tournament, please remember that if you have a question about a call or an issue that arises during the tournament there is a protocol for addressing your concern – send a youth team member to the Question Box to discuss the issue with the Head Referee. Please do not seek out the Tournament Director or the Affiliate Partner to discuss game rule interpretations, remember they are very busy with the tournament operations at the Big Picture Level, and will send you to the Question Box...
I look forward to seeing teams at Gilbert this weekend and wish all safe travels and a wonderful Thanksgiving Holiday!
Best to all,
“Ref Rich”
Rich Gomez
Now that Qualifying Tournaments are underway, a running list of event results and the roster for the Championship is posted under Quick Links to the right.
White Mountain Event Results
Congrats to all the teams that competed in the first event of the season! Thank you to Team 8995 Jaegers Robotics for putting on such an awesome event!
Inspire Award: 10984, Beep Patrol
Winning Alliance: 8081, Knights of the Lab Table & 10984 Beep Patrol
Finalist Alliance: 13517, CPR & 10369 Robosapiens
Think Award: 14571, The Marvels
Connect Award: 12892, Juggerbots
Rockwell Collins Innovate Award: 13517, CPR
Design Award: 12241, Paragon Panthers
Motivate Award: 14436, Roaring Robotics
Control Award: 8081, Knights of the Lab Table
Judges Award: 15158, Rambots
Teams Advancing to the Championship:
10984, Beep Patrol
12241, Paragon Panthers
12892, Juggerbots
Good Luck to all the teams competing at the Gilbert Qualifier this weekend!
No comments:
Post a Comment