|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Quote:
I'd been running under the assumption that the hostbot cannot enter the vertically projected border, but it clearly only talks about the minibot. That makes 469's alignment perfectly legal, then. I'm really surprised more people haven't done this, then. |
|
#2
|
|||||
|
|||||
|
Re: Interesting rule calls from the Detroit District
Quote:
http://www.chiefdelphi.com/media/photos/36706 Team 148 is another that uses this similar deployment method as well. There are a few others doing this too. -Brando |
|
#3
|
|||||
|
|||||
|
Re: Interesting rule calls from the Detroit District
Quote:
Quote:
Rereading the rules as they currently stand makes it clear that this is no longer the case and all the pre-alignment mechanisms are perfectly legal, provided the minibot doesn't cross the boundary before the endgame. Last edited by Kevin Sevcik : 21-03-2011 at 15:17. Reason: Collin, not Anne. dunno what I was thinking. |
|
#4
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Given 469's design last year, I can see why some teams could say that they once again found a loop hole or (depending on your perspective) lawyered the rules.
However, I think it's clear that there is vertical motion that is assisting the minibot up the pole and is therefore illegal. Nice looking bot though. |
|
#5
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
...but last year, 469 neither found a loophole nor lawyered the rules. They looked at what was allowed, asked for clarification from the GDC in public where everyone could see what they were asking and what the answers were, and then built a robot that was completely and unambiguously in line with those rules.
|
|
#6
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Quote:
|
|
#7
|
|||||
|
|||||
|
Re: Interesting rule calls from the Detroit District
Quote:
G61 does not apply here for an opponent pushing this dead robot into the tower once the pinning period (back away > 6ft for more than 3 sec) has ended (they are no longer causing it, and there is no rule violation yet). As a veteran of FIRST it is easy to get used to the old rules where you could hit the E-Stop and be immune from further penalties. Those days are gone and you now get a Red Card for hitting your E-Stop unless it is a safety emergency. There is no protection for dead robots or even mention of dead robots in the rules (so there is no way for a ref to declare them dead and exempt from penalties), they are the alliance's responsibility to clear those dead robots or they will get penalties if they sit there until the End Game. However, the real grey area is if an opponent tips a robot onto the tower, since there are rules about tipping. I say no penalty/red card in this case, but it is open to interpretation. |
|
#8
|
|||
|
|||
|
Re: Interesting rule calls from the Detroit District
Quote:
|
|
#9
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Thanks for posting these up. I had heard about the deployment system, but it is good to actually see it. After watching, you can find a Q&A that warns about this type of system.
The tube touching the tower thing is rough, but by rules the right call. I don't think it is in the "spirit" of what the rule was intending, but this is consistent with what I have seen on other fields. I have been curious how the last one would get called since they starteddoing the revisions. What 3096 was initially doing was completely legal. Pushing them into the base is completely legal up to the "pinning" time limit thus the count. Because 469 did not back up more than 6 feet for 3seconds, then they were essentially still implementing the pin. <G50> An ALLIANCE may not pin an opponent ROBOT that is in contact with a field border or TOWER for more than 5 seconds. A ROBOT will be considered pinned until the ROBOTS have separated by at least 6 feet. The pinning ROBOT(S) must then wait for at least 3 seconds before attempting to pin the same ROBOT again. Violation: 10 PENALTIES BLUE BOX: If the pinned ROBOT chases the pinning ROBOT upon retreat, the pinning ROBOT will not be penalized per Rule <G61>, and the pin will be considered complete. <G61> The actions of an ALLIANCE shall not cause an opposing ALLIANCE to violate a rule and thus incur PENALTIES. Any rule violations committed by the affected ALLIANCE shall be excused, and no PENALTIES will be assigned. Unless otherwise noted, all PENALTIES assigned by referees are applied to the entire ALLIANCE. What is interesting is that had 3096 come back after 469, the pin would have ended and they may have gotten a tower violation. These are 3 rough calls that definitely head to the grayer areas of the rules, but likely the right calls. P.S. Amazing robot/team. I can't wait to play with/against you guys at Troy. Hoping for more with than against... |
|
#10
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Quote:
.They are being very strict that no upwards motion can be imparted on the minibot by the hostbot. Quote:
Quote:
As far as your opponent getting a red card ... that depends.<G61> protects them from you causing a penalty against them, but If the referee believed that your opponent did not attempt to get away from the tower then yes they could get a red card. |
|
#11
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
From looking at the videos, it appears to me that the refs made the correct calls in all three cases...
Thanks for posting these up -- it's a good heads-up for teams that have not yet competed! |
|
#12
|
||||||
|
||||||
|
Re: Interesting rule calls from the Detroit District
So after watching the third video and going strictly by the rules the blue alliance should have received 10 penalties for pinning, or am I missing something?
|
|
#13
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Quote:
...but maybe, yeah. |
|
#14
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Don,
You bring up a great point, and I wanted to post something similar that happened at the Chesapeake Regional this past weekend that had opposite outcomes (Two Red Cards Given). Check out what I posted over the weekend: Quote:
|
|
#15
|
||||
|
||||
|
Re: Interesting rule calls from the Detroit District
Let me warn of an 'interesting' call at West Michigan.
In the qualifications matches, if a human player throws a tube and it accidentally brushes a hanging tube and descores it, it isn't a DSQ. In the eliminations - it's an instant loss for that human player's team, AND their alliance. We had a fairly precariously seated uber-tube that we had hung. It (evidently) was brushed by a tube thrown by the other alliance's human player. It fell, and they were DSQ'ed from the 2nd quarterfinals match, ending their day. It's a lousy way to lose, but it's in the rules. Watch out. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|