Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
-   -   The Dark Side of the 2013 game (http://www.chiefdelphi.com/forums/showthread.php?t=115276)

Chris is me 28-03-2013 16:26

Re: The Dark Side of the 2013 game
 
Quote:

Originally Posted by Hoover (Post 1253962)
From what I've gleaned robot tipping cannot be done as a strategy, so then the alternative is that it can be done as a knucklehead. But then this would be not in the spirit. So has anyone seen a case in 2013 when a robot was tipped by another and no technical foul was called? Stories?

We have tipped robots three times this year. At no time did we ever intend to - we simply pushed the robots and they went over. We were never called on it. If you build a tippy robot, the rules do not offer you protection against simple defense. Only clearly intentional tips (e.g. hitting a robot up high outside its bumper zone, driving hard into a partially tipped robot to "finish the job", etc) are called for technical fouls, as they should be.

Quote:

Side note. I've noticed that the technical fouls seem to be 30 points, is this a modification from 20 in the glossary of the original publication?
They are 20 points. If the technical foul interfered with a hang, the alliance is given 30 hanging points.

Quote:

I noted in one of my earlier posts that in another match a robot hit another robot, but since the second robot was top heavy... but it wasn't only that. The four wheels were almost to the frame perimeter. This plus the top heaviness and the robot slammed right over, boom. This happened right in front of us (on the stands) and I wasn't the only one who raised one brow. So to all of those who say you can't build a robot that will purposely tip, it can be done at least passively. There currently is no inspection test for some kind of minimum bumper hit.
All other things equal, wouldn't wheels farther to the edges of the frame perimeter result in a less tippy robot?

Quote:

How does this jive with the idea of 5.4.4 (about ties) "the ALLIANCE that played the cleaner MATCH", implying that fouling is, how should I say it politely, not clean? In basketball, is fouling part of the dark side of that game, or just strategy?
This is an ongoing debate in the FRC world. In the past, intentional fouls have been worth it in niche situations, but in this game a "strategic foul" gets you a potential yellow card, according to the rules and Q&A.

OZ_341 28-03-2013 16:29

Re: The Dark Side of the 2013 game
 
I am only answering because it is the original poster.
My issue was not with the onfield play or the officiating.
As I mentioned, a rough game is just fine with me and we build for it.

My issue is with the lack of sportsmanship in the crowd.
My problem is with those audience members and teams that were openly calling for a fellow competitor (225) to be tipped. Those same people actually cheered and high-fived when it happened. This is just so far from what FIRST is about.

coalhot 28-03-2013 16:50

Re: The Dark Side of the 2013 game
 
Quote:

Originally Posted by OZ_341 (Post 1253972)
My issue is with the lack of sportsmanship in the crowd.
My problem is with those audience members and teams that were openly calling for a fellow competitor (225) to be tipped. Those same people actually cheered and high-fived when it happened. This is just so far from what FIRST is about.

This. Also, I should point out the times where there have been chants mocking an alliance when the set goes to a third match, because the underdog won. I heard this at CH, and at Mt Olive. Very, very, very un-GP; and the first time I've seen/heard it in this area. Personally, I think it's because too many teams in the area are focused on winning matches. I'd like to think that any team that I was on would not stoop this low.

EDIT: I was sitting right behind the section that was cheering when 225 was tipped. It's quite rude to hear this. The teams in the area are better then this. I'd also like to think that the refs had warned the alliance that tipped 225, and that they would have red carded the alliance if it happened again. Tipping the robot one can be an accident, but once it happens multiple times, it becomes a strategy. Also, I'm glad that 225 was able to garner a strategy to prevent themselves from being tipped.

Lil' Lavery 28-03-2013 17:04

Re: The Dark Side of the 2013 game
 
FWIW, while the competitors certainly looked to up the ante when playing agaisnt 225 at Lenape-Seneca (including a number of blocking devices), there wasn't really any unsportsmanlike behavior centered around them that I was aware of. I remember a gasp the one time they fell over, but no rampant cheering. I also know there was at least one other team who constantly cheered for and chanted 225's name/number during qualifications. Nor do I recall any particularly egregious crowd behavior at Hatboro-Horsham, though I was hardly around the audience at that event.

It's a real shame to hear it went different at SCH and MO. :(

Ben Martin 28-03-2013 17:23

Re: The Dark Side of the 2013 game
 
Quote:

Originally Posted by coalhot (Post 1253978)
EDIT: I was sitting right behind the section that was cheering when 225 was tipped. It's quite rude to hear this. The teams in the area are better then this. I'd also like to think that the refs had warned the alliance that tipped 225, and that they would have red carded the alliance if it happened again. Tipping the robot one can be an accident, but once it happens multiple times, it becomes a strategy. Also, I'm glad that 225 was able to garner a strategy to prevent themselves from being tipped.

For what it's worth, of the three times we tipped (from videos I have watched) only the time in Chestnut Hill SF2-1 could be considered the fault of the opposing alliance.

Regardless of how the crowd reacted at Chestnut Hill, the event staff, volunteers, and the drive teams I worked with were extremely gracious at both events.

Hoover 28-03-2013 17:40

Re: The Dark Side of the 2013 game
 
Quote:

Originally Posted by Chris is me (Post 1253970)
We have tipped robots three times this year. At no time did we ever intend to - we simply pushed the robots and they went over. We were never called on it. If you build a tippy robot, the rules do not offer you protection against simple defense. Only clearly intentional tips (e.g. hitting a robot up high outside its bumper zone, driving hard into a partially tipped robot to "finish the job", etc) are called for technical fouls, as they should be.

This is a good clarification. After the driver tipped the robot, when he turned he hit within their frame perimeter. This was due to clumsiness and no way intentional and it wasn't a hard hit. After the event was over I heard one opinion that the latter is what the foul was for. I never addressed a ref on it and I could cleared this whole thing up then and there.

Quote:

They are 20 points. If the technical foul interfered with a hang, the alliance is given 30 hanging points.
Oh never mind on this as I realize this was total total fouls since that is all that is displayed.

Quote:

All other things equal, wouldn't wheels farther to the edges of the frame perimeter result in a less tippy robot?
Yes. Now I am thinking this is what made it even more out of context about the hit. It could just be the top heaviness of the robot did all the work. I'd still like to have seen the force that took to do it in a test.

Quote:

This is an ongoing debate in the FRC world. In the past, intentional fouls have been worth it in niche situations, but in this game a "strategic foul" gets you a potential yellow card, according to the rules and Q&A.
I well know; when we play an alliance that has an offense that is much higher order than us, it is a balancing act on how much defense we can apply. Could it be that FRC wants the winning robots to win on the merits of how good the robots are built and not how much they can be denied performance? I think that is an obvious yes.


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

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