![]() |
Predictions Week 4: Marking the Thrower
A variety of strategies continue to be successful in Ultimate Ascent, but there's one factor that dramatically changes how the game is played; the presence of full court shooters. Regardless of their success, a robot with this capability being on the field changes the complexion of the match entirely. It goes well beyond the hastily constructed pool noodle and duct tape blockers, as both alliances will adapt their strategy in an attempt to manipulate the radically different game play to their benefit. It doesn't always work out for the full court shooter, especially if their alliance isn't flexible enough to put up significant points from elsewhere, but their presence makes an impact.
When a legitimate full court shooter is present in the eliminations, the other alliance typically attempts to either block their shots and/or prevent them from reaching the protected corner loading station. Some alliances chose to counter this by scoring primarily from the pyramid, hoping they can outscore the opposition in a more typical fashion, with the threat of the full court shot forcing the opposing defense to remain "honest" (especially if an 84" blocker locks the defender into their own auto zone, cuts off their route underneath the pyramid, and sometimes prevents them from hanging). The winners at Central Valley, Northern Lights, and Springside-Chestnut Hill used other alliance partners to clear the corner and fend off blockers to establish the corner shooter's position and allow them to rack up as many points as possible (even at the expense of offense elsewhere). However, this hasn't always been successful, as shown in the St. Louis finals match 2, where 1444 and 1288 weren't able to clear enough space for 1706's shots to avoid 3284's unfolding blocker. In Greater Kansas City, 1806 often served as a decoy to shift the defensive attention away from 1986's quick and consistent cycles. It doesn't matter much if the full court shooter is targeting the 2-point goal or gunning for 3s. The constant stream of discs is usually enough to heavily swing the tele-op score in favor of one alliance. The exception being when 2826's flurry of two pointers quickly fell behind the three pointers being launched from the opposite corner by 2169 at Northern Lights. It will be intriguing to see if the two-pointers continue to work as the season progresses, especially when matched against high octane scoring machines capable of 4+ cycles. Just as the prior weeks, week four will have several full court shooters in play. Many high profile teams opted to shoot from the pyramid, including ones capable of launching the length of the field. This decision particularly makes sense for the shorter and quicker robots, such as 987, 610, and 118, who would have serious problems with blockers but utilize their ability to scoot underneath the pyramid well. This has often presented an opportunity for lesser known teams to make a name for themselves as full court specialists. This weekend will showcase some of each (as well as plenty of competitive bots of other designs), many of which will be competing for the second time. Watch to see how their competitors adapt to them, and how their strategies have evolved with an event under their belt. Observations and foresight:
|
Re: Predictions Week 4: Marking the Thrower
Sad note about 71 to end on, Looking Forward. :(
Good luck to all teams competing this weekend. PS- I would add 219, 222, and 193 into the mix for Mt. Olive district. 193 is MORT Beta and definitely will be a factor at this event. |
Re: Predictions Week 4: Marking the Thrower
987 was initially signed up for the Utah Regional, but withdrew. We don't compete again until the Las Vegas Regional.
|
Re: Predictions Week 4: Marking the Thrower
With all due respect, Looking Forward, the exclusion of 2481 at Wisconsin is crazy. Finalist (as #1 seed) twice in the last three seasons, fastest minibot on Newton in '11 and this year bring a 23 second climb and dump, and an accurate shooter. After 2826, I think 2481 is the favorite to win Wisconsin.
At Wisconsin, I also wouldn't forget about 3940 (climber-dumper with an 18 pt auto), 1716 (slot loaded, accurate pyramid shooter) and, as a deep sleeper, 2039 (tall, full court shooter). |
Re: Predictions Week 4: Marking the Thrower
We're carrying in a replacement for all of our frisbee-related functionality. It's mostly a bolt-on job; tear off the old top and replace it with the new one, but there's a bit of rewiring work to be done as well.
We've switched from a linear-ish storage system for frisbees that caused a lot of control systems challenges to a collector + bucket system. We should be collecting frisbees much faster now and, with the mechanism that was causing frisbees to jam completely gone, firing much faster and more reliably. And in the 3 pt. goal, too. The new system replaces everything -- new collector, new bucket storage, and new shooter -- and reuses only the electronics board. The whole thing is about 22 lbs. We prototyped a bit with buckets in the week after Portland, designed the entire new system in about 3 hours on Saturday morning and had the entire thing assembled and testing by Sunday evening. I'm not sure what took us 6 weeks the first time around. :) |
Re: Predictions Week 4: Marking the Thrower
2512 is competing at Midwest, not Wisconsin.
Otherwise, awesome predictions! |
Re: Predictions Week 4: Marking the Thrower
Quote:
Last time 256 went to Davis we were finalists. Who knows, maybe we'll keep our record (or do better). |
Re: Predictions Week 4: Marking the Thrower
Quote:
I think 930 is notable at the Wisconsin Regional as well. **1716 will be bringing some improvements to WI which will include a faster redesigned shooter and a fun defensive weapon. |
Re: Predictions Week 4: Marking the Thrower
Watch for 379 at Queen City.
|
Re: Predictions Week 4: Marking the Thrower
Also watch out for 1726 the nerds and 4183 bitbuckets. Nerds did pretty well at San Diego and I hear Bitbuckets have a pretty solid robot this year. Az should be fun this year!
|
Re: Predictions Week 4: Marking the Thrower
I'd keep an eye on 2557 in Central Washington, along with the others.
|
Re: Predictions Week 4: Marking the Thrower
Gonna drop in team 2403 for Arizona. They seem to have a super clean and effective robot this year. http://www.youtube.com/watch?v=RgX8VGxl7Jw
|
Re: Predictions Week 4: Marking the Thrower
Quote:
|
Re: Predictions Week 4: Marking the Thrower
Quote:
1318: Played well in Oregon 2517 shoots with authority, but seemed to have accuracy problems in Oregon. Looking at their bot up close and seeing the potential, I would keep an eye on them too this weekend. We are not an insta-lock, but I'm hoping that we can go out and play with some of our friends and find a spot on a strong alliance :) |
Re: Predictions Week 4: Marking the Thrower
Quote:
|
Re: Predictions Week 4: Marking the Thrower
Quote:
Quote:
|
Re: Predictions Week 4: Marking the Thrower
Quote:
|
Re: Predictions Week 4: Marking the Thrower
Congrats to you and the rest of your alliance, Jim! A well deserved win for sure.
|
Re: Predictions Week 4: Marking the Thrower
Thanks Joe! I'll see you at the Vegas regional, cheering on the High Rollers, with Travis' folks. And my brother's team the Bit Buckets 4183 will be playing.
|
Re: Predictions Week 4: Marking the Thrower
Quote:
-Brando |
Re: Predictions Week 4: Marking the Thrower
Quote:
|
Re: Predictions Week 4: Marking the Thrower
Quote:
|
Re: Predictions Week 4: Marking the Thrower
Unfortunately 229 has played out their official season, unless they somehow get a slot in St. Louis. Luckily the other half of the Clarkson pair will be able to make their mark at Championships this year.
From what I've heard 229 really stepped up their game between BAE and Boston, It looks like the #1 alliance had some tough competition in those semi-final matches. I'm proud to hear that they turned up their offensive power, and came home with a Quality award. |
| All times are GMT -5. The time now is 21:55. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi