|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||||
|
||||||
|
From numerous posts in the last two days, it is clear that emotions are high on two particular topics: entanglement and aggressive play. I'd like to guide that emotion into something positive.... so lets try this:
Lets wind the clock back -- it is now the Monday after the first week of regionals... you are on the Game Committee... you decide that two new rules are needed for Tuesday's team update: <G34> needs to be written to address what should occur in cases of accidental entanglement <G35> needs to be written to address overly agressive play Take a shot at one or both! What would you write? (Please give some thought before you post and make your rules something that can actually be called by refs -- don't consult a lawyer to come up with your wording -- and for the sake of this exercise, assume that all the information that came in all of this season's updates is already in place at the time you write these rules) Thanks! ![]() Aidan |
|
#2
|
||||
|
||||
|
Re: You write <G34> and <G35>
<G35> If a team exercises the the use of overly aggressive play (refer to rule <G32> for examples), the ref may, at his or her discretion, present the offending team with a yellow card. It the offending team continues this action or he will be presented a red card which will disqualify their robot for that match. Recieving two yellow cards in one match will result in the issueing of a red card in the disqualification for that match. Teams that have recieved a yellow or red card in a match will carry the "first" yellow card for their next two matches. If they recieve a yellow card in one of the following two matches they will be disqualified for that match. Two red cards will result in disqualification from the tournament.
A little rough but I like it. A think it would work real good too. |
|
#3
|
||||
|
||||
|
Re: You write <G34> and <G35>
While I feel that this idea is hopefully an "unwritten but commonly known rule," one thought for a rule to prevent overly aggressive contact to a disabled team would be the following:
In the event that a robot becomes disabled by any means, said robot should no longer be aggressively contacted by any other robot. Aggressive contact shall be defined as any forceful, apparently intentional contact made when the disabled robot is not in a position to prevent an opponent from scoring. If the disabled robot is preventing the opponent from scoring, the opposing team may attempt to move the robot only as far as necessary and only in a manner deemed by the FIRST officials as non-threatening to the welfare of the disabled team. Again, I hope that this rule is completely unnecessary and is commonly understood without being expressed in writing. The words may not be completely concise, but the intention is hopefully clear. Last edited by Jason Kixmiller : 19-04-2004 at 19:37. Reason: Addition |
|
#4
|
||||
|
||||
|
Re: You write <G34> and <G35>
I wouldn't change anything but would note that for next years rules I might add something. It is my belief that rules should not be made or altered after the start of competition as build rules should not be changed after building has started. Sorry for using this as a soapbox but it needs to be stated.
As for the rules on aggressive play : Any robot ramming or pushing another robot, deamed by the ref to be unable to retreat to prevent damage, that continues after a refs warning will be shut down for the remainder of the match and that robot will recieve a DQ for that match. As for entanglement I believe that there is already a rule that addresses this to my satisfaction. |
|
#5
|
||||
|
||||
|
Re: You write <G34> and <G35>
pushing and pinning vs ramming. Robots may push, shove or be pinned only if contact is confined to the bumper zone that extends from 2" to 8" above the playfield on all sides. If a robot pushes against another above/ below or under this area and damage results, or the other robot is toppled, the offending robot will be disqualified for that match.
Ramming is defined as driving into another robot from a starting position of more than 5 feet away. Drivers that intend to push or pin an opponent must first stop within 5 feet of the other machine, then proceed. Any robot that backs away more than 5 feet and then accelerates into another machine will be called for ramming. If any damage or tipping results from ramming, the offending robot will be disqualified for that match. Tipping. A robot is in a defensive postion when it is physically between an opponent and the opponents intended scoring objects or a goal. A robot is in a offensive position when another robot is blocking its path to desired scoring objects or a goal. If a pushing/ shoving or pinning match ensues with two opponents in defensive/ offensive positions, and the rules listed above are not violated, and one or both robots are toppled, then no penalites will be called. However, if a robot attacks another machine from the side or back, when they are not in offensive/defensive postions, and causes it to be toppled, the offending robot will be disqualified for that match. example. Red bot is between Blue bot and its stationary goal. Blue bot is attempting to place the 2X ball on the goal. These machines are in defensive and offensive positions. If one or both fall over as a result of the enusing pushing match, no penalties apply. Blue bot is directly infront of its stationary goal and is attempting to place the 2X ball. Red bot pushes it from the side, attempting to push it away from the goal, or Red bot gets behind it and attempts to latch on and pull it away, and in either case the Blue bot is toppled. Red bot shall be disqualified for tipping, even if no contact outside the bumper zone occurs. Last edited by KenWittlief : 19-04-2004 at 20:23. |
|
#6
|
|||
|
|||
|
Re: You write <G34> and <G35>
(G35) Ramming, smashing, and overly agressive driving shall not be permitted. Defensive manuevering is allowed in the form of obstructing the path and reacting against another robot for no more than 10 seconds. This defensive tactic may not be employed more than twice per match. Robots must not initiate the interaction with another robot by continuously driving from a distance greater than 5 feet away. Continous repetitive interactions will result in a warning to cease the action. Either time, distance, or number of interaction violations will result in 1 warning, and disqualification of the match if a 2nd warning occurs. 2 disqualifications during the seeding rounds will result in disqualification from competing in the elimination tournament.
|
|
#7
|
||||||
|
||||||
|
Re: You write <G34> and <G35>
Boy Aidan, that's a toughie. I really don't think you can write a band-aid rule very well without the rule being too subjective to officiate. I see it causing more controversy rather than less. What one official sees as acceptable, another will see as overly aggressive. It's easy to see when a robot tips, but it's difficult to say "that ramming was just too strong." Ken had some good ideas to add some quantification, but I still say it would be difficult to officiate.
I really think any non-aggression rule needs to be designed into the game. Therefore, I would like to suggest two potential new game features to cut down aggressive play. Idea #1: non-contact zone Some areas on the field (perhaps near the goals or near the scoring objects) have a different color of carpet. The area of the field with the colored carpet is the non-contact zone. It is illegal to contact a robot that is attempting to score or collect scoring objects in the non-contact zone. Each instance of contact will result in a X point penalty assessed to the non-scoring (or non-collecting) team. Idea #2: Contact allowance Each team has a total of N seconds worth of contact/defense time (the actual time can be better determined at a later date). One official is assigned to each team and they carry an electronic stopwatch that is tied to the official scoring system. When contact is initiated, the official starts the timer, when the robot backs away, the official stops the timer. Everyone would know how much contact/defense time is left for each robot by the "Defense Remaining" bar (like a bar graph) underneath their team number at the driver station. Once the bar shrinks to zero, the team is no longer allowed to play defense. The penalty is Y points per extra second of defense that is played (the extra defense time is kept track of by the official scoring system and by the official starting and stopping the official timer). |
|
#8
|
||||
|
||||
|
Re: You write <G34> and <G35>
this thread is getting interesting. In other contact sports the rules were created and evolved over the years because players were being injured and some sense of fair-play had to be explicitly spelled out. In this years games Im seeing posts from several people who went home from events very upset after their bots were damaged or toppled during play, and they were not able to complete their matches.
In terms of other sports, there are many parallels that can be drawn with a FIRST game: illegal use of hands => illegal use of arm/hook/claw... late hit => bashing into a bot when it is not in the process of attempting to score points hitting a player in the end zone or when they are out of bounds => non-contact zone ideas in Chris' post unsportsmanlike conduct => doing a victory spin at the end of a match?! ![]() Last edited by KenWittlief : 20-04-2004 at 10:18. |
|
#9
|
|||||
|
|||||
|
Re: You write <G34> and <G35>
Quote:
FIRST should put together a video of what violations of the "standard rules" look like. Standard rules are tipping, entanglement, damage, destruction, etc. which are included in the game rules every year. The standard rule set is currently enforced by using personal judgment on the part of the referees. This very easily lends itself to inconsistent calls between referees. Very respected people on this forum disagree as to when a certain rule has been broken. It's obvious that the current system doesn't work. If referees had an example of what to look for it would make their calls much more consistent. Currently, a referee makes a personal judgment on whether a rule was broken. The video will give them leverage in being impartial, in their minds, as to when it's appropriate to flag a team. Teams would see the video of violations to the standard rules and have a better understanding why the referees made a certain call. There wouldn't be as much debate as to whether a team was wronged by a referee because it would be less of a personal judgment call and more of a "did this action meet the example" judgment call. In baseball, it would be tough for an Umpire to call a balk, if he had never seen prior examples of when a pitcher does balk. It's rules where personal judgment is used that need examples in order for them to be enforced consistently. Aidan, the rule you are asking for is impossible to write. You can't qualify or quantify the spirit of FIRST, you need to see it by example. Last edited by MikeDubreuil : 20-04-2004 at 10:41. |
|
#10
|
||||
|
||||
|
Re: You write <G34> and <G35>
but if you can put together a collection of video of examples of rule violations, then those videos become the written rules
can you explain what is happening in those videos to a person who can not see? ok - write down what you are seeing and you now have written rules. I think one of the biggest problems this year is the word 'intentional' in the rules. Its very much like the word 'premeditated' in the laws for 1st degree murder - its much harder to prove that someone planned or intended to do something ahead of time than it is to prove that they actually DID the thing. Ive seen lots of posts this year where one team says their bot was tipped or slammed or damaged, and another team comes back and apologizes and says we didnt intend to do that ok - I accept that at face value, but it reminds me of the sport in the Hitch-hikers Guide to the Galaxy, where two opponents are placed in an arena, you attack your opponent, then retreat to a neutral corner and apologize. You are scored both on the viscousness of your attack AND the sincerety of your apology. (im not saying the apologies on CD are not sincere) but this is why 'intend' needs to be removed from the rules and replaced with 'result'. If you are not able to control your robot very well, then keep away from your opponent. Why should you be allowed to topple or damage another teams machine, and win a match - you have in effect disqualified their robot by taking it out of the game, why should you not also be penalized? if I hold a sharp stick right next to your face, and someone hits my hand and I poke your eye out, do you care if I indented to poke your eye out? no. that would be a careless and irresponsible act on my part. If you are going to play in a wild, uncontrollable or rough manner, and you cause the other team to not be able to play the whole match as a result, then you should be penalized, not them. thats whats missing from the current rules - what would it take for a ref to know what a driver intended to do? would he have to hear him say 'Im gonna knock that bot over' before the match? in the end results are what matters - you bean a batter with the baseball then he walks to first base, ALWAYS - it doenst matter where you intended to throw the ball - if you cant throw the ball over the plate, you are going to lose. if you cant drive your bot around the playfield with out reeking havock on the other machines and the field itself, you SHOULD lose! Last edited by KenWittlief : 20-04-2004 at 11:03. |
|
#11
|
|||
|
|||
|
Re: You write <G34> and <G35>
Quote:
A rule which bans tipping based on result will encourage teams to design tippledy-toppledy robots which run into other teams and fall over. In basketball, occasionally players "do the flop" in order to draw a charge. If the rule states that "two robots run into each other, one falls over, the other is disqualified," then robots and teams will "draw the foul." Quote:
Quote:
The thing that makes this rule work is that the benefit to the batter (taking first base) is usually not worth the punishment to the batter (broken ribs, concussion, etc). If the penalty for tipping is disable or DQ, then it is worth my while to design a robot that tips and to design a self-righting mechanism. I can disable one robot by bumping into them and tipping, then right myself, then bump into the other opponent, tip, disable them, right myself and continue the game. Even a five point penalty to the tipping robot would encourage me to do this. Thus, the word "intentional." Another example (from a real match). We were defending the steps, an opponent attempted to drive up the steps, rode up onto our robot and tipped over. Should we have been penalized? According to your definition, we should have been. However, we did not initiate contact, we were not driving around wreaking havoc, we were holding a defensive position. The point is, you cannot ever write a rule which covers every situation. You need referees. They need to interpret and apply the rules. Perhaps there needs to be an evolving training as the contest proceeds (such as the video-tapes). |
|
#12
|
|||||
|
|||||
|
Re: You write <G34> and <G35>
The only time aggresive behavior should be stopped and penalized is when that behavior goes from defense to destruction. If a team can get in your way to prevent you from scoring thats great.
Aggressive robot behavior has to do with 2 things: the drivers and the robot. The driver makes a concious decision to do the things they do. The robot can only follow commands. But sometimes a sharp edge or other dangerous device passes inspection and gets to be on the field. The robots need to be inspected by experienced people to deem a device destructive or not. I don't know what can be done but a warning like that explained above (cards) is cool. When defense takes away from the game for everyone, we all lose and that offending team or alliance should be warned. |
|
#13
|
||||
|
||||
|
Re: You write <G34> and <G35>
I thought I did cover that situation - if you are already on the steps then you are in a defensive postions and any tipping that results is fair play
for other comments on ramming... I stated a bot is only disqualified if the other bot is damaged or toppled - If you think you can run across the field at 5mph and bump another bot, and no damage results, and they are not knocked to the ground, then that is your judgement call - no harm, no foul but if you can clearly see that your opponents is a wobbly goblen, or they have a 2X ball 9 feet up in the air and out to one side, and your drive into in while it is not in a defensive postion, and it goes over - that was your decision to take that risk - if you dont think you can push it away without knocking it over, then havent you really made a conscience decision to push it over ? think about this for a while - Ive seen so many bots get knocked over while trying to place 2X balls this year, did the driver REALLY think they could push that bot away from the goal - sideways - without knocking it over? also as I defined the suggested rules, you cant run into someone else and fall over yourself and cry foul - there must be agressive action on the other teams part against you and if you deliberately build a top heavy bot then it will be useless in the legitament defensive/offensive situations I defined, in which toppling is not cause for a DQ also (preemptive answer) if you build your bot out of glass, and someone hits you within the bumber zone (2 to 8" high) and your bot shatters - too bad for you, the other team can push you around if detroit can build effective 5mph bumpers on 3000 pound cars, FIRST teams can build them on 130 pound robots. Last edited by KenWittlief : 20-04-2004 at 13:06. |
|
#14
|
|||||
|
|||||
|
Re: You write <G34> and <G35>
Quote:
Are referees going to get a sheet that says, "if the following robots become broken, it's their own fault for not making a robust enough robot, do not give the other team a penalty." |
|
#15
|
||||
|
||||
|
Re: You write <G34> and <G35>
To be playing defence does not mean that you can only approach from a certain side. Don't forget that the best defence is a good offence. By harrassing a robot and not letting it get to a goal is easier than letting it get to the goal and bashing it to pieces as you try to defend.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|