![]() |
G27 Standard
I hope for the Championship, there is a clear standard for G27. During the WI Regional, the G27 rule was updated, and any high speed ramming was called.
During Midwest Regional, only damaging high speed ramming or "inhibition", was called. The problem with damage is: It is really hard for the Ref's to see damage real-time. Unless a piece comes flying off, or gets severely distorted, how can you tell? I hope they update G27 to be a clear standard. If damage is the criteria, then teams should be allowed to show damage after the game. Also, what is the purpose of "inhibition"? If Red prevents Blue from taking a shot, or picking up a ball, why is that not good defense? What is the difference if Red does it full speed, or 1/2 speed? These bots can get up to full speed in one or two bot lengths. Ditto on G28 - Contact inside the frame perimeter. I think this is more of a problem. There is a lot of contact inside the frame perimeter. But, it is really hard to see damage, such as cutting pneumatic tubing. I think almost any contact inside the frame perimeter should be called. The only exception being if the other bot initiated the contact. |
Re: G27 Standard
Quote:
|
Re: G27 Standard
Quote:
These calls were made in week 5, after most or all of the rule changes had been made. While these calls leave me frustrated and uncomfortable, I'd like to hear another opinion because I can't figure out what the ref was thinking. |
Re: G27 Standard
Quote:
|
Re: G27 Standard
Quote:
Quote:
|
Re: G27 Standard
This call will be like so many others this year and will never get better. Another from St. Joe was in Q47 on us at 2:06 as seen in the video here
Our "wings" are fully within our perimeter unless they are outside of it by the full 16" of extension we gave them. But, a judgement call is a judgement call. The problem is when a judgement call can take away from students levels of inspiration. Some students expressed that it is hard to have faith in something when a call isn't made on something as black and white as a g28, and also when they are left as grey as a g27. Edit to add: I think that St. Joe was the first time I saw the game played how it was intended to be played. Rough but not excessive. It was made up of some fast offense, some harsh defense, and mostly clean play sprinkled in between. I don't want to derail this thread away from the OP's point. The only thing to take from my post in regards to that is that this will always be an area decided by the ref on that field, and I don't see how you can put a solid standard to it. Unless we all have impact measuring gauges on our robots, or refs are given radar guns to measure speed prior to impact. Either way, those are more things for a ref to pay attention to, and they have enough on their plates as is. |
Re: G27 Standard
Quote:
Were you given a foul for a G24 and an extended G24 technical foul for continually being outside the 20" perimeter? This is the same situation that happened in Waterloo. Very unfortunate. It seems that at every event there has been calls that are missed as well as not consistently called. Let alone the FMS... There were similar issues at our event in HI. We left the field with our 1/8" thick 2x3 pickup system bent and all the welds broken. I think the small warning in the manual for designing your robot systems robustly should of been bolded and in multiple blue boxes.. A rough game this year is an understatement. |
Re: G27 Standard
Quote:
I believe the technical was actually called here (notice the ref in the bottom left). I can't quite figure out why it was called though, considering how many things robots were getting away with at St. Joe. The way he looked inside 2337 makes me think he saw some kind of damage not visible to the camera, but then again, I don't really know. I really wish things had gone differently and that our win had not been because of fouls. It was great playing with and against you guys and hopefully we'll see you again next year for a "rematch". |
Re: G27 Standard
Quote:
Quote:
Signals all refs use: "Tomahawk" used to count down a pin, wave red/blue flag for a foul, if Technical foul, follow the foul call by crossing arms in an "X". Pointing at the violator is often used as well. (Some refs will also point at a loose dead ball; most will give a "safe" signal after a pin clears though I didn't see one in the first video.) |
Re: G27 Standard
Quote:
Quote:
|
Re: G27 Standard
Quote:
I hope at St. Louis, there are 9 refs for each match. Two at each pad, and the Head Ref. The 4 pad refs watch the ball, and the other 4 refs watch their area away from the ball. |
Re: G27 Standard
Quote:
|
Re: G27 Standard
Quote:
That seems like an awful lot of refs to be watching the field. I think maybe one or two more at most would be useful. But whatever way it goes, hopefully the rest of this season works as it should and teams gain everything they can out of the experience that this year provides. |
Re: G27 Standard
Quote:
|
Re: G27 Standard
I'm curious how you guys would have called this sequence of events in Semi's 2-2 at the OSU district. I'm starting it right before the g28 foul occurs in the lower lefthand corner. It was called on blue 3712 as time expired.
http://youtu.be/ECiXrExJupg?t=2m28s |
| All times are GMT -5. The time now is 05:03. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi