|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#166
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Perhaps an even better response from the GDC would be to step up and take responsibility for unintended consequences that they've created this year. I gave them full credit last year for what I thought was a great overall concept that got more teams involved than ever. But that also means that they should express their mea culpas rather than trying to prohibit an informal process that has been one of the most fruitful means of teams helping each other. As others have said its probably too late to save the game this year, but the GDC should take to heart an important lesson about future games.
|
|
#167
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
I mean, if you have ever heard of one team completely giving a robot to another team for use in elimination matches I'd love to see it. Because it really seems like you want this to be either 0 or 100. |
|
#168
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
That said, Mike has listed several examples of how adding cheesecake to what was otherwise a complete meal of a robot has made a team a more attractive alliance partner. Are you saying that the robots that show up a competition MUST be a complete menu with no dessert provided by other teams? That's way beyond the tradition of FRC. |
|
#169
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
Last edited by Citrus Dad : 17-03-2015 at 15:48. Reason: clarification in wording |
|
#170
|
|||
|
|||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
Quote:
Quote:
|
|
#171
|
|||
|
|||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
I disagree. The rule interpretation does not at all disallow bringing in COTS parts and a design for a device, going to a different team and suggesting they install the device. You can even help them to build/install the device. What you can't do is build it yourself and deliver it to them, already created.
|
|
#172
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
And loaning parts (and the associated expertise that often comes with it) is one of the greatest ways for teams to interact and for students to learn outside of their own team organization. |
|
#173
|
|||
|
|||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
Back in 2004, my team created a robot solely around hanging on and defending the bar. With today's teams, I have no doubt that an elite team today could design a mechanism to install on a 3rd bot that could mimic our robot's ability to move on the bar; installing this singular ability would make the least competitive team a perfect fit to the most competitive team. |
|
#174
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
1) For this year, there is a premium on surprise in the game because the outcome is likely to be determined in less than a second--in the opening auto period. Do the math and you'll see the answer. Any revelations could spoil that strategy. That's a problem particular to this year's GD. 2) After what I thought was a successful GD last year, I called for the GDC to announce in September if the game would require teams to interact on the field to increase scores. You can find my posts on this on CD. As I've said above on this thread above, I don't believe that we can rely on the "goodness of our hearts" to achieve our goals. We need carrots and sticks, mostly through GD. And beyond that the GDC should be taking actions prior to build season to encourage teams interaction. |
|
#175
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
|
|
#176
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
|
|
#177
|
|||
|
|||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Some of the responses and questions in this thread are so preachy it's a little absurd.
Having been on the receiving end of cheesecaking before, I can assure people that it is one of the most inspirational aspects of FRC that your mentors and students can witness. That first blue banner or medal sparks much more than a single trip to a championship event. Witnessing a captain be SO GOOD that they can fine tune their alliance and strategy to knock out wins is the best example of a role model team ever. Have all the cheesecake you want, I say. Last edited by Akash Rastogi : 17-03-2015 at 16:13. |
|
#178
|
|||
|
|||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
From the Q&A: "3) No, but you may certainly assist another team in building new parts for their ROBOT at the event, and we encourage that." |
|
#179
|
|||
|
|||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
How does making your alliance more competitive hurt anyone else? You skipped over my robot in favor of your extra mechanism. |
|
#180
|
||||
|
||||
|
Re: Dangerous precedent set by Q&A 461: Loaning Parts/Assemblies to other teams
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|