Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Rules/Strategy (http://www.chiefdelphi.com/forums/forumdisplay.php?f=6)
-   -   NJ Elim Yellow Card Oddity (http://www.chiefdelphi.com/forums/showthread.php?t=65299)

EricH 02-03-2008 19:59

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by thefro526 (Post 711377)
Fair enough, from now on we will call this rule the "816 Alliance rule". Does anyone know of what rule number refers to this? I searched and could not find it.

I just checked the most recent rule book published by FIRST and there is no mention of an alliance sharing a yellow card in the Tournament section, they just refer to anyone robot getting a red card DQ's the entire alliance

There isn't one at this point. On either count (other than the red card rule).

Elgin Clock 02-03-2008 20:49

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by thefro526 (Post 710520)
Lol we did that and it was a mistake from our programmer/possible IR interference. We personally as the alliance did not get bothered by the yellow card.

Not to be harsh to you, but it doesn't really matter if you weren't bothered by the bad call, or penalty assignment given to you.
I know exactly where you're coming from with that statement though, and felt the same way when some calls were missed or made against us and didn't affect the match.
When it does affect you that's really when you start to care though.

It was wrong, and I am glad Kevin caught this.

When things are caught in week one then that leads to updates changing the game from week to week... This is (kind of) inevitable, but also a gray area as well due to an unfair advantage/disadvantage seen by some earlier competing teams when rules change/get more clear.

Bottom line, a bad call that doesn't effect you per-say is still a bad call, and the teams watching the competitions with a fine tooth comb on the rules, and trying to get a feel of how the game will be played (especially in a week one regional setting) are confused when they are made no matter how it affects the outcome of the game, or even just your one match it just happens to take place in.

dpc131 02-03-2008 21:15

Re: NJ Elim Yellow Card Oddity
 
Just some additional clarification on the situation. There was some comment on test prior to loading new code. If we can remember 2006 was infamous for changing code on the fly to block good shooters. This was extremely effective a lot of the time. There is some risk with using this approach and this is what can happen. 816 added in some last minute changes so we didn't collide in autonomous and some unexpected results happened.

What frustrated me most was the FIRST's IR receiver implementation and the unexpected results when using in a match. I think alot of the hard crashes were robocoach's signals not being received due to range/interference. Like anything, this is an engineering issue to be looked at during design of the robot, but this is a topic for another time. But again I see FIRST has sent something to the teams to implement that has not been proven (IR receivers in 2005, Camera in 2006, etc.)

brimcdonald666 02-03-2008 21:22

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by Brian C (Post 710383)
I'm with you on this one Elgin. I also saw that team 303 was DQ'd in an earlier qualifying match. It's the first time I can ever remember seeing a team DQ'd for hitting into an alliance station wall in hybrid (autonomous) mode. Or for hitting into a wall in the first place.

Teams should have their control system secured in some form or another.

Thats really weird, cause our team (503) accidentally rammed the wall, full speed in autonomous, and broke Robostangs(111) controller, we are still sorry about that, im glad it was nothing perminant, but we still didnt get any penalty what so ever

thefro526 02-03-2008 21:35

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by brimcdonald666 (Post 711443)
Thats really weird, cause our team (503) accidentally rammed the wall, full speed in autonomous, and broke Robostangs(111) controller, we are still sorry about that, im glad it was nothing perminant, but we still didnt get any penalty what so ever

That is very strange but I can see why a full speed ram would justify a penalty and possibly it is up to the refs. These issues will definitely be clarified.

Swan217 02-03-2008 22:28

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by Anne Shade (Post 711325)
Actually Dan,

The team was warned during Qualifying matches, not eliminations. When teams enter eliminations, their slate is supposed to be wiped clean. However, this year's yellow card is to be given for "egregious" robot or team member actions. If the head ref thought the one time was egregious, the yellow card could have been given. That is up to that particular head referee's interpretation of the action. I'm not sure exactly which rule the head ref believed was violated "egregiously" in this case because I can't seem to find one. I guess you could lump it under S01...

My question is whether or not the timing of the yellow card was appropriate. The yellow card was given during the reset of the match. To me, that would mean the match had yet to be completed. Can a team receive a yellow card for a match that had yet to be completed? What if their robot had again rammed the player wall when they replayed the match, would the alliance get DQ'ed for receiving a second yellow card in the same match?

This kinda follows Dez's point about the time out being called during the middle of the match...

I totally agree with you about the timing issue - the Head Ref should've technically waited until after the match had completely ended before giving out a yellow card. Your second hypothetical is moot because generally a yellow card is severe enough punishment to correct the behavior or at minimum abort the hybrid strategy as to not risk getting a red card.

There is no rule that says that the "slate" is wiped clean for eliminations, only that cards do not carry over into eliminations. Unofficial warnings are given to prevent egregious behavior throughout the entire competition, and aren't official rulings on the field. The head ref might've thought that the team was performing programmed egregious behavior the first time, but gave the chance to correct the programmed behavior. Since the behavior was apparently not rectified to the satisfaction of the referee, and the behavior was not severe enough to deserve a DQ, a yellow card was given.

<T11> allows for red cards to be given to the entire alliance, but gives no procedure for yellow cards in elimination rounds. I'm not saying that this ref's interpretation was correct or incorrect, but giving the most likely reasoning. My interpretation up to this point was that a yellow card was given to an individual team on the alliance, but two yellow cards accrued by an alliance results in a DQ for the entire alliance in elims. This may be an incorrect interpretation of the rules. The correct interpretation will no doubt be resolved by the Head Refs this week before the next round of regionals.

At any rate, in general, yellow cards are really no big deal. If you get one you should take it seriously, but since there is no real consequence of a yellow card, save temporary embarrassment, there shouldn't be this much outrage over yellow cards. They're not attached to your "permanent record" and nobody cares about them after the tournament is finished. As defined in T05, a yellow card is an Official Warning, and nothing more.

GaryVoshol 03-03-2008 11:17

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by George A. (Post 711339)
But since the field itself was broken and needed repair ...

A Ha! Teams are prohibited from destroying the field or field elements. (That doesn't explain the group yellow card, though.)

Kevin Sevcik 03-03-2008 16:44

Re: NJ Elim Yellow Card Oddity
 
Quote:

Originally Posted by Dan Swando (Post 711519)
At any rate, in general, yellow cards are really no big deal. If you get one you should take it seriously, but since there is no real consequence of a yellow card, save temporary embarrassment, there shouldn't be this much outrage over yellow cards. They're not attached to your "permanent record" and nobody cares about them after the tournament is finished. As defined in T05, a yellow card is an Official Warning, and nothing more.

I kinda hope teams don't just shrugs off Yellow Cards like this. Or, at least, I hope any team in the Elims doesn't. If you've gotten a Yellow Card, it's usually for a good reason, and it means the refs are going to be watching you a little more closely. If my team got carded in the elims I know we'd be a little more wary of our actions for fear of getting a second card and DQ'd. I can't imagine that a Yellow Card wouldn't have some sort of effect on a team unless they're completely oblivious and uncaring about how their actions might affect their alliance.

Kevin Sevcik 03-03-2008 16:52

Re: NJ Elim Yellow Card Oddity
 
Also, the GDC came back with an answer and basically said "Not standard, but if the refs felt a multiple card was appropriate...."

Which seems a bit of a cop out. I can understand that they don't have all the details, etc. But some sort of statement saying the refs could if they felt the card was deserved for some action or collusion on the part of the whole alliance.... But based on even the vague answer provided and the fact that the announcer said it was for the autonomous driving of the one team... I'd say the refs missed the call with the group yellow card.

Danny McC 03-03-2008 17:26

Re: NJ Elim Yellow Card Oddity
 
I actually felt pretty bad after I wasn't able to stop the bot in time. So I walked over and asked them if everything was ok and if I could do anything to help.

pakratt1991 05-03-2008 10:33

Re: NJ Elim Yellow Card Oddity
 
I saw this same thing at the Oregon regional. A teams hybrid mode hit the other wall at high speeds and it tossed a teams controller to the ground. There were no yellow cards given and the refs just said that teams needed to secure their controllers. We used 3 long strips of Velcro and that worked fine.


All times are GMT -5. The time now is 01:36.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi