![]() |
Re: Predictions Week 3: Creating Flow
Quote:
We had teams adding extensions to block full court shooters throughout elims, much to the dismay of the full court shooter. ::rtm:: It seemed easy for the inspectors to either reweigh quickly or look at their previous weight and determine they would still be in compliance. |
Re: Predictions Week 3: Creating Flow
At GKC the (experienced and knowledgable team of) inspectors were available near the field during elims and were granting rapid re-inspections as needed.
|
Re: Predictions Week 3: Creating Flow
Quote:
|
Re: Predictions Week 3: Creating Flow
Quote:
|
Re: Predictions Week 3: Creating Flow
Quote:
|
Re: Predictions Week 3: Creating Flow
Quote:
Thanks for the feedback everyone; it's nice to know I wasn't off the deep end on this one. |
Re: Predictions Week 3: Creating Flow
Quote:
I'd like to have seen your 30 point climber work a little more though, but stuff happens... I should point out that, if you ever have a problem with an inspection call, your first move should be to ask to get/cite the rules. There were some other calls over the weekend where teams immediately asked for the rule to be cited or cited the rule themselves, and got the proper ruling. Just my $0.02 |
Re: Predictions Week 3: Creating Flow
Quote:
Second, yes as to the rule, but I don't know how FIRST could regulate the amount of time the T10 reinspection takes--nor am I sure I'd want them to. Unfortunately, I don't see a whole lot of regulatory recourse for an unecessarily long (or for that matter, unnecessarily short) reinspection. I don't mean that as a complaint--if anything I guess I mean teams might want to keep such scenarios in mind. |
Re: Predictions Week 3: Creating Flow
Quote:
In general, inspectors will do everything in their power to get teams ONTO the field, not keep them OFF the field. If you've ever hung around an inspection table on practice day, you'll see the LRI directing RI's to help teams that are in danger of missing their first Qualification matches. Not every RI is perfect, and quite frankly some would be better placed in other volunteer roles. That is why every regional has an LRI in attempts to keep team experience as consistent as possible. If you are having trouble with a particular RI, please request the assistance of your LRI. Robot Inspectors are your friend! -Mike PS. I personally had a blast robot inspecting for the first time this year. What a great way to get to know teams and the incredible students who know their robots so well! I highly recommend any post-high school FIRST alum give inspecting a try! |
Re: Predictions Week 3: Creating Flow
Quote:
|
Re: Predictions Week 3: Creating Flow
When something weird happens, send a pre-college student to the question box for further clarification.
|
Re: Predictions Week 3: Creating Flow
Quote:
When a questionable call is made, a call is missed, or we see something obviously illegal happen, we send a student (most often our driver) to the question box. Usually, he's sent there with/by a mentor who stays within ear shot and has a tablet with both the rules and Q&A at the ready. This doesn't always help with a call for the previous match, but we've found that with persistent questioning, the calls will improve over the course of an event. Also, on the subject of changes and repairs done between elimination matches: Quote:
Quote:
In 1640's case, their machine had a camera. The camera was in a less than ideal spot, so they made the decision to move it. IMO, that's CLEARLY 're-configuring' a mechanism and therefore legal. It wasn't like they didn't have a camera to begin with and suddenly decided to add one... (as is often true with blocking mechanisms) Any way, it seems like we should all keep our rule books at the ready. We're going to need them. |
Re: Predictions Week 3: Creating Flow
Quote:
|
Re: Predictions Week 3: Creating Flow
Quote:
|
Re: Predictions Week 3: Creating Flow
Quote:
Regardless of how it's being interpreted., I think it's pretty clear tweaking a camera's position is legal under T08/T10. Quote:
|
| All times are GMT -5. The time now is 18:36. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi