|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
Last edited by marshall : 21-10-2016 at 15:43. |
|
#2
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Yep. I get it that many teams build two robots to get around the time limit. I get it that many will show up with 29.9 lbs. of improvements at every competition.
Did you take more than 10 seconds to actually consider my points and perspective? |
|
#3
|
||||
|
||||
|
Re: paper: Stop the Stop Build
I have in fact. I have taken over ten years to consider my own perspective on the inevitable death of stop build day. I think Jim's paper does a great job of explaining all of the ways the system is currently broken and the compromised solution he lays out is more than acceptable to me. Your response did not lay out a structured argument to refute his claims but yet runs contrary to them, which is why I asked the question that I did. It wasn't meant as an insult though I see now how it could have been misconstrued as one.
|
|
#4
|
|||
|
|||
|
Re: paper: Stop the Stop Build
Quote:
All eliminating stop build does is provide teams who didn't previously have the means to keep working up until the last minute possible the means to do so. This will not require anyone work more than they want to, but instead gives them the *choice* to do so, a choice many would not have otherwise. The top teams are still going to be the top teams. It may move some lower end teams up, but at the end of the day a non-top team isn't going to fare any worse on their own than they would have with stop build. This does not make it worse for teams who don't want to work more, it only opens up the opportunity to do so to teams who didn't have that opportunity before. And before someone says "if we don't work more we'll get left behind while everyone else gets better", congrats, that's part of life. This is a competition. If you don't care about being competitive, great. Good for you. You don't need to work any longer than you'd like to. If your argument is that you won't have the means to work longer, but you still wanna be competitive, join FTC. Or VEX. Or any other competition. FRC isn't the end-all be-all best robotics program for everyone, but it is a program with a lot of potential for those who are willing and able to put in the work. The program shouldn't be limited just because of a few who would benefit more by being in another program. |
|
#5
|
||||
|
||||
|
Re: paper: Stop the Stop Build
I beg to disagree.
FRC isn't an on-the-field competition. FRC *includes* an on-the-field competition. Last edited by gblake : 21-10-2016 at 19:48. |
|
#6
|
|||
|
|||
|
Re: paper: Stop the Stop Build
Quote:
*FRC* is a competition. *FIRST* includes a competition (FRC). There may be methods to pursue the FIRST mission that do not include a competition. However, the method FRC chose does include a competition. It's in the name. |
|
#7
|
||||
|
||||
|
Re: paper: Stop the Stop Build
I know what you're trying to say, but I think this is a bit pedantic and derailing. We are discussing a change to the rules of the robotics competition, so we are of course focused on the impact this competition rules change has to the robotics competition.
|
|
#8
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
The post I replied to appeared to tell someone introducing a bit of the bigger picture, that anything less than single-mindedly dedicating a team to winning FRC's competition is a mistake. I think we can be confident FIRST HQ has an eye on the bigger picture that includes FIRST's primary mission, *and* on the health of the important competition that supports that primary mission. Why not ensure both are emphasized in this conversation? I'm guessing that FIRST HQ and CD will find the result more persuasive than they would otherwise. If I was derailing, please give me credit for trying to derail us onto a set of tracks that takes us to our destination, not past it. Blake Last edited by gblake : 22-10-2016 at 01:51. |
|
#9
|
|||
|
|||
|
Re: paper: Stop the Stop Build
Quote:
![]() |
|
#10
|
|||
|
|||
|
Re: paper: Stop the Stop Build
I think the point over mentor burnout is a big point that Jim's paper kind of ignored but semi-addressed with the 8 hour open bag time per week; which is something I think I'd support.
The one thing I was unclear on is what is the purpose behind FIRST considering this? Is it because the stop build is almost artificial anyway because of how many teams have a second robot and/or use a ton of time with the weight withholding? If that's the driving force behind it then I think Jim's solution is pretty solid. I feel like if it's to increase competitiveness of the events then it's probably not the right solution. I think the solution needs to be two-fold. First, somehow as a community we need to find a solution to improve competitiveness of the lower to mid-tier teams that struggle (maybe a strong eMentoring program or something). Then, I think FRC needs to look at historical performance of teams and maybe put restrictions on teams that win 80-90% of their regionals/districts (maybe only allow a 100lb robot and limit motors, sensors or envelop size compared to the rest of the teams). But, I don't see the point penalizing the historically successful teams without doing something to improve the struggling teams; because that'll just lower the overall quality of the events. |
|
#11
|
||||
|
||||
|
Re: paper: Stop the Stop Build
Quote:
Quote:
![]() |
|
#12
|
|||||
|
|||||
|
Re: paper: Stop the Stop Build
Quote:
--More often over shorter time, or less often over longer time? (Assumes the same number of meetings, or very close.) --More meetings over more time, or same meetings over same time? (Assumes that teams maintain current schedule and simply move crunch time later.) I would suspect that the disconnect is this: Teams that want to keep the bag are likely to assume that the SECOND part is the key. Teams that want to ditch the bag are likely to assume the FIRST part is the key. Basically, number of meetings vs time available to have 'em. Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|