![]() |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Quote:
|
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Maybe I'm mistaken, but I can't find it anywhere. I took it to mean that any time a team went into the goal more than 3", it was automatically assumed to be intentional, and a DQ. |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Please take a minute to look at the wording of the rule if you have an issue. Also if you want clarification bring it up at the Drivers meeting on Thurday or Friday where the ref should address it to the whole group. |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Cars are designed to withstand a 5mph collision (rammed) without damage to their bumpers, and many cars can take 10mph with no structural damage. FIRST has provided a clear rule book of their own. Using kinetic energy (impulse) is allowed to move an opponents robot. This has been in the rules since the kickoff meeting. If you want to be able to score during aggressive play, you will need a tracking system that can quickly acquire the goal, lock onto it, tell your driver when to fire, or a system that wont fire if target lock has been lost. Standing at the freethrow line people can shoot baskets all day long - what is the record now, a couple thousand baskets in a row? In many ways this game is like football: if the quarterback has the ball and is about to throw it, he's fair game to be 'rammed' to the ground. Quote:
|
Re: Rules that are [not] getting called at Regionals, the +s and -s
I don't recall the high speed ramming rule NOT applying during the autonomous period - did I miss that?
In my opinion, the argument will rage on because there are as many opinions as there are teams when it comes to defining ramming - and don't expect that the ref's even see this the same way amongst themselves. So, just ask for as much clarity regarding all aspects of this AT THE DRVERS MEETING, and pay attention to WHAT GETS CALLED. I, for one dislike robots pushing on each other, but that's probably because I have to fix the thing after it gets broken. So, there will always be folks that are unhappy with the interpretation and execution of calling or not calling this difficult to measure infraction - but as long as it is being called consistantly AND that every team was clearly communicated with as to what is and what isn't going to be called - that is all we can ask for. |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Nice to know. :D How many of said BAE regional teams are coming to compete against us in Hartford again? Quote:
I know cause it was at NJ. |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
|
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
I would penalize the robot pushing the other team into the goal for the simple fact that if red is being pushed into a red goal by a blue bot, the driver for the blue bot is at maximum 20 feet away from the robot behind the player's station wall and knows exactly what they are doing, and should be penalized in the name of a safety violation. If they were across the field, and pushing, then it would be hard for them to see what they were doing and I would hesitate to give anyone a penalty. |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
|
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Quote:
|
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Quote:
Quote:
|
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
Long distance does not exclusively mean a cross-court shot. "Long Distance Ramming" has been repeatedly interpreted as meaning "more than about 3 feet away" by the referees. I don't know if anything has changed between last year and this year, but last year they called ramming like that. I saw quite a few hits from a few yards away at VCU. The rule is much more akin to hockey than football. In hockey, body checking is alright, as is checking someone into the boards, while "Boarding" occurs when the player contributes an excessive amount of kinetic energy into the hit (usually determined by the skates leaving the ice). Ramming is the same way. The intent of the rule is to keep "bonejarring" hits to a minimum. I've also heard that a good rule of thumb is, "If the hit makes you wince, it's probably too much." |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
pushing rather than tipping or lifting. Neither offensive nor defensive wedges are allowed. All parts of a robot between 0 and 8.5 inches from the ground (the top of the bumper zone – see Rule <R35>) that might push against another robot must be within 10 degrees of vertical. Devices deployed outside the robot's footprint should be designed to avoid wedging. If a mechanism or an appendage (a ball harvester, for example) becomes a wedge that interferes with other robots, penalties, disabling, or disqualification can occur depending on the severity of the infraction. Now as you know Tristan and I love to argue rules and wording. This is my interpretation. As for speaking to the ref, it was after a match where people were dumping balls. The head ref had already ruled about the legality of these robots. I did NOT have any influence or input on the issue. I believe that the talk was later on on Friday. The ref was calling as per the head refs ruling. As you know also, that many people talk about rules and ideas and interpretations during events. This is not new or unGP. |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
• Rule <R35> in Section 5.3.4 establishes ROBOT BUMPER ZONEs. Any contact within this zone is generally acceptable, with the exception of high speed long distance ramming. Where was this quote from? |
Re: Rules that are [not] getting called at Regionals, the +s and -s
Quote:
|
| All times are GMT -5. The time now is 14:59. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi