|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||||
|
||||||
|
Re: paper: Stop the Stop Build
Quote:
I know, I know, Zebracorns feel that they were not taken advantage of. I hear you. And I don't care. Well that is too strong of a statement. I care, in fact, I am happy for Team 900. It was a good experience for you. But I STILL think that such excessive cheesecaking was bad for the sport. The typical team in the future will not have a great experience having their hard work (for 6 weeks ;-) being pushed to the side so that a top team can cheesecake the snot out of them. Dr. Joe J. |
|
#2
|
|||
|
|||
|
Re: paper: Stop the Stop Build
I agree. One of the strongest motivational factors that sustains a team (IMO) is the sense of ownership the students have in their machine. Win or lose, being able to watch your robot on the field and knowing that part of it exists due to your hard work and effort is a powerful thing.
Last edited by Tim Sharp : 07-09-2016 at 15:00. Reason: Grammer |
|
#3
|
|||||
|
|||||
|
Re: paper: Stop the Stop Build
Quote:
Most years, "cheesecaking" consists of relatively minor, relatively low tech additions dreamed up on the spot, in a collaborative effort between teams. Alliances are largely selected on the base competency of the robot a team showed up at the event with, and cheesecake provides minor enhancements. In 2015, we had a game uniquely suited to cheesecaking, largely because of just how completely the vital canburgling task could be completed via a self-contained, sub 30 pound mechanism, developed and brought in entirely by another team, and how few less than elite teams put any effort whatsoever into this task, or developed systems with a prayer of being competitive at it. As a result, we started to see some teams picked more on their willingness to abandon elements of the robot they brought in. And at the end of the season, cheesecake and its possibilities being in people's minds lead to us seeing a new robot built from the ground up at an event, based largely on design work done by another team prior to the event. The debates over whether or not this was a positive thing have been beaten to death. But one indisputible fact about the experience remains: the harpoon build was a monumentally difficult feat for all teams involved. It required an unprecedented level of coordination, pre-planning, and engineering skill. We've only seen it once, and I don't know that we'll ever see anything quite like it again. If we do, it'll be hard not to be in awe of the teams that pull it off, and the amazing accomplishment will once again overshadow any sourness about the ethics of attempting it. One can say similar things about teams that manage to pull off mid-season full-bot rebuilds under the bag system, and arguments about design convergence. However, the difficulty of this feat was almost 100% artificially generated, through the bag rules and withholding rules. Getting rid of bag and tag would presumably also erase poundage limits on fabricated items that a team can bring to competition with them. Which brings up the logical questions: What stops teams, many of whom are already building multiple robots, from bringing in pre-built "Cake-bots," ready to roll as-is with different team numbers slapped on (or Cake-tops that can bolt on top of a kitbot, if FIRST adopts VRC-style definition of a robot)? Would the hypothetical gains in performance of the average team be enough to erase an elite team's motivation to do this? Would the sense of collaboration and involvement by all teams so often quoted regarding past extreme cheesecake endeavours always be maintained? Would we want to stop this at all, or would it be a positive thing to a degree? EDIT: To be clear, I don't anticipate this ever becoming a widespread thing, nor do I mean to suggest that certain teams are ready and waiting to do this, only held back by the current ruleset. But the door does open up if we aren't careful. Last edited by Joe G. : 07-09-2016 at 15:51. |
|
#4
|
|||
|
|||
|
Re: paper: Stop the Stop Build
Quote:
I don't see this as ever becoming widespread as I don't think there are that many teams who would ever consider this as an acceptable way to participate in FRC, especially on the part of the receiving team. Then again, I'm not from an ultra-competitive district, so perhaps the mentality really is that different there. I know our students would be pretty offended if someone suggested that we do that. |
|
#5
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
That said, cheesecake limits are a separate issue from Bag/Witholding, and should be addressed with separate rules. The GDC tried to put in some rules last year, but they probably went too far. I think it's possible to strike the right balance with something like a separate weight limit, but that's a different conversation. |
|
#6
|
|||||
|
|||||
|
Re: paper: Stop the Stop Build
Random thought on cheesecaking.
Would teams cheesecake less if they were allowed to enter multiple robots for less-than-ridiculous costs? We would probably enter 3-4 robots if it didn't cost an arm and a leg. The amount of time we could commit to cheesecaking would definitely taper off at that point. I think a lot of FRC's issues boil down to program cost actually. Hmmm... -Mike |
|
#7
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
Edit: Makig clear what I was highlighting. Last edited by marshall : 07-09-2016 at 15:45. |
|
#8
|
|||
|
|||
|
Re: paper: Stop the Stop Build
I don't see the need for half-measures here. Don't give everyone an unbagging time slot, just get rid of the bag entirely. The current policy is regressive and unfair, and lessened version of it is still going to be regressive and unfair, only somewhat less-so.
This might just be me, but I can't envision this doing anything but further exacerbating the gap between high- and low-resource teams and breeding a lot of ill-will. For instance, I don't think many people would take kindly to seeing an elims bracket at district championships consisting of multiple robots from only a handful of "elite" teams. That might be a more accurate reflection of the distribution of resources in FRC (both monetary and human), but I doubt it's what's best for the program. Last edited by Oblarg : 07-09-2016 at 15:38. |
|
#9
|
|||||
|
|||||
|
Re: paper: Stop the Stop Build
Quote:
I know this has basically been done with 494 and 70, but that is a sort of unique situation that had a large opportunity cost. |
|
#10
|
||||
|
||||
|
Re: paper: Stop the Stop Build
-snip-
I mistook that "Page 2 of 5" for "Page 5 of 5." Please disregard. Last edited by Cothron Theiss : 09-09-2016 at 03:48. |
|
#11
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
Tell you what, forget I brought it up. I'm good without the public display of mental gymnastics that is someone coming to terms with their own cognitive dissonance. |
|
#12
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
![]() |
|
#13
|
||||||
|
||||||
|
Re: paper: Stop the Stop Build
Quote:
I have obviously offended you (and all of Team 900?). That wasn't my intent. Sorry for that. AND... I have a views on how the world should work. I do my best to come up with a consistent set of values which you graciously call mental gymnastics and talk of cognitive dissonance. From my point of view, our differences boil down to this: regarding excessive cheesecaking, I come down against it while you come down on the other side. Can we disagree without insulting each other? Maybe? Dr. Joe J. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|