![]() |
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. |
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.
|
Re: Cheesecake robot. How far is too far?
Quote:
--- 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. |
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. |
Re: Cheesecake robot. How far is too far?
Quote:
Quote:
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 |
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?
|
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?
|
Re: Cheesecake robot. How far is too far?
Quote:
|
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.
|
Re: Cheesecake robot. How far is too far?
Quote:
|
Re: Cheesecake robot. How far is too far?
What if the robot frame was made of cheese cake? :cool:
|
Re: Cheesecake robot. How far is too far?
Quote:
|
Re: Cheesecake robot. How far is too far?
Quote:
|
Re: Cheesecake robot. How far is too far?
I'm confused. Is there or is there not going to be free cheesecake at Alamo?
|
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.
|
| 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