|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Drivers' Meeting
This driver meeting thoroughly disgusted me.
1. Any robot that has anything that extends past the original size constraints (28x38x60) (not in the bumper zone) and touches by accident, coincidences or on purpose, will be penalized. The word incidental is not used in its proper definition in the rules. The definition of incidental touching means a robot will not be penalized if it touches the bumper zone first, stays in contact with the bumper zone, and then touches higher up. True incidental touches WILL STILL BE PENALIZED. That means if you have a dumper, expanding hopper, arm, wing, blocker, stick, tie wrap, something that sticks out by accident, you will be penalized if someone else touches that object. 2. Clarification of pinning rule. You can pin a robot for a few seconds and then you have to back away in any spot except for on top of the ramp. The clarification states that if you push a robot on either ramp, you can hold it forever. This gives big power robots lots of room to do whatever they want. If you were to push a robot up the ramp and say it was sideways you could hold your robot against it the entire match and get the points for the robot as well as "disabling the robot the entire match" Even though this rule may have been in the book the entire year, this is a serious blow to GP. 3. Bumper zone contact, (please if anyone knows this better than I do please comment) As I heard, if a robot pushes another robot in any position as long as the pushing was done in the bumper zone, and the opposing robot flips over, it is not the aggressors fault. Another serious blow to GP. This is giving the ability to easily disable a robot for the entire match. With the sharp ramps this year pushing a robot onto the ramp makes it very easy to tip. This makes me feel like this is turning into a destruction derby. 4. Autonomous and Corner Goals, Intentional ramming in auto is now illegal, and I firmly back this rule and this was a very good one. While that is a great addition, The rule considering robots protruding into a goal is absolutely ludicrous. Obviously the protruding rule was based first on safety. But the consequences are terrible, an entire robot alliance DQ'ed? While we can legally tip other robots. But the real ugly problem comes in with robot aggressors. If a robot were to push another robot into the goal, well you think there would be no penalty or maybe a penalty against the aggressor, right? Wrong. The team that gets pushed in gets the penalty, most people have pieces on their robot that extend more than 3 inches in a certain angle or even straight on. You could so easily push a robot straight into a goal beyond the 3-inch penetration with no effort. This is absolutely ludicrous, allowing robots to disqualify robots on purpose. We might as well have not put the time, effort, blood, and sweat into making shooters and ball handlers. I would like to take this time to thank all the volunteers and referees that make FIRST possible. One of the great things I have learned this season is how to work with material handling. I am so thankful for that, FIRST basically gave me the opportunity to work on it. I feel with this current rule I believe everything has gone to waste. Many, many of us were not happy. Gracious for all the time the refs put in, but not happy campers. The situation has upset some teams designs so much, some feel that this group of new additions/clarifications have turned FIRST into battlebots. Some go so far as not coming back next year. This is a dire situation that needs to addressed for the sake of Gracious Professionalism. I know we can all do better than this. -- FIRST team alumni, FIRST team mentor, FIRST volunteer, and FIRST Vex Judge Peter |
|
#2
|
|||
|
|||
|
Re: Drivers' Meeting
Quote:
Quote:
I'm really confused . |
|
#3
|
||||
|
||||
|
Re: Drivers' Meeting
The refs are making new rules as the game goes on. And they must be using the elastic clause on the word excessive, to mean ramming.
|
|
#4
|
|||||
|
|||||
|
Re: Drivers' Meeting
Quote:
Just because you don't like how the rules will be called doesn't mean that they haven't existed for the last 4 months. |
|
#5
|
||||
|
||||
|
Re: Drivers' Meeting
I 100 percent agree with that, as stated in my earlier post.
|
|
#6
|
||||
|
||||
|
Re: Drivers' Meeting
Quote:
|
|
#7
|
||||
|
||||
|
Re: Drivers' Meeting
Yes if it was accidental it is fine, I believe, disruption of auto will be ruled as fine, as long as these robots aren't driving full speed into another bot. It may be case by case depending on the infraction after the opposing bot is out of the box. We will have to see how it gets ruled if another bot rams one at fullspeed out of the box.
Last edited by UlTiMaTeP : 28-04-2006 at 01:15. |
|
#8
|
||||
|
||||
|
Re: Drivers' Meeting
Quote:
|
|
#9
|
||||
|
||||
|
Re: Drivers' Meeting
Quote:
|
|
#10
|
||||
|
||||
|
Re: Drivers' Meeting
Quote:
Almost nothing in my 8 years of FIRST has been so discouraging as to be tipped in autonomous two matches in a row. I've got mentors and parents asking how this is different than Battle bots. I sincerely wish that when the first questions were asked that FIRST had changed the rules to prohibit autonomous motion on the defensive side of the field. At least at the regional level, teams were afraid of a DQ or other penalty. |
|
#11
|
||||
|
||||
|
Re: Drivers' Meeting
Wow that rule for expanding bots is terrible! If any of you have seen SPIKE we expand with our net, and now people can just hit the net, and we get penalites, that is really dumb. Why start using this rule now? It was not in effect at the two regionals we attended.
Luckily we were able to constrain our expanding hopper, but this new rule/interepretation is ridiculous. |
|
#12
|
|||||
|
|||||
|
Re: Drivers' Meeting
Quote:
Seeing Spike's robot with the smaller net was thoroughly depressing. At Chesapeake, everyone knew who Spike was. They had a great machine and I applaud them for playing hard. I am sorry that they had to change an excellent robot to conform with rules that had been enforced differently at previous competitions. I know that with the game changing every year and all the different people responsible for enforcing the rules, these sorts of things do happen. Thanks to the refs for all their hard work. |
|
#13
|
|||
|
|||
|
Re: Drivers' Meeting
I, too, was thoroughly disgusted by the drivers meeting. However, I feel like I am against the majority. I was not offended by the rules, they are what they are, and there is little use to arguing with the referees over moot points. I was shocked by the complete lack of gracious professionalism by some of the drivers/stage crew. No respect was shown to the referees or FIRST.
Worst of all though, everyone applauded the repeated, unsportsman-like conduct. I've seen a lot better out of first. Also, everyone needs to remember that you are representing your entire team, not just yourself. |
|
#14
|
|||
|
|||
|
Re: Drivers' Meeting
Quote:
Quote:
Quote:
|
|
#15
|
|||||
|
|||||
|
Re: Drivers' Meeting
it was long and spiteful, full of people who need to learn to read... and it made me miss dinner with my team >_<
Seriously, the manual is out for a reason... um... to read it maybe? |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Ask Head Refs questions before Driver's Meeting | Brandon Martus | Announcements | 0 | 22-04-2006 19:41 |
| Operator Interface LED Drivers | Andrew | Programming | 7 | 15-03-2004 11:27 |
| 2003 IRI: A driver's last hurrah or a new rookie driver's experience? | Amanda Morrison | Off-Season Events | 14 | 23-05-2003 17:39 |