|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Drivers' Meeting
What were the interesting questions, answers and interpretations? Is anything going to be remarkably different from the regionals to the championship?
|
|
#2
|
|||
|
|||
|
Specifically:
What was said regarding extensions and contact outside the bumper zone?
|
|
#3
|
|||||
|
|||||
|
Re: Drivers' Meeting
Basically you're screwed if you have an apendage outside the bumper zone and someone either hits it or you hit someone with it, you get a 5 pt penalty every time theres contact. Also if you have an apendage that goes more than 3" into the ball chute your alliance gets dq'd, and that even if someone else pushes you causing the thing to go in. So if you have a thingy outside the bumper zone you better take it off or risk losing every match because of it. These are 2 brutal rules that will ruin many teams design strategies, that are being executed on late Thursday/Friday morning basically, giving these affected teams no time to make the needed changes. Too much too late IMO. Also you can't ride up a bumper on top of the bumper zone etc. But if a bot is on its side you may push them wherever you like. They also clarified pinning to exist everywhere on the field except when a bots wheels are all entirely off the carpet (on the ramp) then they are fair game.
The q&a got a little coarse where some students weren't too happy with these rules and Dr. ???Aiden took the abuse well. These rules acoording to him always existed, but to my knowledge were never enforced. |
|
#4
|
|||||
|
|||||
|
Re: Drivers' Meeting
The drivers meeting was good, in the beginning. Dr. Brown did a wonderful job at doing what he is supposed to do in explaining the basic layout and gist of things as per the national event. He answered many Chiefdelphi questions promptly and concisely. However, when it came to the live QandA period, I was shocked. So many questions asked had already been answered or were what I consider common knowledge. There were however a few diamonds in the rough. On of which was from a member of team 4 who asked if an appendage broke and was the first part of said robot to contact another robot (being outside of the bumper zone) would there be a penalty. There answer was yes, a penalty would ensue. I don't know why I typed that entire question out, just an example I guess of one of the good questions.
I ended up having to leave early however when a member from a team not to be mentioned here, repeatedly asked for non bumper zone interaction clarification. Many of his questions were to the point of "if I repeatedly hit an opponent in an area where they were outside of the bumper zone will they continue to rack up penalty points?" I have no problem with the rules, they haven't changed, but this person's questioning over and over which lead everyone there to believe that this is their game plan for tomorrow (whether it is or isn't I will have to see) disgusted me, that is when my drive partner and I left. Teams, drivers, coaches, read the rules and play with gracious professionalism in mind. I understand that the game is the game, but lets not turn this game to a 2005 who gets the most penalties. Maybe I am over-reacting, maybe not. I have had a long day of making my robot the best SCORER (not de-scorer) it can be. I am off to watch match video and sleep. -$.02 de Henry |
|
#5
|
|||
|
|||
|
Re: Drivers' Meeting
Quote:
Did he address the idea of incidental contact? They don't mention "incidental contact" four times in <G22> for no reason, so any discussion on the rule without mention of what constitutes incidental contact is incomplete. |
|
#6
|
|||||
|
|||||
|
Re: Drivers' Meeting
Quote:
|
|
#7
|
|||
|
|||
|
Re: Drivers' Meeting
Quote:
I'm confused . |
|
#8
|
||||
|
||||
|
Re: Drivers' Meeting
Quote:
If something breaks on a robot such that it becomes an appendage, would penalties be incurred by contact with an opposing robot outside the bumper zone? Answer: Yes. So, if you design and build a robot that is not intended to ever extend beyond the bumper zone, but a mechanical failure occurs such that now your robot has a loose piece that could contact a opposing robot outside of the bumper zone, you are now vulnerable to being penalized should the opponent drive into your broken part... So the guy who was worried about his camera getting whacked better hope that it falls to the floor, because if the opposing robot who knocked it loose in the first place now comes back and hits it as it swings around by its cables might be able to collect penalty points for his alliance. It can't be this twisted, can it ?Probably not. However, I could imagine a portion of a shooter, or a piece of lexan coming loose from a robot and creating the potential for this penalty. So if this happens to your robot, you need to go on the defensive to prevent robot contact with your broken part. Get up your ramp and camp! |
|
#9
|
||||
|
||||
|
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 |
|
#10
|
|||
|
|||
|
Re: Drivers' Meeting
Quote:
Quote:
I'm really confused . |
|
#11
|
||||
|
||||
|
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.
|
|
#12
|
|||||
|
|||||
|
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. |
|
#13
|
||||
|
||||
|
Re: Drivers' Meeting
I 100 percent agree with that, as stated in my earlier post.
|
|
#14
|
||||
|
||||
|
Re: Drivers' Meeting
Quote:
|
|
#15
|
||||
|
||||
|
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. |
![]() |
| 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 |