![]() |
Los Angeles Regional Finals Match Defense
Hi CD, as I was watching the finals match at the LA Regional between 1197, 987, 5012 vs 294, 330, 1452, I noticed how significantly a defense bot can swing your match and in this case, decide the Regional Winner. 330s robot was flipped twice out of the three finals matches, causing 330 to lose many potential points in both matches, and perhaps being a reason that alliance lost both of those matches.
I was wondering how this might effect team strategy at future regionals, seeing that the refs were okay with harsh defense and didn't card the defending robot who was seemingly the reason for 330s tip. Thoughts? PS I'm a first time poster, so please let me know if I'm practicing any ill advised posting methods. Thanks!! :) |
Re: Los Angeles Regional Finals Match Defense
I have not seen the matches in question so take all this with a huge grain of salt.
Usually a robot tipping because of collision with another robot is at least in part a result of an unusually high center of gravity on the robot that was tipped. If you are building a robot for a game where defense can be played, you should assume that defense will be played and design accordingly. At what point do we consider defense too vigorous or a robot to be poorly designed? I do not know. There is a little bit of blame on both sides of that I am sure. Edit: you must mean 294 not 254 |
Re: Los Angeles Regional Finals Match Defense
Quote:
|
Re: Los Angeles Regional Finals Match Defense
Quote:
|
Re: Los Angeles Regional Finals Match Defense
Quote:
|
Re: Los Angeles Regional Finals Match Defense
Quote:
Just my 2¢. |
Re: Los Angeles Regional Finals Match Defense
5012 has built a very impressive resume as being clutch in elims. I was at LA and these matches were incredibly fun to watch. 330 even managed to recover from one of the tips. I was shocked that they were still around and somehow dropped to the 23rd pick. bold prediction time: 5012 will be playing defense on Einstein.
|
Re: Los Angeles Regional Finals Match Defense
Quote:
|
Re: Los Angeles Regional Finals Match Defense
Quote:
|
Re: Los Angeles Regional Finals Match Defense
Link to the first match of the finals: http://www.youtube.com/watch?v=IulNn2whPXw&t=54m2s
Tip #1: https://www.youtube.com/watch?v=IulNn2whPXw&t=55m55s Tip #2: https://www.youtube.com/watch?v=IulNn2whPXw&t=1h31m55s Tip #2 was pretty awesome because 330 was able to right themselves even though they were completely upside down. Judging from all the matches during the regional, defense was a huge part in the winning alliance strategies. Pretty much every ranged shooter was struggling to make high goals when a defender robot collided with them during the shooting process. You can see this during the 3rd final's match when 1452 was easily harassing arguable two of the best shooters at the regional (before their robot lost connection :( ). 330's robot was unique because it braced itself against the bottom of the tower, making it nearly impossible to defend... Until it tipped. From my memory, 330's robot only tipped 3 times during the regional, all cases during playoffs, and two in the finals. 330's robot center of mass was fairly high, especially when its shooter arm was fully extended. Combined with a nudge directly against it side, it isn't surprising that they fell over. However, in one of the previous play off matches, a low center of mass robot was completely flipped upside down by a defender, and the defender's robot alliance was penalized with a dq for the match. When the same thing happened to 330 twice during the finals, myself and many others around me (even listen to the commentator) expected the game would be automatically awarded to 330's alliance by dq. The fact this was not the case brings up questions about the scope of defending. In a case of a tip, when is it considered a warning or dq? Hopefully other teams at the regional know more information regarding the subject. So a few things to learn from the regional. Defending is very important, especially if the other alliance has a ranged shooter of any capability. Also, if possible, teams might want to consider creating a shooting algorithm where their robot is flesh against the bottom of the tower. Defense seemed pretty rough this year, so team should work on a case to deal with that. |
Re: Los Angeles Regional Finals Match Defense
Disclaimer: LA stream was down during these matches, and I didn't see 5012 in action.
I have been thinking about this too, after seeing 3316 tipped during the playoffs in Israel. Without any "true" safe zones for teams to take advantage of, this sort of scenario is inevitable for tall robots. While it should not be the goal to tip your opponent on its back or side, defenders shouldn't have to show any less agression towards tall robots. Teams should design accordingly... I am concerned about many of these tall robots and I expect to see a lot of rebuilds done before DCMP's/CMP. |
Re: Los Angeles Regional Finals Match Defense
There is a VERY fine line between hitting a robot that produces a tip and continuously pushing a robot after it begins to tip.
5012 performed hit without intent to flip (as determined by the refs at that moment) 5089, as determined by the refs at that moment, intentionally pushed 3863, causing 3863 to flip in QF4-3 at Los Angeles. The red alliance got a red card for that match due to the flip. |
Re: Los Angeles Regional Finals Match Defense
How does pinning apply to tipping? If a robot were to start a flip on a robot and cause an opposing robots wheels (or treads) to be off the ground it has prevented the robot from moving, wouldn't this meet the requirements of a pin? If so then it means that starting a flip is legal just finishing it isn't.
I dunno how I feel about that. |
Re: Los Angeles Regional Finals Match Defense
Quote:
|
Re: Los Angeles Regional Finals Match Defense
I don't know if it's just me, but it looked like 5012 helped 330 get into a better position to right themselves after they tipped in F3. If that's true, I'd say that was pretty classy of 5012.
|
| All times are GMT -5. The time now is 22:09. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi