|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: G17 (ball return time limit) penalties in endgame
Quote:
I hate to be a stickler, but according to the way it's written the alliance would still need to reintroduce the ball to the field in the requisite time or be penalized. |
|
#2
|
|||||
|
|||||
|
Re: G17 (ball return time limit) penalties in endgame
Quote:
Let us assume that a ball enters the chute at T=1 second remaining. For simplicity, there are no balls in the station, leaving an 11-second countdown. This means that (ordinarily) the ball must pass through the return counter before T= -10 seconds. Are we agreed on this? According to <G05>, scores are calculated at T= -10 (10 seconds after the field timer displays 0), or when everything comes to rest, whichever comes first. To assess a penalty for a ball not going through the return counter by T= -10, the following would have to happen: 1) Something on the field would need to be moving for all 10 seconds. We can claim, for the sake of argument, that this is the ball being returned. Also, 2) The ball has to go through the counter at or after T= -10 (not sure which it is, but looking at the DOGMA graphical description, we'll assume after, as a further penalty is to be applied for every 2 seconds late after the timer trips, and is not applied when a ball goes through 2 seconds after the timer trips.) So, we assume that 1) and 2) happen, and the ball goes through at T= -11. A penalty is assigned, right? Wrong! Scoring, if you remember, stops at T= -10 under <G05>. (This is, of course, aside from refs verifying everything like robots hanging on towers.) This is for the case of a score with 1 second left. Logically, it would not get a penalty. But what about the case with 2 seconds left and nothing in the station? We have established that the ball will have until T = -9 seconds. Again, looking at the conditions above, we see that it is possible to get a penalty in this instance, assuming that both 1) and 2) are true. But what if our assumption that the ball moving in the station is enough to delay the scoring to the 10-second mark is false? Then 1) is false, and automatic scoring has already finished. So, under certain conditions, it would be possible to get a penalty for a ball scored at T = 2 seconds, if an assumption is true, and not possible if it is false. The same case can be made out to T = 11 seconds. But wait! What if there's another ball in the station? That adds 4 seconds onto the time to return. So, for anything under 5 seconds, with one already in, the conditions say that no penalty could be applied if our assumption in condition 1) was true. For two balls already in, the same can apply to anything under 9 seconds. And for 3? Well, that goes out to 13 seconds (though you really want to start getting those balls back out there at that point). In other words, if the timer in fact keeps going, at least in software, then after a certain point, teams will get penalties assigned by the software for not returning the balls to the field, even though time has expired, and after another point, they will not get any more. Under <G03>, the match ends when the arena timer displays 0 seconds. So, after a match, you give a team a penalty that was earned after the match ended. A penalty, not a card. Let's say that there are two such penalties, and they would have won by one point without them. And, to take this example to an extreme, let's say that this has been consistently applied throughout all events, and this particular instance happens in Match 3 of the Championship Finals. Now, if you're a ref/GDC member/algorithm developer, do YOU want to hear the "So-and-so's X cost Y the World Championship because a penalty was given after a match ended" complaints? Didn't think so. Especially if this has already been happening at the regional events. If your take is correct, and teams lose matches because of that, then according to Murphy's Law, the above will happen at least once, and probably more. (I'm disregarding the seeding point discussion, because that's going to make it even worse.) Under <G03>, it should not happen at all. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Ball Return | frank.pendzich | Rules/Strategy | 11 | 11-01-2010 09:19 |
| Ball Return Trajectory | kirtar | General Forum | 8 | 11-01-2010 08:07 |
| Limit Switch return value | Team1710 | C/C++ | 15 | 02-02-2009 15:32 |
| Center goal ball return? | b-rant | FRC Game Design | 12 | 22-04-2006 20:15 |
| ball penalties? | clatek | Rules/Strategy | 4 | 25-01-2006 16:58 |