|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: What we learned from week 1
Quote:
|
|
#2
|
||||
|
||||
|
Re: What we learned from week 1
I haven't had time to read this whole string, but I'll say that I learned that even teams that say they can climb for 30 (or 50) didn't at the Hub City and shooting frisbees four at a time is the best skill.
But like others here have said, even rookie teams were competitive and a ten-point hang is completely worth it. Many videos of Hub City (for team 1108) at my youtube site. [url="https://www.youtube.com/user/hrench"] |
|
#3
|
||||
|
||||
|
Re: What we learned from week 1
That was a huge hit if I've ever seen one. If you look at the picture they show a little later, 16's bumper comes up and hits them inside their frame perimeter. Nothing against 16 but if I was a ref and saw that I feel like I would call something.
|
|
#4
|
||||
|
||||
|
Re: What we learned from week 1
There is no foul rule that applies to this situation.
|
|
#5
|
||||
|
||||
|
Re: What we learned from week 1
3.2.6.2 G29
Deliberate or damaging contact with an opponent ROBOT on or inside its FRAME PERIMETER is not allowed. G29 does apply, depending on the severity of the contact. Edit: The blue box appears to limit the impact of this rule to contact by appendages. Contact by bumpers may be a good candidate for a Q&A question. Last edited by smistthegreat : 05-03-2013 at 11:22. |
|
#6
|
||||
|
||||
|
Re: What we learned from week 1
My comment was not that G29 did not exist, only that it did not apply to this situation. A robot tipped while being pushed and their bumpers overlapped momentarily. Hardly deliberate, damaging contact.
|
|
#7
|
|||||
|
|||||
|
Re: What we learned from week 1
Quote:
|
|
#8
|
||||
|
||||
|
Re: What we learned from week 1
Read your own quote:
High speed accidental collisions may occur during the MATCH and are expected. ROBOTS extend elements outside of the FRAME PERIMETER at their own risk; no penalties will be assigned for contact between two such extended elements. 16 had no such extended element. Their bumpers overlapped. It happens. |
|
#9
|
|||||
|
|||||
|
Re: What we learned from week 1
Quote:
|
|
#10
|
|||||
|
|||||
|
Re: What we learned from week 1
Quote:
At any rate, I think the primary issue is that your initial post seemed dismissive of the whole category of G29 fouls. Since you acknowledge that they do exist, the issue boils down to whether athe few stills and video we have show some evidence of deliberate and damaging contact. I think we can file this under "Judgement Calls" and everybody can move on. |
|
#11
|
||||
|
||||
|
Re: What we learned from week 1
The rule itself acknowledges that this type of contact may occur and is not a foul. The purpose of G29 is to make clear that the element must be purposeful and the damaging contact deliberate in order for there to be a foul. I do not believe I "dismissed a whole catagory of fouls." Since I wtnessed this contact myself, I was offering my opinion that it did not violate any foul rule.
|
|
#12
|
|||||
|
|||||
|
Re: What we learned from week 1
Quote:
I'm sorry, but that right there dismisses the fact that any rule applies to what happened. Rule G29 specifically applies to what happened, was it violated is a completely different question. |
|
#13
|
||||
|
||||
|
Re: What we learned from week 1
Quote:
G29 refers specifically to robot elements outside the frame perimeter which are purposefully used to cause damage to another robot. That rule does not apply here, if for no other reason than because 16 had no such element. Two robots came in contact while pushing when one of them tipped. If you would like for that to be called as a technical foul in your match, you may want to be careful what you wish for. |
|
#14
|
|||||
|
|||||
|
Re: What we learned from week 1
Quote:
|
|
#15
|
||||
|
||||
|
Re: What we learned from week 1
It is silly to debate the content of something that is in writing. The rule and its blue box explanation speak for themselves. I don't think the rule applied to this situation, but that is just my opinion, which is all it ever was.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|