View Single Post
  #17   Spotlight this post!  
Unread 29-06-2013, 11:12
Pault's Avatar
Pault Pault is offline
Registered User
FRC #0246 (Overclocked)
Team Role: College Student
 
Join Date: Jan 2013
Rookie Year: 2012
Location: Boston
Posts: 618
Pault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond repute
Re: [FAF] - June 28, 2013 - Game Design Committee

Quote:
Originally Posted by inkling16 View Post
Sometimes, when looking at a complaint about scoring values, it is useful to look at the team's context. Team 3289 competed at the Utah regional, they went 10-4 overall. The lost one qual match to the Hawaiian Kids (enough said, you guys are awesome). In their other 3 losing matches, they played against 1891, the best high-level climber there.

Believe me, I know how it feels to lose matches because there are other robots that can do things that your robot cannot, it stinks. Afterward, all that I think is what ifs.
What if we had spent our time designing a minibot deployment system.
What if we had had different wheels so that we could balance more easily.
What if we had built a climber instead of a floor pick-up device.
I can definitely see what you mean. This year my team competed in 2 competitions so far: the Boston Regional and Beantown Blitz.* At the Boston regional, we played a qualification match, a replay of that match, and 3 semifinal matches against 3173, a fcs. We won the 2 qualification matches because 3173 was broken, and then we won the first semifinal match, but then they beat us twice. At Beantown Blitz we played 195, a fcs, 4 times: 2 qualification matches and 2 quarterfinal matches. We lost to them 4 times. After seeing this, members of my team compared the simplicity of 3173 and 195 to our relatively complex floor pickup robot, and it began to seem like we made a bad design choice. We weren't angry at anybody because of it, but I can see why the asker might have needed someone to place the blame on.

*We attended the WPI regional, but it would be a big stretch to say that we competed in it.

Quote:
Originally Posted by inkling16 View Post
This is the one statement that I have trouble with:

["If the side events score is decreased, maybe we can get back to all-around robots vs. specialized 'point bots'."]

Personally, I would much rather see 10 FCSs, 10 ground pick-up bots, 10 3rd-level climbers, 10 cyclers, and 10 defenders that are all specialized than 50 all-around so-so robots when I go to a competition. Then, when we all play, it will become apparent what the strongest strategy is. Engineering is optimizing and trade-offs. FRC is the same. Choose the best strategy that your team can manage, then optimize until you run out of ideas, brainstorm some more, and optimize again. If the GDC wanted, they could make games where only one thing happens, and we would all become excellent at optimizing. But they don't, because they want us to make trade-offs.

I hope the best for you guys, 3289. You appear to have done well this year. My one suggestion would be to spend 1 more day in the early build season analyzing the game and determining trade-offs.

EDIT: Pault added in 3289's context, beat me to it
I agree with the askers statement, actually. He is not saying he wants 50 all-around bots, he's saying he wants a few all-around bots mixed in with all of the specialized bots. I would love a game like that. Then, you still get the design trade offs, and you still get to see which strategy is best, but at the same time you have some of the best teams building these bots that are so inspirational because they manage to do everything. Just look at 118's reveal video this year. And even the decision to be an all-around robot is a trade off because it could easily be more effective to just specialize.
Reply With Quote