View Single Post
  #184   Spotlight this post!  
Unread 02-03-2015, 18:02
PayneTrain's Avatar
PayneTrain PayneTrain is offline
Q&A Dartboard Detractor
AKA: Lizard King
FRC #0422 (The Meme Tech Pneumatic Devices)
Team Role: Mascot
 
Join Date: Mar 2010
Rookie Year: 2009
Location: RVA
Posts: 2,271
PayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond reputePayneTrain has a reputation beyond repute
Re: Week 1 Observations

Quote:
Originally Posted by Breadbocks View Post
I disagree with the "Robots control their own fate" thing. This year, more than ever, you're vulnerable to bad matchmaking.

This time, you're running the risk of being shafted by the opposing alliance not doing coop. Coop points are half of the baseline 80 points that's going to be expected of every single team every qualification match in coming weeks, and you 100% cannot do the entire coop stack yourself. If you get matched against potatoes, your ranking is going to drop, and drop precipitously. Our team dropped from top 4 to what eventually became 9th because the opposing alliance never put a 4th tote on the coop stack in one match, which was brutal on our average.
1) Wait, you're telling me that you think each team should be averaging 80 on their QA in the coming weeks? Currently available data for mean QA for week 1 didn't even break HALF of that. I would be shocked if mean QA ever hit 80 before CMP.

2) While this is a true thing that does suck, 148, 3824, and other high ranking teams ranked high with <50% co-op stack conversion rate. I know our rank dropped precipitously because by the time we fixed our robot we hit a stretch of matches without co-op capability on the opposite side of the step. It's an issue we're looking to solve in two ways for our next event.
Reply With Quote