|
|
|
| I may be mere steel but my heart melts when you're around. |
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#46
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
Quote:
|
|
#47
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
The question comes in with inspectors, particularly rookie inspectors. I know at my regional in Duluth over half my inspectors were rookies, and I know that a lot of stuff was missed initially and we worked the entire weekend to catch it and get it fixed. |
|
#48
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
|
|
#49
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
And keep in mind that anything one of the key volunteers (including me) says on a public board like this towards a question like the one posed is likely to be rather vague... the last thing I want to be doing is throwing another LRI or Head Ref under the bus by disagreeing with them when I wasn't present and can't possibly have full information as to the situation. That's one big reason why I'm hesitant to give a straight yes/no answer, and instead prefer to explain the process we go through and which rules come into play.
|
|
#50
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
What I hope comes out of this is First puts out re-inspection process that is workable. Franks' blog says they are working on this. Last edited by FrankJ : 17-04-2014 at 16:07. |
|
#51
|
|||||
|
|||||
|
Re: [FRC Blog] Orlando Incident
Quote:
As written, the implication of T6 is to keep teams that have never been inspected from coming onto the field: Quote:
Thus I think it is a stretch to make T6 all encompassing and suddenly say that it applies to any instance in which a robot may be non-compliant with the rules. There is zero precedent before the last two years to say this is the case. I have seen numerous cases of teams that were non-compliant with the rules during a qualification match that were told to remedy the situation before going out again, but never have I seen a team that got inspected and was temporarily non-compliant be DQ'ed after the fact (besides 973 last year, but that could be considered an isolated event and not a change in policy). The precedent was only set this year when HQ decided specifically that this was the appropriate action to take (or backed up the Head Ref/LRI's decision). Perhaps FIRST/the GDC's standpoint is that any non-compliant robot that competes after being inspected initially should be DQ'ed immediately after said match, or whenever it is brought to the attention of the LRI. If it is, they should explicitly say so, as well as who the burden of proof is placed on when it comes to getting inspected. It is completely unreasonable to place that burden on a team acting in good faith that has approved any changes with an inspector. If the requirement is for the LRI to pass changes, then that should be explicitly stated. At SVR and Waterloo we have requested that the LRI inspect changes that we make to our partners, for fear of getting burned by exactly what happened to 233 (and previously 973). At times we have felt like their time is being wasted with trivial changes, but it is the only way for us to ensure there is no blowback later. Last edited by Cory : 17-04-2014 at 16:44. |
|
#52
|
|||||
|
|||||
|
Re: [FRC Blog] Orlando Incident
Quote:
The appropriate resolution probably will have to come down to clearly defining what "inspected" means, and that sounds like what the documentation mentioned in the blog is supposed to do. I don't want to aim negative thoughts toward a volunteer without knowing more, but I need to maintain a distinction between "an inspector said we were good" and "our robot passed a reinspection after we added ballast." |
|
#53
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
We could be like Golf where filling out your score card wrong can get you into trouble but that would be ridiculous. T6 needs to be cleared up. If a robot is suspect to be gaining an advantage by violating a rule, reinspect the robot to find evidence. We can't be DQ'ing robots with no evidence. |
|
#54
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
|
|
#55
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
Our interpretation was that any examination of a robot by an inspector could constitute an inspection, if the inspector elects to treat it as such.1 The process above was intended to ensure a balance between the need for teams to have legal robots, and the need for teams to play. Granted, the rules were slightly different in those years, but I think the core rationale is still consistent with the current version of those rules. (I would be interested to learn whether FIRST supports that open-ended definition of an inspection, or whether they intend to define the types and scopes of various kinds of inspections more rigourously in the future. Certainly we would benefit from better definitions of the process of inspection, but I don't think it's actually necessary to define separate powers for every kind of inspection—that's too complex, and could cause perverse outcomes.) Quote:
1 Since that is a subjective standard, it was also important to make clear to teams that an inspector had observed the violation, and was mandating compliance. Note that we didn't address the question of an inspector overlooking a defect by treating that observation as not having been an inspection; some guidelines on that front would be welcome. Last edited by Tristan Lall : 17-04-2014 at 17:18. Reason: Adding footnote. |
|
#56
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
As an LRI I have found many teams to make changes without being reinspected. When this has happened in the past I have approached the team and identified the issue. I also make sure that the head Ref knows what was said and what was expected. If the team did not get reinspected at which time I notified the Head Ref they could be penalized.
This year was the first time that I was involved with teams being DQed. They were both during qualification rounds. The first one was with a team damaging the carpet. I spent time with them and when a solution was in place I left them and told about 8 students in the pit that they had to be re-inspected before going out to play again. Two other Inspectors also talked to them about re-inspection. I happened to go out to the field when they were playing. I asked all of my inspectors if they had re-inspected them and the answer was no. I informed the Head Ref before the scores were announced. We both went and questioned the team and they admitted to not being re-inspected. Red Card and DQ followed. The second was a rookie team that had added a blocker to their robot. Again I noticed during the match. I would have waited till after the match as they were rookies but the part added to the robot did affect the match. Same process with Inspectors and Head Ref. Same result, Red Card and DQ. I felt really bad for the alliance partners and 1 team was involved with both DQ's. I read and re-read the rules and next morning (Saturday) I spoke with the FTA and Head Ref. I requested a ruling from HQ on the DQ's to the 4 teams not in violation of the rules. I pleaded my case to the FTA who took it to HQ. Final ruling, only the robots that had made the modifications got a Red Card and the other robots got their points back. I guess the point is that FIRST is fair. We as LRI's and Inspectors do our best to keep all teams competing on a even plain. I know as an LRI I tell all of my inspectors that if in any doubt ask me. If I find that an Inspector makes a mistake I try and show it to them and use it as a learning experience. I am even willing to put it here in writing that "I HAVE MADE MISTAKES". For those that know me, don't say a word. I will also say that all of the events I have been involved with The LRI, Head Ref and FTA work together to make each event be the best that it can be. |
|
#57
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
And if so, did they publish a version of that ruling in the Q&A or in an update? |
|
#58
|
|||||
|
|||||
|
Re: [FRC Blog] Orlando Incident
Guys I can't believe you are even discussing this. A repair is a repair and except for items that Jon pointed out that could potentially damage the carpet, a repair of a damaged mechanism with an identical mechanism is a repair it is not a modification. If the arm is an upgrade part, then the replacement is a modification and needs to be reinspected. Re-inspections and reweighs are still free.
We will be using a form similar to that posted earlier in this thread. The team does not fill out or handle the paperwork. Re-inspections need to be carried out in the pit during qualifying. Following lunch on Saturday, we will move the paperwork and re-inspections out to the dome and carry the paperwork with us. We will have all documentation available during eliminations. To Be Sure... If you make a change, a modification, remove anything, even think about taking something off and putting something else on, come and ask us. We are really nice guys and we want you to play and win. |
|
#59
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
I hope this never happens again to another team - it really hurts. PS: The report from the Florida today was there during the entire process and it was her own opinion to write the article the way she did. No one called up the paper to whine about anything. These are my views only, and not of the Pink Team, Exploding Bacon or Cryptonite (sp) |
|
#60
|
||||
|
||||
|
Re: [FRC Blog] Orlando Incident
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|