If 2590 wins Hatboro-Horsham, they will have won this event 4 times in a row.
Not listed for Hatboro-Horsham are 203 and 708, who have really built up their programs over the past several years. I expect them to be competitive there.
2607 and 303 don’t get a lot of press outside of MAR–they both won a lot of competitions last year both in-season and during the off-season, and I would expect to see them fielding strong robots again this year.
EDIT: Not sure how I missed mentioning them before–1218 won two districts and was a Championship division alliance captain and finalist last year. They’ll definitely be competitive at Hatboro-Horsham.
There are lots of great MAR teams playing this weekend!
I’m shocked we got a mention here since we aren’t playing this weekend. We’ll be watching though and best of luck to all of the teams in NC. It’s a fun game so we know you’ll enjoy playing it!
These are my favorite pre competition summarys. Thanks for the mention! Should be a really good competition this weekend. With so many normally good teams at the event, there should be a deep field for eliminations compared to many district events.
I was wondering the same thing. I got really excited for a minute and thought that I had missed your name on the teams participating. Also who is 3791? A quick blue alliance search shows that they folded in 2012. I am assuming you meant team 3971, Kai Orbus. I know my team cannot wait to compete in the first ever NC District event.
Thanks for the kind words. Although we tend to improve our robots greatly throughout the season, our first events have typically been good to us. I was surprised the home team 2907 wasn’t mentioned as they won the event with us in 2014 and were finalists with us in 2015. We’re looking forward to seeing what they, and all the PNW teams, have in store this weekend.
Gotta agree here - although Bear Metal used to struggle week 1, over the last couple years we’ve become far more successful in week 1… it’s DCMP that’s been giving us issues :v
I love reading these posts, and then marveling over how you got some of this information
I just wanted people to take note of 865 as well. Over the course of GTC last year, they improved their robot by leaps and bounds, and I eventually saw them intake totes from the landfill faster than 1114. I wouldn’t be surprised to see them rank very high.
I’m really looking forward to see how teams will apply the lessons learned from Palmetto, as well as seeing if anyone has any secret plans in mind…
We got off to a slow start this weekend, but I’m happy with the way the robot turned out in the end. The hanging mechanism should be ready to go in Central Washington in two weeks and I think we’ll have a more well-rounded machine at that time. Still, I think we demonstrated that we were one of the better machines focused on breaching at Auburn. We’re super into our portcullis crossing mechanism.
More importantly, however, I want to thank team 1983 for helping us out in a big way after we received the bad news from our sponsor. The sheet metal shop we’ve worked with for the last three seasons has been great to us, but late in week four, we learned that they wouldn’t produce any of the remaining parts we’d asked them to make. We redesigned everything above our drive over the next day and team 1983 graciously offered to allow us to cut plates on the waterjet in their shop. Without their help, we may not have finished a working robot in time for bag day.
We had a great weekend as #8 in San Diego an we beat the #1 alliance that had the best HG shooter…2-0
We broke our hex shaft ,a team had one and in the hour before our SF we fixed that …then our shooter got stuck in SF and the camera was off so we were driving blind so we lost…we failed mechanically and lost to eventual winners.
It was great . Our bot performed extremely well we scaled 3 times all the way up. Only counted once… one time they winched to high and we lowered at last second. The other the driver was excited and started 2 seconds early. Then one that was PERFECT in our first QF match so beautiful. Took all regional to get the scaler tuned to the field with modifications.
Now it should be great for Central Valley later this week. We are excited to have one more shot. This time with a modified shooter and steel hex shaft possibly auto HG still working on that…we might have to move our camera the tomahawk blocks the processing … we get readings but the view is not good enough yet. If we get that working too wow.
Thanks for the mention! It’s nice to know that people are noticing our hard work and efforts despite having many, many difficulties at Hatboro. Nonetheless we had a great time and are definitely aiming to contend at Seneca!
Chesapeake District - Northern Virginia Event:
Especially so coming off a build season that in a region not prepared for the type of winter weather that hit, which cut into many team’s testing and iteration time. That could play into the advantage of teams like 1418, who finished early and had plenty of time to troubleshoot and refine their low goal and scaling specialist machine. Similarly, it could work against 116 and 612, who have often struggled early in the season as they get the kinks worked out of their machines. While fine tuning a machine at early events is a viable strategy in the regional format, losing those points in districts can spell doom for a team’s DCMP or CMP hopes.
Spot on LF! Programmer from 612 here, we spent a fairly large amount of time working on fixes for our robot in the time between matches, especially on the first day. However, this year we’ve done a lot better than we have in the past few years, and by the morning of the second day we were able to shoot high goal and cross every defense, though we only shot high goal once in my recollection during a match and we could not handle a few defenses (the sally port for example) without help.
Even though we are usually around the middle of the pack, this year we came out very strong. We oscillated between first and sixth place throughout the day, ending at 6th after our last match and moving up to the 5th place alliance captain. This coming competition (week 4) we plan to be even stronger with a ton of code work and some mechanical fixes.
