![]() |
Balls In Opposing Robots
I've seen numerous fouls called today on teams who had an opponent's ball enter their robot. If a team has put the ball in your robot, or it accidentally enters your robot, why should you be penalized for trying to remove it?
I understand why it has been called this way, but it's painful to see this create huge point differences... |
Re: Balls In Opposing Robots
I agree. It is extremely saddening to me that this caused 1114 to lose. They had the best robot there and in my opinion should've won. These penalties are deciding elimination matches when the penalties received are judgement calls. Meaning it is debatable as to whether or not the penalties should've been received. In the Finals at the Arkansas regional the Blue Alliance won the first match and the next two the Red Alliance won but solely because of foul points that were questionable.
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Sorry, but the problem was entirely avoidable by the drivers having the robot back up when they saw the ball bouncing toward them. I watched this match as it happened. The GDC made no mistake in the rules by saying you should design your robot to make sure you don't accidentally possess another team's ball. That's how it happened. There should be no changes made in the rules.
|
Re: Balls In Opposing Robots
We got 50 foul points twice on our alliance for 100 tech foul points. Luckily we still won! It was for the same reason. They threw it in our intake. I can't see why it's a game changer?
|
Re: Balls In Opposing Robots
I find that the rule covers all of the situations of possession but I don't like the rule.
Quote:
|
Re: Balls In Opposing Robots
Since when should engineering not have a hard, defined, approach to a problem that could very easily occur.
|
Re: Balls In Opposing Robots
Quote:
As for the GTRE match, was the second tech foul pinning? That was enough to seal the game for the blue alliance (who won due to strong defense in the first match). The illegal catch just meant that the game was hard to win from an earlier point in the match. While I was cheering on the red alliance (3683 is long due for a championship appearance!), the red alliance got upset by a strong 5th seed. |
Re: Balls In Opposing Robots
The second tech foul was indeed pinning.
|
Re: Balls In Opposing Robots
Quote:
I completely agree with the decision on this matter. I saw this happen plenty of times both at week 1 events and this week, even in cases where the ball was not directly in the robot. It was clear possession, regardless of intent. It is unfortunate that it has happened to teams, all of which I'm sure were accidental, but it was clearly stated very early that you must design around this to make it impossible for that to happen. It's no different than a robot designed to effectively shoot the ball. Both aspects are incredibly important parts of the game. |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
I agree, it's a harsh rule. BUT think about it this way: anytime the other alliance's ball is in your robot, that alliance cannot be scoring said ball. So it's harsh, but it's necessary to ensure that both alliances have as fair and equal scoring opportunities.
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
If it accidentally enters your robot, it is on you to avoid that situation. Especially when you've been warned of it in the game manual. I feel it is a reasonable foul because otherwise teams would make no effort to avoid possessing the wrong ball! It would add ~10 seconds to the other alliance's cycle time. Think about it, without this rule, holding the other alliance's ball would actually become a part of teams' strategy! As someone said earlier, the red robot at GTR-E should have driven backwards or just stopped going towards the ball - easily avoidable situation in my opinion. |
Re: Balls In Opposing Robots
Quote:
Quoting for relevance: Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
I remember during the drivers meeting at UNH we were reminded of this rule and told to "Make sure your robots are designed so they can't hold an opponents ball". I heard this and I know this was out of the control of our head ref (who did a fantastic job all weekend I think UNH ended extremely fair and of the few problems that did go wrong they were remedied quick and fair) but this is coming directly from FIRST so what kind of bogus line is this? Are we all supposed to put a bunch of sensors on our robot to detect red/blue balls and close up our intakes when we get near one?
We all know the intent of the rules because if the rule didn't exist teams would just grab opponents balls and play keep away for the match but most of the calls for possessing an opponents balls are either accidental or caused by the alliance that is benefiting by getting the penalty points. Same thing with the G40 problems of week 1 its the accidental infractions of the rule that are killing teams because the penalties for tech fouls are way too large for minor offenses! |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
![]() |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
I have a general question to ask.
Should a team receive a penalty during a match, but the after that match the ref/head ref does not and or cannot explain what the penalty was to that team? Basically can someone get a penalty without a reason if they were to question the decision? |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
I think in the end though no penalty is truly going to be placed on any team for no reason what so ever. Just because one ref doesn't know doesn't mean someone else wont know. |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
On this note also, I would say be careful about calling for a dead ball twice in a match. As we saw at UNH this weekend, this can be grounds for a replay. The ball getting lodged in another team results in a 100 point penalty, however, you must wait for the head ref to suspend the cycle.
Quote:
http://www.youtube.com/watch?v=DcMtO...k57J7Q# t=170 You will see at 3:11 that the blue alliance on the right side of the screen holds up the dead ball sign. Then the match proceeds and one of their teammates gets the ball lodged in them. You can see at 3:56 that a second dead ball is called for. Even though the second dead ball replacement is never put into play it was deemed that just calling for it was grounds for a replay of this semi final match. Luckily, this did not affect the outcome of this semifinal series, but under other circumstances it certainly could have. |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
We had a similar situation yesterday at CVR. Our alliance's ball got stuck in the opposing alliance's robot and the opposing robot died on the field. In this instance, who is supposed to hold up the dead ball card? How is our alliance supposed to know if the opposing robot is dead or is going to try to spit the ball back out?
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
It does not matter what another person knows because the head ref is in charge |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
I don't mean to single you out, Justin, but in general I dislike this trend on Chief of people diminishing the victories of others. Our team has been on both sides of this coin, and it's never fun. There absolutely needs to be discussion on the merits of various game rules and penalties, but we also need to be able to do it without marginalizing the efforts of the affected teams on both side of the result. |
Re: Balls In Opposing Robots
The rules are the rules. They are written in a very specific way and meant to be called in a very specific way. We are going to see times where the ref's make judgment calls and not everyone is going to agree with the outcome. We had a match yesterday that our opponent ended up with our ball for a short time and got rid of it as quickly as they could and did not get called on it. Had the call been made the way the rules stated, we would have won the match. However the way the call was made was consistent with how it was made all weekend. This game like any other game and for that matter Life itself has a certain element of luck. Lady luck was not on our side this time.
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
My two cents is that the game was designed for catching these balls and human player loading. So many teams have hopper like collector systems. My team was in a match where the opposing ball landed in our partners robot and they had technical difficulties prevented them from ejectong the ball. We got penalties for possessing and prolonged possessing. It just felt a bit unfair. They were doing everything they could to get rid of it. It's not like they were trying to continue playing with their ball. I think the whole "intentional" possessing is a hard call. Just like having your collector driven into and getting penalties for inside the frame perimeter.
Just my two cents. :/ |
Re: Balls In Opposing Robots
G12
An ALLIANCE may not POSSESS their opponent’s BALLS. The following criteria define POSSESSION : “carrying” (moving while supporting BALLS in or on the ROBOT or holding the BALL in or on the ROBOT), “herding” (repeated pushing or bumping), “launching” (impelling BALLS to a desired location or direction via a MECHANISM in motion relative to the ROBOT), or “trapping” (overt isolation or holding one or more BALLS against a FIELD element or ROBOT in an attempt to shield them). Violation: TECHNICAL FOUL per instance. If extended, another TECHNICAL FOUL. If strategic, RED CARD for the ALLIANCE. Examples of BALL interaction that are not POSSESSION are A. “bulldozing” (inadvertently coming in contact with BALLS that happen to be in the path of the ROBOT as it moves about the FIELD) and B. “deflecting” (a single hit to or being hit by a BALL that bounces or rolls off the ROBOT or a BALL slips through the grips of a ROBOT without arresting the BALL'S momentum). A BALL that becomes unintentionally lodged on a ROBOT will be considered POSSESSED by the ROBOT. It is important to design your ROBOT so that it is impossible to inadvertently or intentionally POSSESS an opponent’s BALL. G14 Strategies aimed solely at forcing the opposing ALLIANCE to violate a rule are not in the spirit of FRC and are not allowed. Rule violations forced in this manner will not result in assessment of a penalty on the target ALLIANCE. Violation: TECHNICAL FOUL Tl:DR Punishing for accidents because your design should account for that. |
Re: Balls In Opposing Robots
Quote:
Quote:
Please remember Referees are all volunteers doing a difficult job. I mean no disrespect to them. The rule is the same for intentional or intentional procession. |
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
Re: Balls In Opposing Robots
Quote:
|
| All times are GMT -5. The time now is 02:24. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi