Re: Cheesecake: How far is too far?
 

In my opinion, "too far" is when a robot shows up for playoffs that wasn't there for qualification rounds, and nobody else had a chance to select it.

If cheesecake is to be limited by new rules, I hope they strike a reasonable balance that still allows/encourages stronger teams to help struggling teams, and still allows teams in playoffs to keep their machines in top form. I like the idea of unrestricted upgrades during the qualification matches (with the required re-inspections), but with some sort of design/configuration freeze after that. Perhaps a total freeze with no changes allowed that meet the criteria for re-inspection. Perhaps a partial freeze with some nominal allowance (a couple of pounds?) for upgraded parts. No restrictions on repairs, maintenance, or software (as currently allowed without re-inspection). In summary, no significant mechanisms in playoffs that were not present in at least one qualification match.

Another thing I think would be interesting - something that would reduce the incentive for cheesecake at championship - would be to go back to three team alliances for division playoffs, with backup bots drawn from unpicked robots as needed. Then, after the division winners have been decided, let them pick their "backup bot" from any of the teams in their division. This would create "super alliances" that truly represent the best that their division had to offer, and make Einstein matches the best they could be.

Re: Cheesecake: How far is too far?
 

What would be the problem with the following rule? (Yes, I've brought this up in another thread, but it seems relevant here.)

"FABRICATED ITEMS/MECHANISMS/COMPONENTS brought into an event (including those on their ROBOT) must be used on the ROBOT of the team that brought them. Teams are encouraged to bring in raw materials and COTS items to assist other teams at the event. COMPONENTS/MECHANISMS that are on a ROBOT that competes in a match become part of that team's ROBOT for the remainder of the event."

In addition, what would happen if alliance selection at regionals took place AFTER lunch, and the elimination/playoffs started after a short "figure out your strategy" session?

This would allow all sorts of alterations, improvements and teams working together, but would prevent a team from bringing in a pre-built component and putting it on another team's robot. They could build something to help any team they wished, but that "cheesecaked" team would be available for any alliance to select.

- Mr. Van
Coach, Robodox

Re: Cheesecake: How far is too far?
 

Team 4063 is well known for helping team with their robots between matches when they are in need, whether it be donating spare parts, lending tools, etc. Once in a while, we'll see a team that comes to a regional with no robot built in the entire season (for reasons unknown to us because we consider it rude to ask why that's the case), and those teams are usually the ones we prioritize helping, so we'll help them build a robot from the ground up. So the question is, would this be considered cheesecaking or not? Last year we helped a team build a defensive robot so they will at least have the opportunity to compete, but we did it for no strategic reason whatsoever, just good ol' Gracious Professionalism. So a concern for us is, indeed, how far is too far? In a sense we are building an entire robot for them (with the team's actual support and help, of course, and usually that team will tell us what their robot should contain) and if any restrictions were made, we would no longer be able to do this. Also people could try to bend the rules by saying they're doing something like what we do, but who knows? It's hard to even take this poll baring our team's philosophy in mind. It's a shame to see something like cheesecaking in a program that aspires for professionalism, which only means we still have ways to go.

Re: Cheesecake: How far is too far?
 

I always got the sense that cheesecaking implied that the help you give to the other team has some sort of quid pro quo attached to it, e.g. "I'll help you modify your robot / I'll choose you for my alliance if those modifications do what I want/need". If your motivation is simply "I'll help you because I want to help / I feel bad you have no robot / it's the right thing to do" then I don't consider that cheesecaking.

Re: Cheesecake: How far is too far?
 

I wrote the poll with the following definition of cheesecake in mind:

Cheesecake: Adding parts, components, mechanisms, or structures brought by one team onto another teams robot to enhance that robots ability.

Helping all teams compete at their best, whether it improves your own chances at winning or not, is at the heart of GP. Even if a team isn't on your alliance, where do we draw the line? Einstein had Canburglars from a FIM team that was knocked out at the divisional level. Clearly this was GP, but it also was cheesecake.

Re: Cheesecake: How far is too far?
 

I don't believe that anyone is talking about limiting a team's ability to help another team.

Perhaps we can make four distinctions:

1. Team A brings COTS and stock and helps team B with their robot. Team B competes with and against team A throughout the competition.

2. Team A brings components/mechanisms and puts them on team B's robot (most likely with team B's help). Team B competes with and against team A throughout the competition.

3. Team A brings COTS and stock and modifies/rebuilds team B's robot only because team B is (or is expected to be) part of team A's alliance.

4. Team A brings components/mechanisms and puts them on team B's robot (with team B's help) only because team B is (or is expected to be) part of team A's alliance.

I strongly encourage scenario 1, and I would be surprised if anyone would object to it. I believe that all of the positive elements of "cheesecaking" can be found in this scenario.

Things get a little (or indeed a lot) less clear in the other situations.

- Mr. Van
Coach, Robodox

Re: Cheesecake: How far is too far?
 

I love this quote. My thoughts exactly.

I like how this would definitely reduce the huge redesigns unless the alliance is going to field 2 bots for the first few matches. The only problem I see is that the 3rd bot for the Division win is then most likely going to be sat out for the Einstein matches in favor of the "backup".

Re: Cheesecake: How far is too far?
 

...create any number of rules...someone will find a loop hole.

Re: Cheesecake: How far is too far?
 

Design a game that requires cheesecaking to win, and it will happen no matter what rules are created to try and prevent it.
Design a game that doesn't require cheesecaking to win, and it won't happen even if there aren't rules created to try and prevent it.

As long as cheesecaking is required to win, it will happen. The chokehold strategy requiring a complex mechanism, limited game pieces, cluttered field, and lack of defense in Recycle Rush required it, and it happened.

Ban the ingredients for cheesecake, and stores will find substitutes. Remove the market for them, and stores have no reason to make them.

Re: Cheesecake: How far is too far?
 

Eh. Cat is out of the bag now.

973 is likely going to regionals next year with 3rd picks that in an average game won't contribute much.

We will likely be able to make a sub 30 pound mechanism that allows our 3rd to be statistically far better than the other teams available in the draft.

If the rules don't change, we must assume that others are doing this as well. If we assume others are doing it, we must do it to remain competitive.

Re: Cheesecake: How far is too far?
 

Everybody blames this on the game design, but I'd argue that cheesecaking has always been a viable strategy for teams who are extremely competitive.

In 2014, your third pick could become an autonomous shot blocker.
In 2013, your third pick could get a 50 point climb and dump mechanism, or a full court shooter.
In 2012, your third pick could get a bridge stinger to help balance or a simple shooter to throw balls to your side.
In 2011, your third pick could get a minibot deployment and minibot.
In 2010, your third pick could get a climber.
In 2008, your third pick could become a 30 pound lap bot.

Cheesecaking is also deceptively difficult.

Re: Cheesecake: How far is too far?
 

At this point you might as well let teams bring their practice bots and enter those in the competition too. :rolleyes:

Re: Cheesecake: How far is too far?
 

I've only been in FRC for two years, but from what I saw last year, 2nd picks (assuming that was what you meant) weren't on average that much better than this year in terms of individual scoring capability. Yet I didn't see cheesecaking to this extent. Maybe I just didn't pay as much attention, but I don't remember this debate at regionals or on CD.

Would cheesecaking robots from 2014 help alliances? Yes. Why wasn't it done then? Was the idea really not thought of until this year?

I guess a better question would be:
If we replayed Aerial Assist, would we see cheesecaking to the extent that we saw it in Recycle Rush?

Re: Cheesecake: How far is too far?
 

So we might need a new name for this kind of help. "Cheesecake" suggests a delicious, possibly unplanned dessert.

The arms race Adam's post anticipates is not about dessert, it is about supplements. Where is FIRST's boundary between wheat germ and steroids?

Re: Cheesecake: How far is too far?
 

I believe you are right about this. This puts struggling teams who actually attempt to accomplish the game challenge at a competitive disadvantage compared to those teams who anticipate "cheesecaking" and simply provide a "cheesecake pan".

Is this what we want?

- Mr. Van