Re: What did it take to win a Week 1 Rebound Rumble match?
 

This makes perfect sense.
You know what your team can do, but imagine if it was vice versa?
Without mentioning specific teams, I saw it to be just the case in eliminations......where the widebot was waiting at the end of the bridge for their partner to balance with them on the bridge. It failed when they needed it the most, and was the difference between advancing vs. being eliminated.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

From my experience at Hatboro-Horsham (which, granted, now seems to be one of the best events of week 1), it was rare that teams weren't attempting to get on a bridge during a match. Balls under bridges caused many failures, especially if teams didn't leave time to cross the bump or couldn't cross the bump. Many other teams, including 1712, didn't have functioning bridge manipulators and had to follow up other teams.

Because of this, 1712 only once tried to balance on our own alliances' bridge during qualifications (we tipped with 1 second remaining), but had seven attempts at balancing on the co-opertition bridge (three successful, two where the other team never went for the bridge, and twice where we "failed"/ran out of time). Without the ability to manipulate the bridge ourselves, we figured the best way to ensure QPs was the co-op bridge with a balancing machine from the other alliance. The 4 coop points we had at the end of Friday were a big portion of why we were seeded 5th at the time. Some bad luck on Saturday and other teams starting to use the co-op bridge more led to us falling to 13th, but the concept was proven.

Our bridge manipulator should be functioning and durable by Lenape, so we'll see if our strategy changes.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

I guess my comment stems from the title more so than the presented data. A QS of 22 seemed on average to be good enough for 1st or 2nd seed. As I see it during qualification rounds there are 20 opportunities to get 2 points. 11/20 doesn't seem that great to me. The point being that winning is not everything as the tournament structure is different this year.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

KC only had 9 matches, so our average may be a bit higher than it appears from raw numbers. As for the average -- I don't think a lot of teams thought through the scoring system enough, and didn't realize that coopertition points would be so important, win or lose. I don't like having them so important, but they are what they are. I think this will change dramatically in the coming weeks, and 22 will soon not be enough to get you in the top 10.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

I only looked at SMR data, but 45 of the 81 qualifying matches were decided by 10 points or less, so without a lot of detailed review that would imply the ability to balance at least one robot would be very beneficial. Many matches the winning score was <10, so either alliance balancing just one robot could have won that match. In 28 of the 45, at least one alliance had less than 10 points, so a single balance could have changed the outcome.

From the matches I watched, I think a key was to be flexible. Many matches just needed one robot to balance to win, but alliances were trying for 2 and then ended with o.


It would be interesting to look at all the match data from week 1 and see the "margin" trend.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

i feel the best way to win was getting out onto the field as many times as possible during practice as the more practice you get the better you get, we got out a dozen times during practice and it helped us alot expecially balancing on the bridge and learning how we want to play the game.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

Another "Heads-up" to teams going in to competitions in the coming weeks regarding teams trying to get 2 or 3 robots onto a bridge when 1 fewer would decide a match...

We witnessed the other end of that situation in a critical elim match where a single robot balanced a bridge with some time to spare instead of going over to allow an alliance partner to join them. The match was decided by fewer than 10 points, meaning that additional robot would have been decisive.

Part of the problem...and the "Heads Up"...at the GKC regional, only the Blue Alliance Drive Teams were facing the projected score board and it took more of a concerted effort on the part of the Red Alliance to continue monitoring the scoreboard during the final seconds of the match. We had coaches monitoring the board but in the heat of battle, they weren't successful in conveying the message to the involved drivers that the additional robot was the only way of winning the match.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

Ask and you shall recieve. I'm still waiting on someone to parse the FRCFMS twitter feed for me, as the margins we care most about are the ones where the alliance had the opportunity to make up the difference. That is, if you lose by 10 points but already balanced two robots you couldn't have done more.

25% of matches were decided by less than 5 points, 50% by less than 10, 75% by less than 19, and 90% by 30.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

Ask and I shall receive eh.. well it would be nice if data was separated by elims and quals. I imagine this request may be too difficult though.

Re: What did it take to win a Week 1 Rebound Rumble match?
 

I would be interested to know what the winning score data without bridges is. Ie, how many baskets do you need to make to get a chance of winning?

Re: What did it take to win a Week 1 Rebound Rumble match?
 

All of the data he has posted so far was just qualification matches.