Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
-   -   Cheesecake robot. How far is too far? (http://www.chiefdelphi.com/forums/showthread.php?t=145504)

MaGiC_PiKaChU 03-09-2016 09:46 PM

Cheesecake robot. How far is too far?
 
Hello CD. I was thinking about it with a friend, and we consider building an entire robot at an event to give away as cheesecake to our 3rd alliance member. This seems entirely within the rules. The robot would be able to drive around. Is it too far? How would you feel competing with a robot you did not build? Opinions?

The other Gabe 03-09-2016 09:48 PM

Re: Cheesecake robot. How far is too far?
 
whether or not it is within the rules, it would be neither gracious nor professional to imply that their robot was worthless by giving them a completely different one

it would also be a poor allocation of your pit space and resources, IMO

MaGiC_PiKaChU 03-09-2016 09:50 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by The other Gabe (Post 1554744)
whether or not it is within the rules, it would be neither gracious nor professional to imply that their robot was worthless by giving them a completely different one

it would also be a poor allocation of your pit space and resources, IMO

Not saying it is worthless... Just had a unique design in mind that can win elimination rounds quite easily

carpedav000 03-09-2016 09:53 PM

Re: Cheesecake robot. How far is too far?
 
I think once you get to a point where you have to make considerable (anything beyond adding a cheesecake platter) changes to a team's base/frame, that's taking it too far.

FrankJ 03-09-2016 10:05 PM

Re: Cheesecake robot. How far is too far?
 
Basic chassis with bumpers plus minimum electronics, motors, & drives is approaching $2000. That is a lot of cheese cake. Would you let them keep it?

throwaway 03-09-2016 10:05 PM

Re: Cheesecake robot. How far is too far?
 
If you can find a team willing to use it then it's find IMO.

MaGiC_PiKaChU 03-09-2016 10:10 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by FrankJ (Post 1554762)
Basic chassis with bumpers plus minimum electronics, motors, & drives is approaching $2000. That is a lot of cheese cake. Would you let them keep it?

That is one valid point. thank you

Okeegan55 03-09-2016 10:10 PM

Re: Cheesecake robot. How far is too far?
 
Wouldnt the robot have to fit inside the 30Ib of extra parts restriction?

JohnSchneider 03-09-2016 10:10 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Okeegan55 (Post 1554767)
Wouldnt the robot have to fit inside the 30Ib of extra parts restriction?

Kitbot is all COTS.

MaGiC_PiKaChU 03-09-2016 10:11 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Okeegan55 (Post 1554767)
Wouldnt the robot have to fit inside the 30Ib of extra parts restriction?

We plan to build it from scratch at the event... Also, not with the kitbot

Caleb Sykes 03-09-2016 10:13 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by The other Gabe (Post 1554744)
whether or not it is within the rules, it would be neither gracious nor professional to imply that their robot was worthless by giving them a completely different one

it would also be a poor allocation of your pit space and resources, IMO

If you had a gameboy advance, and I gave you a 3DS, am I implying that your gameboy advance is worthless?

IronicDeadBird 03-09-2016 10:14 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Caleb Sykes (Post 1554772)
If you had a gameboy advance, and I gave you a 3DS, am I implying that your gameboy advance is worthless?

I don't care I've got a free 3DS now and I keep my GBA...

GreyingJay 03-09-2016 10:49 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Caleb Sykes (Post 1554772)
If you had a gameboy advance, and I gave you a 3DS, am I implying that your gameboy advance is worthless?

If you baked a pie to bring to a potluck and I gave you a cheesecake and told you to bring that instead, am I not implying that your baking skills are undesired?

marshall 03-09-2016 10:52 PM

Re: Cheesecake robot. How far is too far?
 
I can't believe this is still a discussion...

GreyingJay 03-09-2016 11:00 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by marshall (Post 1554801)
I can't believe this is still a discussion...

Now I'm hungry.

*any student on my team would say "He's always hungry!"

Chief Hedgehog 03-09-2016 11:01 PM

Re: Cheesecake robot. How far is too far?
 
Wow - there is a large gray area of cheesecaking that would be crossed. It is one thing to help a team create new manipulators so that the team competes at a higher level...

As for building an entirely new robot for a team that already worked for six weeks on their own - yes, that is crossing a line.

However, there was a point at Lake Superior where a few teams got together in case a rookie team did not have one ready to go. Luckily for all involved - the rookie team showed up with a robot that was nearly ready to go. That being stated, the robot DID need some major work - and kudos to FRC 93 and FRC 1816 the team was ready to go at the end of the day on Thursday.

murphy14 03-09-2016 11:04 PM

Re: Cheesecake robot. How far is too far?
 
Whether or not it is going too far is debatable. However, i feel that it is very against the point of FIRST, which is for students to work together with other students and overcome challenges as a team. Simply the fact that you have to ask this question should be enough of a answer.

ratdude747 03-09-2016 11:08 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by MaGiC_PiKaChU (Post 1554771)
We plan to build it from scratch at the event... Also, not with the kitbot

Lots of raw stock then. Unless you order it pre-cut, you'd have to cut all of it in the pits.

---

The fact that one team builds it, to me, is not in the spirit of first. At least the 900/1114 Harpoon rig was a combined effort. Just picking a team to drive it, to me, is indeed too far.

GreyingJay 03-09-2016 11:17 PM

Re: Cheesecake robot. How far is too far?
 
It also kind of minimizes every part of the build season in favour of only looking at (presumably) winning. It says to me, never mind all the strategy work and planning and designing and time management and skill learning and testing and coding and teamwork and practice that you did during your build... forget all that and drive this instead because this will win more.

I would say this would be a grand gesture for a team that has had trouble getting something rolling and effective. The team that looks like they barely had time to assemble a working kitbot might appreciate this gesture on Thursday or Friday of a regional. A team might be interested in collaborating with you to build this ala the Simbacorns Harpoon Initiative. But I wouldn't want to be on a team that felt briefly elated because they were chosen only to find that the choosing team had an ulterior motive and no desire to use what they built.

dtengineering 03-09-2016 11:18 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by MaGiC_PiKaChU (Post 1554741)
Hello CD. I was thinking about it with a friend, and we consider building an entire robot at an event to give away as cheesecake to our 3rd alliance member. This seems entirely within the rules. The robot would be able to drive around. Is it too far? How would you feel competing with a robot you did not build? Opinions?

I know the manual is pretty long, and that sometimes people don't read ALL the way through, but... um... R1 is pretty close to the beginning:

Quote:

R1 A Team must submit their ROBOT for Inspection. The ROBOT must be an electromechanical assembly built by the FIRST Robotics Competition Team to perform specific tasks when competing in FIRST STRONGHOLD. The ROBOT must include all of the basic systems required to be an active participant in the game – power, communications, control, BUMPERS, and movement. The ROBOT implementation must obviously follow a design approach intended to play FIRST STRONGHOLD (e.g. a box of unassembled parts placed on the FIELD, or a ROBOT designed to play a different game does not satisfy this definition).

R1 requires that the ROBOT a Team uses in competition was built by
that Team
, but isn’t intended to prohibit assistance from other Teams
(e.g. fabricating elements, supporting construction, writing software,
developing game strategy, contributing COMPONENTS and/or
MECHANISMS, etc.).
Emphasis mine. Feel free to give away whatever you want, but maybe read at least one of the rules before suggesting your strategy is "entirely within the rules".

Sorry if that seems a bit snarky... some FRC rules can be difficult to figure out, or hard to notice. But they were pretty clear about this one...

Jason

IronicDeadBird 03-09-2016 11:37 PM

Re: Cheesecake robot. How far is too far?
 
Also if you haven't alreayd made and tested the robot how do you know its worth replacing a robot on an alliance?

FIMAlumni 03-09-2016 11:41 PM

Re: Cheesecake robot. How far is too far?
 
Similar discussion from last season with poll results from the community. Last year 16.20% of voters thought a new cheesecake robot should be allowed. Cheescake: How far is too far?

MaGiC_PiKaChU 03-09-2016 11:42 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by IronicDeadBird (Post 1554834)
Also if you haven't alreayd made and tested the robot how do you know its worth replacing a robot on an alliance?

I can't know that. I believe it's worth the try

JohnSchneider 03-09-2016 11:53 PM

Re: Cheesecake robot. How far is too far?
 
Is the plan to have a drive team compete with a robot for the first time in eliminations? Because if you give it to them before I would bet that it gets drafted. Then what? You reposes the robot? Both situations sound like poor decisions even if it finished skirting the legal grey area.

Ginger Power 03-10-2016 12:16 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by marshall (Post 1554801)
I can't believe this is still a discussion...

It's going to be one of those annual threads like the mentor build vs. Student build, Regionals vs. Districts, and Mentor vs. Student Drive coaches. Unsurprisingly, all of those topics have been discussed in the last 3 days.

The Ginger 03-10-2016 01:04 AM

Re: Cheesecake robot. How far is too far?
 
What if the robot frame was made of cheese cake? :cool:

cj3958 03-10-2016 01:07 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by The other Gabe (Post 1554744)
whether or not it is within the rules, it would be neither gracious nor professional to imply that their robot was worthless by giving them a completely different one

it would also be a poor allocation of your pit space and resources, IMO

Clearly someone wasn't at champs last year... Or wasn't paying attention to 1114's pit...

Caleb Sykes 03-10-2016 01:19 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1554798)
If you baked a pie to bring to a potluck and I gave you a cheesecake and told you to bring that instead, am I not implying that your baking skills are undesired?

You offering me cheesecake does not make my pie "worthless." That is the particular word to which I was responding. If I have a decent pie, and you have some spectacular cheesecake that you want to give to me, that doesn't automatically make my pie un-edible, and it doesn't necessarily mean you think I am a horrible cook.

hectorcastillo 03-10-2016 01:32 AM

Re: Cheesecake robot. How far is too far?
 
I'm confused. Is there or is there not going to be free cheesecake at Alamo?

Akash Rastogi 03-10-2016 01:54 AM

Re: Cheesecake robot. How far is too far?
 
I'm very pro-choice about this issue. I think a team has the right to do with their robot whatever they want, even if it means doing away with their whole existing robot and creating a new one using a donating team's parts or full robot.

IronicDeadBird 03-10-2016 04:43 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by MaGiC_PiKaChU (Post 1554836)
I can't know that. I believe it's worth the try

Approach a team with...
"We have an idea for the robot and the materials but we haven't tested it at all we would like to run this untested robot instead of your robot."

That'll turn some heads.

logank013 03-10-2016 06:14 AM

Re: Cheesecake robot. How far is too far?
 
This has definitely been a topic before on our team but hasn't been discussed a lot. I won't talk about others on my team's views but I will talk about mine.
Basically, I believe the the line has been crossed when it forces a main component of the robot to be unfunctional.
Example: a team has spent 3 or 4 weeks developing their shooter. Despite shooter capability, it is wrong to make them stick a PVC pipe in front of it allowing them to not be able to shoot a boulder.
Cheesecaking is fine when you are adding to it but as soon as you take something away, despite how much you added, you are telling them that their robot isn't good in that part you took away. Does this make sense? Despite our team being an alliance captain much of the time these last two years, I never see our team Cheesecaking and alliance partner's robot. It is fine to a slight extent but most first teams who do it want to cross the line. Unfortunately, there is no rule against it.

jwfoss 03-10-2016 07:44 AM

Re: Cheesecake robot. How far is too far?
 
I would advocate that if you think you have the time and are willing to put the effort into building a second robot at an event for a potential alliance partner, your time would be better spent helping those teams at the event that need it most. Raising the floor will give you more options come alliance selection time, and improve the event for everyone.

Sperkowsky 03-10-2016 07:50 AM

Re: Cheesecake robot. How far is too far?
 
I do not see an issue with it. If that team gets to win now because of the robot you gave them that is great.

Lil' Lavery 03-10-2016 07:57 AM

Re: Cheesecake robot. How far is too far?
 
Why not borrow a team shirt from the team you drafted and have your back-up driver drive the bot you built for them, as well? The drafted team still get to win, right?

Quote:

Originally Posted by jwfoss (Post 1554909)
I would advocate that if you think you have the time and are willing to put the effort into building a second robot at an event for a potential alliance partner, your time would be better spent helping those teams at the event that need it most. Raising the floor will give you more options come alliance selection time, and improve the event for everyone.

"You must spread some reputation around before giving it to jwfoss again"

IronicDeadBird 03-10-2016 08:01 AM

Re: Cheesecake robot. How far is too far?
 
If you have the resources for another robot practice bots are always nice.

Dan Petrovic 03-10-2016 08:09 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Ginger Power (Post 1554849)
It's going to be one of those annual threads like the mentor build vs. Student build, Regionals vs. Districts, and Mentor vs. Student Drive coaches. Unsurprisingly, all of those topics have been discussed in the last 3 days.

You left out the topic of 6 Week Build Schedule vs No Build Schedule Restrictions.

CJ_Elliott 03-10-2016 08:12 AM

Re: Cheesecake robot. How far is too far?
 
I think conversation comes down to some people think that it would be fine or don't care and some do care. Personally, I think it should be between the teams to decide whether or not to take the cheesecake bot. IMO everyone that isn't those teams should mind their own, if you are against having your team change robots then don't. Simple as that.

marshall 03-10-2016 08:14 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1554912)
Why not borrow a team shirt from the team you drafted and have your back-up driver drive the bot you built for them, as well? The drafted team still get to win, right?

A couple of years ago we witnessed a team do exactly this but with a human player instead of a driver. We lost a regional because of it. More specifically, the other alliance gained a huge advantage since they had two human players who could load their own robot.

A couple of our students were quite mad/frustrated with me that I would not contest it but winning or replaying matches because the other side broke the rules is not how we want to win. From our reading that year, the rules actually prohibited this and have since. Notice that I said "the rules" and not the "spirit of the rules" or "spirit of FIRST".

But hey, what do I know about cheesecaking? :rolleyes:

Lil' Lavery 03-10-2016 08:24 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by marshall (Post 1554927)
But hey, what do I know about cheesecaking? :rolleyes:

I have interpreted this line (and others like it) to implicitly mean "we've been cheesecaked, we liked it, therefor it MUST be good and ALL teams should like it." Can you tell me if I have interpreted that incorrectly? If so, can you clarify what you mean by it?

marshall 03-10-2016 08:27 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1554934)
I have interpreted this line (and others like it) to implicitly mean "we've been cheesecaked, we liked it, therefor it MUST be good and ALL teams should like it." Can you tell me if I have interpreted that incorrectly? If so, can you clarify what you mean by it?

I meant that I had derailed the thread slightly and was trying to put the train back on track but you can take my post however you'd like to.

Taylor 03-10-2016 09:17 AM

Re: Cheesecake robot. How far is too far?
 
Conceptually, I am firmly against cheesecaking, for many reasons I won't bother to list here.

Then I think about 2013, when we completely rebuilt our robot at INTH, with the help of another team who gave us parts and labor that helped us immensely, and we told the judges about it and this team won the GP award at the event, and we were by the letter of the definition the recipients of cheesecake.

So my personal conclusion is the same that I've reached across many other false dichotomies in our landscape - student v mentor built, child v adult coach, etc.

If it works for that team in that situation, then good for them.

GreyingJay 03-10-2016 09:35 AM

Re: Cheesecake robot. How far is too far?
 
To me it comes down to the mindset of the receiving team. Did they want cheesecake? Did they expect cheesecake?

"We were in trouble and team XYZ saved the day by giving us their ABC (or helping us make ABC with their resources)" - awesome. Super GP, teamwork, good for everyone involved.

"We were in trouble so we approached team XYZ and offered our drive base as a platform to build an awesome alliance strategy involving harpoonsABC" - also cool.

"We were picked by team XYZ but it turns out all they wanted was something they could attach their ABC to. We didn't even get to use our own" - not awesome. Not GP. Good for the cheesecaking team but not exactly morale boosting for the receiving team.

Akash Rastogi 03-10-2016 09:45 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1554968)

"We were picked by team XYZ but it turns out all they wanted was something they could attach their ABC to. We didn't even get to use our own" - not awesome. Not GP. Good for the cheesecaking team but not exactly morale boosting for the receiving team.

Different strokes for different folks.

Any time I've selected a team, their role is always discussed prior to selection and roles are always agreed upon. Most teams have enough mutual respect to discuss these things.

What boosts morale for one team versus what might boost yours don't have to be the same...

taaha_alidrisi 03-10-2016 10:03 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by The other Gabe (Post 1554744)
whether or not it is within the rules, it would be neither gracious nor professional to imply that their robot was worthless by giving them a completely different one

it would also be a poor allocation of your pit space and resources, IMO

I've seen powerhouses teams help out the 3rd robot in their alliance by giving them major mechanisms but to respect their hard work and effort during the construction you should keep it at that mere minimum.

In addition, it's not a mere cheesecake robot if it's a full robot (in the 30lbs or not). Investing that money for other expenses would be the most beneficial decision.

taaha_alidrisi 03-10-2016 10:08 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by CJ_Elliott (Post 1554923)
I think conversation comes down to some people think that it would be fine or don't care and some do care. Personally, I think it should be between the teams to decide whether or not to take the cheesecake bot. IMO everyone that isn't those teams should mind their own, if you are against having your team change robots then don't. Simple as that.

But the question comes to fairness as if you were competing in a regional elimination rounds and the other alliance you're competing with has a cheesecake robot for their 3rd robot member... Hence, shouldn't you care if it affects you closely (and it does as the main post by 3360 goes to the Montreal Regional like the team I'm in 3386).

MaGiC_PiKaChU 03-10-2016 10:12 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by taaha_alidrisi (Post 1554981)
But the question comes to fairness as if you were competing in a regional elimination rounds and the other alliance you're competing with has a cheesecake robot for their 3rd robot member... Hence, shouldn't you care if it affects you closely (and it does as the main post by 3360 goes to the Montreal Regional like the team I'm in 3386).

Since it may affect you and your team, mind if I ask how you would feel playing finals against such an alliance, and not winning because of that?

Lil' Lavery 03-10-2016 10:15 AM

Re: Cheesecake robot. How far is too far?
 
Not sure why it's still being ignored, but dtengineering already explained why an 100% "cheesecaked" robot is illegal.

taaha_alidrisi 03-10-2016 10:26 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by MaGiC_PiKaChU (Post 1554982)
Since it may affect you and your team, mind if I ask how you would feel playing finals against such an alliance, and not winning because of that?

Going against such an alliance makes the other competing teams face unfairness. Of course some teams have more resources and it will never change but doesn't it make you lose the fundamental values of FIRST ? Not winning is not the end of the world but knowing you had chances of winning stripped away from you because of some gray areas and irregularities in regulations, that just wrong from my point.

BetaHelix 03-10-2016 10:28 AM

Re: Cheesecake robot. How far is too far?
 
In my opinion if you have to cheesecake a whole new bot into you alliance, it says a whole lot about your strategy. If you are so focused on needing this one exact type of robot that you will completely remove a functional robot from the field, it is a poorly drafted strategy. A major part of FRC strategy is the aspect of adapting to what you have and applying problem solving skills. If you can't find one speck of utility in someone else's design, you find a role for them, or you don't pick them.

Also cheesecake is not an instant win. At one of our regionals we saw one of the top alliances take the entire lift of of a robot so they could replace it with can grabbers, and they ultimately only came in second to an alliance of three bots who worked together.

As a student and the drive coach of a mid tier team, I support improving existing systems that teams have build, but oppose adding new ones that are untested or risk removing current robot function

Caleb Sykes 03-10-2016 10:45 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1554984)
Not sure why it's still being ignored, but dtengineering already explained why an 100% "cheesecaked" robot is illegal.

Yes, 100% cheesecake is illegal. This thread still has value though, since anything between 1% and 99% cheesecake is potentially still legal.

nrgy_blast 03-10-2016 11:38 AM

Re: Cheesecake robot. How far is too far?
 
The rules are pretty clear: you alone can't build a robot for another team, but you can help them build an entirely new robot in the time available with 'raw materials' and COTS parts. Since the rules allow it, it's going to happen. And since the rules allow it for everyone involved, there is nothing 'unfair' about it.

If you don't like something about the rules, go out and lobby the rules committee. But good luck, not even CD can agree on what 'should' be allowed.

GreyingJay 03-10-2016 11:49 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Akash Rastogi (Post 1554975)
Any time I've selected a team, their role is always discussed prior to selection and roles are always agreed upon. Most teams have enough mutual respect to discuss these things.

What boosts morale for one team versus what might boost yours don't have to be the same...

Let's just say "I have a friend" whose team was selected by another team for the sole purpose of (massively) cheesecaking their robot, that these plans were not discussed in advance and came as a complete surprise to the receiving team, and that the entire experience was frustrating, demoralizing and even humiliating for the team being cheesecaked.

All I'm saying is, as you have said, if all teams involved are open about their intentions and agree to it, then it's fine -- but if it isn't open and discussed prior to selection, then it's not fine at all.

JohnSchneider 03-10-2016 11:51 AM

Re: Cheesecake robot. How far is too far?
 
Think about it from FIRSTs side. Obviously this is not in the "spirit of FIRST" so as FIRST what are your options to stop people from building their own alliance partners?

1) You could extend withholding weight to include COTS parts. Which hurts everyone.

2) You aren't allowed to bag 2 robots, but what if they bag all the parts to make a robot? Now FIRST has to say "You can only bag your robot and no other parts"

3) A plausible solution could be to include a maximum financial cost on withholding, COTS and bagged parts to ensure that a second robot cannot come in while allowing you to have spares for yourself.

All 3 of these solutions would hurt teams as the FIRST metagame stands now. Is it really worth opening that can of worms?

pfreivald 03-10-2016 12:22 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1555025)
Let's just say "I have a friend" whose team was selected by another team for the sole purpose of (massively) cheesecaking their robot, that these plans were not discussed in advance and came as a complete surprise to the receiving team, and that the entire experience was frustrating, demoralizing and even humiliating for the team being cheesecaked.

It is for this that the word "no" was invented.

"Hi, new partners! We selected you so that we can strip off your upper mechanical and add this stuff that we made!"
"No."
"...but we'll probably win if we do that!"
"No."
"...but that's the whole reason why we selected you!"
"Then you should have gotten us on-board with that before selecting us."
"Sorry, our bad. But you're okay with this so we can win, right?"
"No."

Daniel_LaFleur 03-10-2016 12:37 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1554968)
To me it comes down to the mindset of the receiving team. Did they want cheesecake? Did they expect cheesecake?

For me, it's more about inspiring the receiving team.

It's very hard to inspire someone by telling them that you only picked them so that you could cheesecake their robot, and far easier if you talked to them prior to picking them.

Lil' Lavery 03-10-2016 12:56 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Daniel_LaFleur (Post 1555055)
For me, it's more about inspiring the receiving team.

What about the inspiration of the teams not picked? The other alliances? The spectators?

The impact of actions such as this shouldn't be solely evaluated based on the team receiving the "cheesecake."

Jared Russell 03-10-2016 01:02 PM

Re: Cheesecake robot. How far is too far?
 
Ethics and rules aside...

ain't nobody got time for that.

BobbyVanNess 03-10-2016 01:04 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1554984)
Not sure why it's still being ignored, but dtengineering already explained why an 100% "cheesecaked" robot is illegal.

While that could be circumvented by having the receiving team involved in the production, 5.5.2 states that:

Quote:

Each registered FIRST Robotics Competition team may enter only one (1) ROBOT (or ‘Robot’, which to a
reasonably astute observer, is a Robot built to play FIRST STRONGHOLD) into the 2016 FIRST Robotics
Competition.
Now if the one robot entered is significantly modified instead of replaced, that would likely satisfy this.

As for the ethical side of this argument, I think it stands that this should be agreed upon BEFORE alliance selections. If this isn't agreed upon with the alliance captain and leadership of the team being selected, then it's the picked team's call as to whether or not they alter their robot.

That being said, I don't think it's unreasonable to request this of a team if it's for the better of the alliance. If this is something that could lead to an event win, then I personally think it'd be a bit foolish for a team to refuse to consider the potential gains. It is, however, unacceptable to EXPECT this of a team.

Personally, I'd rather have the blue banner with a modified/altered robot and intelligent alliance strategy than go home empty handed because I let pride trump logic.

Nuwanda 03-10-2016 01:05 PM

Re: Cheesecake robot. How far is too far?
 
Isn't the goal of FIRST to inspire students towards STEM? It's more than just the robot and certainly more than winning. Helping a team add a mechanism without disabling other features of their robot can be beneficial to everyone. However, picking a team to completely rebuild or replace their bot isn't. The situation on Curie with 1114 last year was difficult to watch. I wouldn't have wanted to be on the team being rebuilt. Seeing six weeks of work go down the drain wouldn't have been worth a win for my team. The point should be people putting forward their own work and what they've learned. If winning is worth more than that dedication and work, I wonder if you're doing this for the right reasons. You can help other teams without throwing away everything they've done.

Lil' Lavery 03-10-2016 01:09 PM

Re: Cheesecake robot. How far is too far?
 
Nuwanda, the "situation on Curie" last year was initiated by team 900, not 1114. They approached 1114 with the idea. There's already extensive discussion of that situation in other threads. No reason to rehash that here.

Quote:

Originally Posted by bobby5150 (Post 1555072)
While that could be circumvented by having the receiving team involved in the production, 5.5.2 states that:



Now if the one robot entered is significantly modified instead of replaced, that would likely satisfy this.

Discussions of cheesecaking in general have already occurred in multiple threads, almost all of which happened within the past year. This thread was brought up for the specific purpose of discussing an entire robot being given to an alliance partner to replace their robot.

GreyingJay 03-10-2016 01:13 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Nuwanda (Post 1555073)
The situation on Curie with 1114 last year was difficult to watch.

That was a very interesting example because in that case clearly 900 was willing to do it, and there was a lot of notoriety over this particular case, but I think it backfired on them in the end. There were a number of matches where only two robots came out to play. Presumably 900 was busy being cheesecaked at the time. The alliance ended up losing a semifinal by only a few points. Had a third robot been out stacking, even if they had only managed to stack a few totes, I believe that would have been enough to up the average alliance score high enough that they would have won.

And we never got to see the harpoons in action :(

Daniel_LaFleur 03-10-2016 01:15 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1555065)
What about the inspiration of the teams not picked? The other alliances? The spectators?

The impact of actions such as this shouldn't be solely evaluated based on the team receiving the "cheesecake."

Would you rather I don't inspire that team?

The other Gabe 03-10-2016 01:17 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by cj3958 (Post 1554874)
Clearly someone wasn't at champs last year... Or wasn't paying attention to 1114's pit...

actually, we were beaten in finals on our field by that alliance.

the harpoon situation was a combined effort, built in team 900's pit (so of course I wasnt paying attention to 1114's pit, the stuff was happening in 900's!), and agreed upon before they were picked. I'm not saying it's something I entirely supported (I mean, the harpoons were damned cool, so I liked that bit), but that was something in which the team that was cheesecaked was totally cool with it and not surprised by their robot being completely replaced.

marshall 03-10-2016 01:18 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1555077)
That was a very interesting example because in that case clearly 900 was willing to do it, and there was a lot of notoriety over this particular case, but I think it backfired on them in the end. There were a number of matches where only two robots came out to play. Presumably 900 was busy being cheesecaked at the time. The alliance ended up losing a semifinal by only a few points. Had a third robot been out stacking, even if they had only managed to stack a few totes, I believe that would have been enough to up the average alliance score high enough that they would have won.

And we never got to see the harpoons in action :(

Sorry to correct but 1923 was the third robot (1114 and 148 being the first two) and they were out playing. The loss on Einstein had little to do with our (900's) cheesecaking.

BenBernard 03-10-2016 01:23 PM

Re: Cheesecake robot. How far is too far?
 
What bothers me about this thread is how far from "gracious professionalism" some writers seem willing to stray in their pursuit of "winning at all costs."

Sperkowsky 03-10-2016 01:29 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Jared Russell (Post 1555070)
Ethics and rules aside...

ain't nobody got time for that.

RI3D at the competition?

GreyingJay 03-10-2016 01:40 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by marshall (Post 1555081)
Sorry to correct but 1923 was the third robot (1114 and 148 being the first two) and they were out playing. The loss on Einstein had little to do with our (900's) cheesecaking.

Ah, thank you for the clarification.

Still never got to see those harpoons :(

Lil' Lavery 03-10-2016 01:44 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Daniel_LaFleur (Post 1555078)
Would you rather I don't inspire that team?

I would rather you consider the totality of the actions, rather than just the impacts on one team. I already posted similar thoughts on this back in April, during the previous round of cheesecake debate.
http://www.chiefdelphi.com/forums/sh...1&postcount=87

mentos54 03-10-2016 01:44 PM

Re: Cheesecake robot. How far is too far?
 
Also, consider what this does to the receiving team's reputation, both inside and outside the team.
I mention this because last year, my current team's robot was cheesecaked with a major mechanism by a powerhouse team. We went on to win the event with them.
However, the members of my team who talk about winning that competition have found themselves shamed by new members because "they didn't build the robot that won, they borrowed it". I honestly believe that major cheesecaking is almost never beneficial in the long run, and your resources would be better spent finding a team which is close to what you need and helping them perfect their bot. If your needed partner is nothing close to what any of forty teams have, you're strategizing wrong.

Zebra_Fact_Man 03-10-2016 01:45 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1554934)
I have interpreted this line (and others like it) to implicitly mean "we've been cheesecaked, we liked it, therefor it MUST be good and ALL teams should like it." Can you tell me if I have interpreted that incorrectly? If so, can you clarify what you mean by it?

Quote:

Originally Posted by marshall (Post 1554937)
I meant that I had derailed the thread slightly and was trying to put the train back on track but you can take my post however you'd like to.

The salt is palpable.

Honestly I think we should spend more time combining different controversial topics into SUPER Controversial topics, such as:
- If we ended bag and tag, would teams cheesecake more or less?
- Is student-built cheesecake better or worse than mentor-built cheesecake?
- Can a team competing in one World Championship cheesecake a team in a second World Championship?
- Can a mentor who mentors both the cheesecaking team and the cheesecaked team replace the student coach on the cheesecaked team?
- If you yell "Cheesecake" while transporting the cheesecaked robot through the pits, does it make the pits safer and/or the cheesecake better?
- Can teams later cheesecake the cheesecaked robot at the district championship, and again at Nationals?

#WeBrokeTheGame?

CJ_Elliott 03-10-2016 01:48 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by pfreivald (Post 1555042)
It is for this that the word "no" was invented.

"Hi, new partners! We selected you so that we can strip off your upper mechanical and add this stuff that we made!"
"No."
"...but we'll probably win if we do that!"
"No."
"...but that's the whole reason why we selected you!"
"Then you should have gotten us on-board with that before selecting us."
"Sorry, our bad. But you're okay with this so we can win, right?"
"No."

I like this. From what I have seen, if a team doesn't want to do something then they will say no and it probably wont happen. In all actuality I find it more frustrating to see people say that it's not gracious professionalism to use cheesecake. If the two teams agree on it then it is a decision that is made by both teams and nothing says anything about the choosing alliance member forcing the picked alliance member to put something on their robot, which would be entirely against what FIRST wants.

MaGiC_PiKaChU 03-10-2016 01:48 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by mentos54 (Post 1555098)
Also, consider what this does to the receiving team's reputation, both inside and outside the team.
I mention this because last year, my current team's robot was cheesecaked with a major mechanism by a powerhouse team. We went on to win the event with them.
However, the members of my team who talk about winning that competition have found themselves shamed by new members because "they didn't build the robot that won, they borrowed it". I honestly believe that major cheesecaking is almost never beneficial in the long run, and your resources would be better spent finding a team which is close to what you need and helping them perfect their bot. If your needed partner is nothing close to what any of forty teams have, you're strategizing wrong.

if I see a robot that fits the idea and is available, we'd be more than happy to pick them.
my point is, if I see a single robot worldwide that fits our idea, i'm eating my team shirt.

marshall 03-10-2016 01:49 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Zebra_Fact_Man (Post 1555099)
The salt is palpable.

LOL!

Quote:

Originally Posted by Zebra_Fact_Man (Post 1555099)
Honestly I think we should spend more time combining different controversial topics into SUPER Controversial topics, such as:
- If we ended bag and tag, would teams cheesecake more or less?
- Is student-built cheesecake better or worse than mentor-built cheesecake?
- Can a team competing in one World Championship cheesecake a team in a second World Championship?
- Can a mentor who mentors both the cheesecaking team and the cheesecaked team replace the student coach on the cheesecaked team?
- If you yell "Cheesecake" while transporting the cheesecaked robot through the pits, does it make the pits safer and/or the cheesecake better?
- Can teams later cheesecake the cheesecaked robot at the district championship, and again at Nationals?

#WeBrokeTheGame?

These are all very important questions. Honestly, yelling cheesecake in the pits thought might get you a flock of hungry engineers surrounding you.

Cam_Team 2619 03-10-2016 01:55 PM

Re: Cheesecake robot. How far is too far?
 
I would rather not be picked for eliminations than have to compete with another teams robot and scrap ours. I would be so saddened to say "Look, here is the blue banner that we won with another teams robot". Cheesecaking makes me sad, but this is just wrong on a new level.

Nuwanda 03-10-2016 01:55 PM

Re: Cheesecake robot. How far is too far?
 
[quote=Lil' Lavery;1555076]Nuwanda, the "situation on Curie" last year was initiated by team 900, not 1114. They approached 1114 with the idea. There's already extensive discussion of that situation in other threads. No reason to rehash that here.


I was not aware, and I apologize. I was a passive observer of the situation.

RoboChair 03-10-2016 02:04 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1555096)
Ah, thank you for the clarification.

Still never got to see those harpoons :(

Still never got to see those harpoons go against our M.A.D. cheesecake strategy. Happy we won without it, sad we didn't get to use it. If you thought our can grabbers were scary, the cheesecake tether grabbers were 30-40% faster.

That scenario will live on in my dreams. Thank you 5012 for giving me the mental image of fighting a full on millisecond war of power against teams 900 and 1114's harpoons with our tethered can grabbers and 118's bolt on can grabbers.

CJ_Elliott 03-10-2016 02:06 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by RoboChair (Post 1555113)
Still never got to see those harpoons go against our M.A.D. cheesecake strategy. Happy we won without it, sad we didn't get to use it. If you thought our can grabbers were scary, the cheesecake tether grabbers were 30-40% faster.

That scenario will live on in my dreams. Thank you 5012 for giving me the mental image of fighting a full on millisecond war of power against teams 900 and 1114's harpoons with our tethered can grabbers and 118's bolt on can grabbers.

Excuse me good sir, but why haven't I seen/heard of these?

Citrus Dad 03-10-2016 02:06 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Chief Hedgehog (Post 1554807)
However, there was a point at Lake Superior where a few teams got together in case a rookie team did not have one ready to go. Luckily for all involved - the rookie team showed up with a robot that was nearly ready to go. That being stated, the robot DID need some major work - and kudos to FRC 93 and FRC 1816 the team was ready to go at the end of the day on Thursday.

I think building an entire new robot crosses the line, and I think the new rule about requiring alliances to use robots to their full potential, which I took as no longer parking and cabling a bot, probably precludes that.

The situation you describe above is why the rules about cheesecaking need to be flexible. Helping a team improve their bot and make it competitive is an important aspect of the FRC experience. It certainly falls withing gracious professionalism.

Citrus Dad 03-10-2016 02:07 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by CJ_Elliott (Post 1555115)
Excuse me good sir, but why haven't I seen/heard of these?

Which didn't you see, 900s harpoons, or 1678's remote can grabbers. There's video on CD of both of these.

CJ_Elliott 03-10-2016 02:09 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Citrus Dad (Post 1555117)
Which didn't you see, 900s harpoons, or 1678's remote can grabbers. There's video on CD of both of these.

1678's... Im looking now but I don't think this thread is for this conversation

Citrus Dad 03-10-2016 02:17 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by GreyingJay (Post 1555025)
Let's just say "I have a friend" whose team was selected by another team for the sole purpose of (massively) cheesecaking their robot, that these plans were not discussed in advance and came as a complete surprise to the receiving team, and that the entire experience was frustrating, demoralizing and even humiliating for the team being cheesecaked.

All I'm saying is, as you have said, if all teams involved are open about their intentions and agree to it, then it's fine -- but if it isn't open and discussed prior to selection, then it's not fine at all.

To explain our team's approach, we talked to everyone of the teams that we drafted last year about their willingness to add our can grabbers. They were always able to elect a different course. And they were always involved in installing the devices.

It's important to remember that it is the alliance captain who is assembling the alliance and it is the alliance captain's discretion to choose the strategy; it is not the role of the 2nd pick robot to dictate what strategy the alliance captain should be using. If a team built a robot to pursue a specific strategy and either it is not well executed or doesn't fit with the alliance captain's chosen strategy, then that team needs to accept that they may not be selected. That's always the nature of a competitive setting; it might be a surprise to some who have been only in the school system that the real world works this way too. You will not always be rewarded solely for your efforts.

Daniel_LaFleur 03-10-2016 02:22 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by BenBernard (Post 1555085)
What bothers me about this thread is how far from "gracious professionalism" some writers seem willing to stray in their pursuit of "winning at all costs."

I never apply 'gracious professionalism' to others. I do apply it to myself and my team.

Quote:

Originally Posted by Lil' Lavery (Post 1555097)
I would rather you consider the totality of the actions, rather than just the impacts on one team. I already posted similar thoughts on this back in April, during the previous round of cheesecake debate.
https://crbewebappdev.dt.navy.mil/CR....php?id=366878

I believe I have considered the totality of this action.

I have not "cheesecaked" another's robot, nor has my robot ever been "cheesecaked". That being said, if it inspired my (or another's) team then why wouldn't I do so? and why would I be upset if it was used against me?

Remember, FIRSTs mission is to inspire, not to win on the field.

BTW, Sean your link is unreachable.

Lil' Lavery 03-10-2016 04:23 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Daniel_LaFleur (Post 1555133)
I believe I have considered the totality of this action.

I have not "cheesecaked" another's robot, nor has my robot ever been "cheesecaked". That being said, if it inspired my (or another's) team then why wouldn't I do so? and why would I be upset if it was used against me?

Remember, FIRSTs mission is to inspire, not to win on the field.

BTW, Sean your link is unreachable.

Oops, clipboard error. :o Sorry about that! This is the appropriate link.
http://www.chiefdelphi.com/forums/sh...1&postcount=87

themccannman 03-10-2016 07:40 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by CJ_Elliott (Post 1555115)
Excuse me good sir, but why haven't I seen/heard of these?

https://youtu.be/6pwuyqeMoOM

As requested. Afaik I didn't upload this footage anywhere until now, and I believe the only other person who saw this was one of the Newton inspectors who stayed around the in pit during elims/einstein.

This system was mounted entirely on a separate wood platform that would sit underneath our robot at the start of the match, but be tethered to 5012 (who would also have 118's modular grabbers mounted on their actual chassis). When the match started these would launch, our robot would hold the platform to the ground, then we would drive away during tele op leaving it attached to 5012 (and hopefully the cans they hit) while leaving our robot mobile to build stacks for the rest of the match.

Essentially, it would have boiled down to 900 and 5012 in a tug of war at the center of the field, and 1678 + 118 stacking against 1114 + 148.

Lil' Lavery 03-10-2016 09:59 PM

Re: Cheesecake robot. How far is too far?
 
Wasn't the whole point of the 1114/900 harpoons to negate any tugs of war? Simply to grab the cans with a hook that could not be removed, rendering them essentially unusable for both alliances?

JohnM 03-10-2016 10:18 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1555298)
Wasn't the whole point of the 1114/900 harpoons to negate any tugs of war? Simply to grab the cans with a hook that could not be removed, rendering them essentially unusable for both alliances?

I might be wrong, it's been a long time since seeing that contraption, but I thought their robot collapsed on itself to pull them away, maybe same goal.

marshall 03-10-2016 11:27 PM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by JohnM (Post 1555301)
I might be wrong, it's been a long time since seeing that contraption, but I thought their robot collapsed on itself to pull them away, maybe same goal.

Yes.

Quote:

Originally Posted by Lil' Lavery in that other thread
First off, the positives your listing are also teams talking about how they feel.

Secondly, the unfortunate reality is that when the source of inspiration comes from working closely with an elite team and/or deep runs in the eliminations, unfortunately that's a zero sum equation. For each team that was picked to cheesecake, a team was left off an elimination alliance. In many cases that team was a very capable team that had a competitive season, but was left off in favor of a bot that presented a better blank slate to add parts to. In other words, they were left off for a less capable team. It's pretty easy to see how being passed over for a less capable team could be disappointing. Disappointment can very well lead to a lack of inspiration.

Does the the benefit of the cheesecaking team outweigh the disappointment of the teams passed over in alliance selection? It's certainly not an easy call to make, but it's not one that should be written off as some trivial matter that can be summed up by air quotes and sarcastic titles.

Sean, at the risk of causing you to go into a rage (and I hope you don't because you seem like a nice fella)... I don't understand your analysis of the problem. Alliance selections work in mysterious ways. I have seen teams choose numbers at random from people in the audience shouting them as well as teams pick rookie teams who had barely functional robots because they wanted to share the experience.

Let us forget robot modifications for a moment and then let me ask you this. If a team were to choose a less capable alliance partner instead of a more capable team then is that inspirational? What about choosing a team not based on scouting data but based on purely the fact that you like their pants, is that ok? (Go #TeamCrazyPants) What about choosing a team because the mentors know each other really well? What about because the students know each other really well? What about because they paid you to choose them?

Now let's add robot modifications back in. What about choosing a team with a known bad drivetrain that they have to repair before eliminations and you offered to help them or lend them parts? What about choosing a team based on the fact that they are going to put a giant goal blocking sheet on their robot instead of choosing another offensive capable robot because defense suits your strategy?

Just spitballing but perhaps instead of alliance selections we could move to a process by which the serpentine draft just auto assigns teams based on qualification rankings instead of allowing a team's feelings and perception to come into play. Except that qualification rankings could be attributed to match luck. We've all seen some post-turtles turn up in the top 8 at events. So we should probably get rid of qualification matches and then we can judge robots purely on if they can accomplish the tasks that a team built them for. We don't even need events for that, we can all just sit in our labs and build robots in isolation and take videos of them completing the tasks.... Cheesecaking isn't the only slippery slope around here.

themccannman 03-11-2016 12:36 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1555298)
Wasn't the whole point of the 1114/900 harpoons to negate any tugs of war? Simply to grab the cans with a hook that could not be removed, rendering them essentially unusable for both alliances?

If you didn't bother challenging the harpoons, then they'd just pull them to their side where I believe they had the ability to release/use them. They absolutely intended to get in a tug of war, but they wanted to lose as few bots as possible to it, which was the same objective we had with that tethered ramp. If they brought out the harpoons we had to each sacrifice one bot to holding down the cans, this was our match to their strategy, mutually assured destruction.

Lil' Lavery 03-11-2016 01:33 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by marshall (Post 1555321)
Sean, at the risk of causing you to go into a rage (and I hope you don't because you seem like a nice fella)... I don't understand your analysis of the problem. Alliance selections work in mysterious ways. I have seen teams choose numbers at random from people in the audience shouting them as well as teams pick rookie teams who had barely functional robots because they wanted to share the experience.

Let us forget robot modifications for a moment and then let me ask you this. If a team were to choose a less capable alliance partner instead of a more capable team then is that inspirational? What about choosing a team not based on scouting data but based on purely the fact that you like their pants, is that ok? (Go #TeamCrazyPants) What about choosing a team because the mentors know each other really well? What about because the students know each other really well? What about because they paid you to choose them?

None of that is particularly relevant to this discussion. Nobody here is claiming that alliance selection is perfect. There are plenty of shortcomings in many facets of FRC, alliance selection included. However, claiming that because a system has other potential flaws means you should embrace a contentious aspect is not sound logic. I don't have to pick a bad option* just because there are even worse options. Strive to optimize the situation, rather than perpetuating the flaws.

*Do not interpret this to mean I'm definitely declaring that cheesecaking is a bad option. I'm just illustrating my logic.

Quote:

Originally Posted by marshall (Post 1555321)
Now let's add robot modifications back in. What about choosing a team with a known bad drivetrain that they have to repair before eliminations and you offered to help them or lend them parts? What about choosing a team based on the fact that they are going to put a giant goal blocking sheet on their robot instead of choosing another offensive capable robot because defense suits your strategy?

The drivetrain scenario is cheesecaking (albeit, offering parts solely on the condition that a team will be on your alliance may not leave the best taste in many people's mouths).
The second scenario is picking based off of strategy. I'm not advocating we take the ability to select strategically out of the hands of alliance captains. I'm not advocating we take any selection choices out of the hands of alliance captains.

I'll try to word my point slightly differently, in the hopes it is better communicated.

When people cite the inspirational value of cheesecaking, they're almost always talking about the team receiving the cheesecake. They talk about the inspirational value of winning (which has also shown up in many other threads). They talk about the inspirational value of getting to work closely with powerhouse teams as alliance partners. They talk about the inspirational value of collaborating together to improve a robot. When all parties are on the same page, that can be some real value.

However, the benefit of one team is not the total utility of the move. That one team may have been very inspired, but that doesn't mean other parties were not disillusioned by the same circumstances. The cheesecaked team was granted an opportunity, but (barring a 24 team event) another team was left out in order for that team to have that opportunity. In the case of a large and highly competitive event (such as a championship subdivision), the teams left out are highly capable teams already. Seeing a highly competitive (by any metric) team left on the sidelines in favor of a "blank slate" is something that would obviously raise questions and mixed emotions. Not simply for the teams excluded, but for parents, VIPs, sponsors, and others who may not be familiar with the esoteric practices of FRC.

I'm not arguing that cheesecake is automatically bad. I'm not arguing that cheesecake is automatically good. I'm stating that there are factors that should be considered, beyond how the teams receiving the cheesecake feel. They are not the sole parties impact by the act of cheesecaking. Like it or not, some of the peculiar things that happen in FRC might not appeal to the grandmothers in the audience.

Based on the comments in this thread and many of those preceding, you know firsthand that there are plenty of those out there who did not get the same takeaway from your partnership with 1114 as you did. Some of that is based hearsay or factual inaccuracies. You can do your best to communicate the real story, but you're never going to reach everyone. Further still, there are those who know what happened and still don't like it. These are people who are ultimately aiming for the same culture change, and their opinions of the situation do matter, even if they were not directly involved.

To me, cheesecaking is obviously a grey area.

Quote:

Originally Posted by marshall (Post 1555321)
Just spitballing but perhaps instead of alliance selections we could move to a process by which the serpentine draft just auto assigns teams based on qualification rankings instead of allowing a team's feelings and perception to come into play. Except that qualification rankings could be attributed to match luck. We've all seen some post-turtles turn up in the top 8 at events. So we should probably get rid of qualification matches and then we can judge robots purely on if they can accomplish the tasks that a team built them for. We don't even need events for that, we can all just sit in our labs and build robots in isolation and take videos of them completing the tasks.... Cheesecaking isn't the only slippery slope around here.

I have no idea what this statement is in response to. Nothing in my posts in this thread or the previous thread stated anything regarding the validity of qualification rankings. Nor were any of my positions "slippery slopes." As stated, my position was pointing out that the totality should be considered, not simply the one team that (in some cases) benefits positively. My position, as stated, was that the benefits of cheesecaking and being an alliance partner are (unfortunately) zero-sum. Neither of those are arguing that cheesecaking is a slippery slope, but rather they're challenging the logic being used here. Nor am I even claiming to have all the answers (and the post you quoted from the other thread makes that very clear).

Rangel(kf7fdb) 03-11-2016 07:50 AM

Re: Cheesecake robot. How far is too far?
 
My feelings on cheesecake is that as long you aren't stripping major fuctions off of the receiving team's robot for the cheesecake is not okay in my opinion. I know it's allowed currently and I'll respect teams who do it but I'm never going to like it. Putting can grabbers or simple blockers is one thing. But say taking a stacker off for a better stacker is too far.

marshall 03-11-2016 07:59 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by Lil' Lavery (Post 1555364)
None of that is particularly relevant to this discussion. Nobody here is claiming that alliance selection is perfect. There are plenty of shortcomings in many facets of FRC, alliance selection included. However, claiming that because a system has other potential flaws means you should embrace a contentious aspect is not sound logic. I don't have to pick a bad option* just because there are even worse options. Strive to optimize the situation, rather than perpetuating the flaws.

*Do not interpret this to mean I'm definitely declaring that cheesecaking is a bad option. I'm just illustrating my logic.


The drivetrain scenario is cheesecaking (albeit, offering parts solely on the condition that a team will be on your alliance may not leave the best taste in many people's mouths).
The second scenario is picking based off of strategy. I'm not advocating we take the ability to select strategically out of the hands of alliance captains. I'm not advocating we take any selection choices out of the hands of alliance captains.

I'll try to word my point slightly differently, in the hopes it is better communicated.

When people cite the inspirational value of cheesecaking, they're almost always talking about the team receiving the cheesecake. They talk about the inspirational value of winning (which has also shown up in many other threads). They talk about the inspirational value of getting to work closely with powerhouse teams as alliance partners. They talk about the inspirational value of collaborating together to improve a robot. When all parties are on the same page, that can be some real value.

However, the benefit of one team is not the total utility of the move. That one team may have been very inspired, but that doesn't mean other parties were not disillusioned by the same circumstances. The cheesecaked team was granted an opportunity, but (barring a 24 team event) another team was left out in order for that team to have that opportunity. In the case of a large and highly competitive event (such as a championship subdivision), the teams left out are highly capable teams already. Seeing a highly competitive (by any metric) team left on the sidelines in favor of a "blank slate" is something that would obviously raise questions and mixed emotions. Not simply for the teams excluded, but for parents, VIPs, sponsors, and others who may not be familiar with the esoteric practices of FRC.

I'm not arguing that cheesecake is automatically bad. I'm not arguing that cheesecake is automatically good. I'm stating that there are factors that should be considered, beyond how the teams receiving the cheesecake feel. They are not the sole parties impact by the act of cheesecaking. Like it or not, some of the peculiar things that happen in FRC might not appeal to the grandmothers in the audience.

Based on the comments in this thread and many of those preceding, you know firsthand that there are plenty of those out there who did not get the same takeaway from your partnership with 1114 as you did. Some of that is based hearsay or factual inaccuracies. You can do your best to communicate the real story, but you're never going to reach everyone. Further still, there are those who know what happened and still don't like it. These are people who are ultimately aiming for the same culture change, and their opinions of the situation do matter, even if they were not directly involved.

To me, cheesecaking is obviously a grey area.


I have no idea what this statement is in response to. Nothing in my posts in this thread or the previous thread stated anything regarding the validity of qualification rankings. Nor were any of my positions "slippery slopes." As stated, my position was pointing out that the totality should be considered, not simply the one team that (in some cases) benefits positively. My position, as stated, was that the benefits of cheesecaking and being an alliance partner are (unfortunately) zero-sum. Neither of those are arguing that cheesecaking is a slippery slope, but rather they're challenging the logic being used here. Nor am I even claiming to have all the answers (and the post you quoted from the other thread makes that very clear).

I appreciate the response and I think I have a better understanding of where you are coming from now.

Ultimately I don't view this as a grey area or a zero-sum situation but that is me. I think the competitive nature of FRC and the rules both enable and encourage "cheesecaking".

Taylor 03-11-2016 08:01 AM

Re: Cheesecake robot. How far is too far?
 
Quote:

Originally Posted by marshall (Post 1555413)
I think the competitive nature of FRC and the rules both enable and encourage "cheesecaking".

I believe this statement is absolutely true. I also believe this is the root of the underlying frustration for all involved.


All times are GMT -5. The time now is 02:36 AM.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi