![]() |
Referee not knowing the rules
I hate to come here to complain, but I have heard many points about the referees not knowing the rules and just had my first experience with this at the MSHSL state championship (Minnesota). We were competing in eliminations (I won't state the teams) and one of our alliance partners were blamed of touching another robot that was in the safe zone. They called a technical foul on us, but it should have been only 3 pts, because (if I'm wrong, just say in the comments) if they were loading, that's 20 pts, but if they're just in the safe zone and getting prepared to load, it's 3, I may be wrong. This costed us the match. In the second match, one of their alliance partners was trying to block our full court shooter by extending an 84 inch blocker up, this is totally ok, but they weren't always in their auto zone. Myself and another alliance partner began to tell the ref during the match that he couldn't do that, that it was a technical foul. Right at the end of the match, the ref finally got the point and brought it up to the head ref. After the match was over, we lost by about 8 pts, but they didn't give us the multiple technical fouls they had, because they 'didn't see it.' We ended up getting 3rd in state, but this really frustrates me. I thought that the refs should have known the rules a bit better than what they did. thoughts?
|
Re: Referee not knowing the rules
Quote:
|
Re: Referee not knowing the rules
I understand where you are coming from, but as I was on the field I noticed multiple times in which the team wasn't making an attempt at getting back to their auto zone, sometimes they were, but I remember them being at about half court with their blocker up and no one by them. I know it's over and done, but I thought I would bring it up. Thanks for the input
|
Re: Referee not knowing the rules
We all know it's frustrating when you see something the ref doesn't.
Quote:
Quote:
I can tell you regarding the refs (As I know all of them)... this wasn't their first show this season. Or even their second. I'm pretty sure they all were at both the Duluth and Minneapolis regionals. Additionally, I know the technical for a blocker being out of the autozone did get called earlier during at least one qualification match (I saw it happen, saw the flag, and shared comments between matches with the refs that that particular foul was the difference in the score between a win and a loss). Again, it sucks to see something that the refs didn't, or expect a foul to be called when it isn't, but unfortunately that's the nature of the game. |
Re: Referee not knowing the rules
Ok, so I was wrong on the loading, my apologies. I wasn't sure about it but that's what I thought the rule was, and I'm not sure whether or not it was intentional or if someone pushed them into them, I was on the other side of the field so I'm not sure. Yes, it is unfortunate, but this is just like a sport and you have to play it by the refs, and sometimes, stuff happens.
|
Re: Referee not knowing the rules
Quote:
Relavent Rules: Quote:
Quote:
Quote:
Quote:
Quote:
Also, I hope you didn't leave the alliance station, because if you did then you should have been red carded. If you didn't leave the alliance station that means you were yelling at the ref, which violates G-18. Quote:
|
Re: Referee not knowing the rules
Actually, I would prefer if someone told me that something was happening. In sports, if something is happening that the ref doesn't see, obviously you wait until the play is over to tell them, but you do tell them. In this case, we knew that they wouldn't change the score unless we told them during the match, so we did our best to have them realize what was going on. And I'm not sure if it was accidental or not, I couldn't see it, it may or may not have been, but we got the foul.
|
Re: Referee not knowing the rules
You are also talking about a set of rules about which there has been a lot of difficulty this season. We also have a full court shooter and found that G30, G22 and G18-1 were called differently at every event we attended - and were generally inconsistent at each event (including at Championships). They calls have varied so much, that I have seen something one match be called a technical on the defending bot, then, when the exact situation arises in another, it is a technical against the FCS. I have been somewhat privvy to discussions about this rule amongst referees and have learned that they disagree (yes, even different head referees) as to how several scenarios should be called. From what I can tell, most referees recognize the ambiguity in the rules and, frankly, hate the G18-1 rule. The best bet is to talk to referees before competition and get clarification as much as possible.
Example of ambiguity: Defender bot puts up 80" blocker. FCS cannot shoot over it. FCS loads hopper and driver to the autoline. Blocker stays in front of FCS, but does not have the power to push back. FCS crosses autoline, pushing blocker across in the process. FCS then shoots from loaded hopper. G22, says that the blocker cannot be across the autoline - period. G18-1 says that the FCS cannot have a strategy with the sole purpose of causing a tech. Now what? The blocker was shoved across teh autoline - maybe it could have avoided it, but it certainly was not intentional and not even under its own power. Does it really deserve a tech? At teh same time, if the blocker were 20" shorter, there would be no issue. Does the attachement of, say, a pool noodle suddenly make a defender robot immune to being shoved out of the way? At teh same time, teh FCS did force the blocker across the line - it employed a strategy that drove the other bot to a foul. However, the rule states that it cannot employ a strategy with the SOLE purpose of drawing the foul - it did go up and shoot. It could not shoot before, as it was being blocked. Are we going to make it illegal for the robot to try to find an open shot? On Archimedes, this situation was ruled like this: No foul against either side - the defender has the right to defend and the FCS has the right to find an open shot. However, once across teh autoline, the tall bot must immediately return to its autozone, lest it be called for a technical. However, even on Archimedes, we had one match in which the head referee told us that if we (FCS) were to persist in doing that, we'd be charged with a technical - this was resolved after a long discussion. Other questions: What if, after crossing the auto line, the FCS were to shoot and the blocker, due to its tall (and now illegal) height, were to inadvertently block a disk or two? In other words, let's be kind to the refs on this - the real issue is an ambiguity in the rules. |
Re: Referee not knowing the rules
OP, you will have more credibility if you link to videos of the matches you mention. I've learned that students on the field (even our own) often misinterpret what is happening because of their perspective.
In one controversial match of ours, from last year, a mentor from the opposing alliance wrote a very detailed description based on a first hand account from one of his drive team members. The only problem was that the video showed that the account was completely wrong. I've seen things like this happen on CD often enough that I don't believe any claims about too harsh or missed penalties unless those claims are backed up by video. I myself have had the experience of seeing a ref miss a penalty which I thought was clear as day. Then I go back and review the video and see that the ref was right after all. |
Re: Referee not knowing the rules
Quote:
I've felt this as a ref, too: seeing an interaction that I know can be diagnosed by every coach on both alliances, but I just plain could not see. At the same time, I've been yelled at by teams for what basically amount to optical illusions for them. Every incident type has happened more this year than in any other game whose field I've stepped on. It's painful. Refs at a level like MSHSL know the rules, they just have to interpret them based on what they see on the field and what they understand them to mean. Particularly with so many "intentional/purposeful/consequentials" this year, it's really hard to say that a call is wrong...or right. Do be careful of accusing anyone of not knowing the rules without having checked them yourself, though. |
Re: Referee not knowing the rules
Quote:
Your second point is only slightly more clear cut. It is still somewhat a judgement call. I believe they went over this in the drivers meeting at all 3 Minnesota competitions I’ve been to this year. If the 84” robot was pushed out and tries to get directly back in, there is no foul. If they make any other move to pick up a disk, play defense, play offense, or interfere with other robots it will be called a 20pt technical. I watched a robot get called for 2 of the 20pt technicals in 1 match for driving outside of their auto zone at the MSHL tournament. The refs were definitely aware of this penalty so they either didn’t see it or deemed that they were pushed out and trying to get back in. I’m sorry you feel your season ended because of referee calls. You guys had a great bot and were good competition! |
Re: Referee not knowing the rules
Quote:
|
Re: Referee not knowing the rules
Quote:
|
Re: Referee not knowing the rules
The easiest thing to do in the world is to stand on the sidelines, point a finger and criticize.
If you really think the refs are so bad step up and show them how it's done. Volunteers are in short supply and we always need more. |
Re: Referee not knowing the rules
Quote:
|
| All times are GMT -5. The time now is 18:00. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi