|
|
|
![]() |
|
|||||||
|
||||||||
| View Poll Results: You Make The Call | |||
| I warn/penalize BLUE team for pinning |
|
19 | 36.54% |
| I award Bluabot 50 points for hanging |
|
31 | 59.62% |
| I award Redabot 50 points for hanging |
|
6 | 11.54% |
| I do not award Bluabot any points for hanging |
|
9 | 17.31% |
| I do not award Redabot any points for hanging |
|
26 | 50.00% |
| I do something else ... please explain |
|
4 | 7.69% |
| Multiple Choice Poll. Voters: 52. You may not vote on this poll | |||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: YMTC: Bluabot sits on Redabot
I'm not sure if this one is a stumper as much as it is unpleasant to score by the rules of the game.
Quote:
Bluabot is hanging because it is not touching the ground, it would remain hanging with Redabot removed (not supported by Redabot), and it would not remain hanging (off the ground) with the horizontal bar removed. The rules as is only apply to pinning while on the carpet, so strictly speaking, pinning penalties do not apply. And if it is modified to apply on any field ground (platform and carpet), it would depend on whether Redabot could have moved away, including if Redabot was able to lower itself off the bar and drive away. If so, no penalties on Bluabot, as Redabot's movement was not inhibited. However, if Redabot cannot lower itself or move reasonably in any direction whatsoever, warnings and penalties on Bluabot, the number of penalties as per precedence on the pinning rule. Last edited by Winged Globe : 05-04-2004 at 04:44. |
|
#2
|
||||
|
||||
|
Re: YMTC: Bluabot sits on Redabot
if the blue bot is keeping the red bot from pulling itself up, it MUST be supporting some of its weight on the red bot, it could not possible be preventing the red bot from ascending if most of its weight were not supported by it
and the red is clearly supported by its wheels so neither are entirely supported by the bar neither are hanging BTW - this would be easy to determine - bluebots cables or hook arm would be loose on the bar, or slack, it its applying force to the redbot Last edited by KenWittlief : 05-04-2004 at 08:15. |
|
#3
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
According to the rules, Bluabot IS hanging, and Redabot is not. However, I would penalize Bluabot for pinning. Also, Bluabot is technically not pinning, while they are inhibiting the movement of Redabot, Rule <G27> clearly states,
Quote:
|
|
#4
|
||||
|
||||
|
Re: YMTC: Bluabot sits on Redabot
the red bot is not 'pinned' if it is free to drive away
the blue bot is preventing it from going up - it is blocking its path in the Z direction but its not necessarily pinning it so it cant move at all. besides, the rules state pining only applies when: Quote:
also from the rules: Quote:
Last edited by KenWittlief : 05-04-2004 at 11:16. |
|
#5
|
||||
|
||||
|
Re: YMTC: Bluabot sits on Redabot
I asked this very question at UTC New England. The ruling was that if the Bluabot was removed and the Redabot was hanging then Redabot scores. Aidan was the Head Ref.
|
|
#6
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
The way I see it, Redabot is definitely NOT hanging. That's not in question at all.
What is in question is Bluabot's method of descent. IF BLUABOT SLAMMED DOWN ON REDABOT: -No points for Redabot, as it's not hanging. -50 points for Bluabot, as it is defined as hanging in the scenario. -Warn Bluabot for getting a too rough, penalize if there's some real damage IF BLUABOT EASED DOWN ON REDABOT IN A SLOW, CAREFUL MANNER TO PREVENT DAMAGE: -No points for Redabot, as it's not hanging. -50 for Bluabot, as it would be hanging (given in scenario). -No warnings to Bluabot, as it's exhibiting a legitimate strategy and showing enough GP by not intentionally trying to damage Redabot. (Besides, Redabot is supposed to be built to withstand "vigorous interaction.") |
|
#7
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
Quote:
|
|
#8
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
Quote:
Red is obviously NOT hanging, because it is touching the platform. Blue is NOT hanging, because, if Red is SUPPORTING enough of Blue's weight that it can't raise itself off of the platform, then the chin-up bar is NOT supporting Blue. |
|
#9
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
Quote:
![]() |
|
#10
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
My idea (which probably throws away a few rules) is this:
|
|
#11
|
|||||
|
|||||
|
Re: YMTC: Bluabot sits on Redabot
I suppose I'll toss my pennies into the argument now..
For the record, this exact situation occurred at LSR, which is where I assume Lucien got the idea from. The call as made was that Blue WAS hanging and Red was NOT. I didn't discuss with the refs, but I assume the logic was as mentioned earlier. Red was touching, when red was removed, Blue was still hanging. There were no other penalties given, as Blue lowered itself very slowly. I'll just comment real (not) quick: Red is obviously not hanging, as it is touching the ground, so supported this and removing that is immaterial. if it couldn't lift in the first place because a robot was above it, but enough energy was stored to lift it when the offending robot was removed, it would seem very, very odd to suddenly give it 50 points. How Red has ended up touching is, I think, immaterial. Bringing that into the argument would so horribly complicate rulings that it is infeasible. Blue obviously IS hanging, if it is still above the platform when Red is removed. The definition of supported clearly states that an object is supported, for FIRST scoring purposes, is the robot is no longer hanging when the supporting object is removed. Thus, by FIRST definition, red cannot be supporting Blue, despite common sense and physics and all that. Pinning doesn't seem to be an issue here, unless Blue is resting so heavily on Red that Red is completely incapable of moving on the platform. If Red can move to the side, out from under Blue, then it is not pinned. This entire lowering episode is akin to a robot pushing another around on the field. If Team A pushes Team B around in the open field, it is not considered pinning. Atleast, I think it's patently silly to penalize A for pinning when B has the freedom to move away from A. In fact, I have never seen pinning called for such an action. The rule states that pinning is inhibiting a robot's motion. As I see it, this can be interpreted in only two ways: Totally inhibiting, so that a robot may not move at all in any meaningful sense; or partially inhibiting, ie. preventing a robot from moving in any particular direction. If the latter was the correct interpretation, any team could be penalized for pinning simply for getting in the way of another team for several seconds. So, I see dropping onto a robot as simply the vertical equivalent of pushing someone around. Ahem. that was slightly longer than I'd intended, but I like to be thorough. For the record, my team was the dropping robot, and it won us the match, so I might be biased. I can also state that it was one of the most exciting matches outside of the elims at LSR, and the crowd had no complaints at all about the drama of one robot attempting to dehang another. |
|
#12
|
||||
|
||||
|
Re: YMTC: Bluabot sits on Redabot
Yeah thats quite a situation. My guess is that Blue is pinning red and therefore it will be penalized. After that i would that blue and red should be awarded the 50 points.
|
|
#13
|
||||
|
||||
|
Re: YMTC: Bluabot sits on Redabot
Regarding the pinning rule, not only does it explicitly apply only to the carpet, but it is specifically designed to stop powerful robots from having too much of an advantage over weak ones (or else it would lead to some pretty defensive strategies). It's also a carry-over from old games and therefore it's reasonable to say it isn't designed to take hanging into account. FIRST has also said otherwise.
Quote:
Quote:
|
|
#14
|
||||||
|
||||||
|
Re: YMTC: Bluabot sits on Redabot
Quote:
That certainly doesn't seem to be the intent of the rule. |
|
#15
|
||||
|
||||
|
Re: YMTC: Bluabot sits on Redabot
Are you asking me, or the people that wrote the rules? The carpet clause is explicit and not open to interpretation, but furthermore, I'd do it given the chance, and I can justify it in my own mind by saying I'm preventing that robot from reaching a specific goal, rather than parking in front of them in order to take them out of the game, which is the reason the rule exists in the first place. Stopping a robot from a specific target is still GP and is strategic; pinning them for the whole match is lame (though running down 10 seconds is certainly viable).
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| YMTC - No battery plugged-in | SilverStar | You Make The Call | 15 | 10-04-2004 13:12 |
| YMTC: Redabot grabs rail | Natchez | You Make The Call | 10 | 10-04-2004 12:16 |
| YMTC: Redabot accidentally breaks goal | Natchez | You Make The Call | 9 | 10-04-2004 12:11 |
| YMTC: Bluabot and Redabot hanging? | Natchez | You Make The Call | 15 | 23-03-2004 01:42 |
| YMTC: Bluabot dies while pinning | Natchez | You Make The Call | 17 | 21-03-2004 11:33 |