|
Re: Why do we bother bagging?
Quote:
Originally Posted by Monochron
I have two main points here to make.
1. I like the Stop Build method for one reason: it sets up a window in which you work on your robot. It enforces a challenging time limit to prevent teams with a huge amount of resources from designing and constructing for months. It helps level the playing field by imposing an even degree of difficulty.
2. Allowing teams to build and practice with a second robot breaks that level playing field. Like you say, teams that have the resources to do it, more or less, do not have that 6 week limit placed on them. Sure, they must do their building on a proxy bot, but the action of physical construction is where you iron out your unforseen problems.
The way I always saw Ship Day or Bag 'n Tag days was a way to ensure every team got the same amount of time to work (and as it has been posted before, that was the original intent of the rule). Now that teams continue work/training/debugging on a proxy bot they are breaking that limit of 6 weeks. The 6 week limit is a good thing, it is the same as having all Regionals on the same day and allowing teams to build up until that day.
FIRST shouldn't be removing the limit, they should be enforcing it strictly by disallowing work on a proxy bot. Basically, disallowing proxy bots. How they enforce that . . . I'm not sure. But the level playing field time limit has to be preserved.
|
Brian,
I can see your point........although not saying I agree/disagree with it.
Our program has the resources to build 2,3,4 or even 5 robots if we really wanted to. But we dont have the manpower, passion, or time to make even 1 practice bot at this time.
It also doesnt bother me that other teams do and have a lot more practice/refinement time than us. My body needs a break, my family needs me at home more often, and my day job needs attention after a long 6 weeks and all the preparations leading up to it.
I think the spirit of the build season is as you have described to create an even playing field with respect to time.
But the reality is, over the years, more and more teams have access to better equipment, better design support/capabilities, and more experience to do a second robot while competing in more and more events.
I think FIRST has to figure out how the rules should evolve, if any to either stop it, or support the reality of the changes that hundreds of teams now employ.
__________________
2016 Hawaii Regional #1 seed, IDesign, Safety Award
2016 NY Tech Valley Regional Champions, #1 seed, Innovation in Controls Award
2016 Lake Superior Regional Champions, #1 seed, Quality Award, Dean's List
2015 FRC Worlds-Carver Division Champions
2015 Hawaii Regional Champions, #1 seed.
2015 Australia Regional Champions, #2 seed, Engineering Excellence Award
2015 Inland Empire Regional Champions, #1 seed, Industrial Design Award
2014 OZARK Mountain Brawl Champions, #1 seed.
2014 Hawaii Regional Champions, #1 seed, UL Safety Award
2014 Dallas Regional Champions, #1 seed, Engineering Excellence Award
2014 Northern Lights Regional Champions, #1 seed, Entrepreneurship Award
2013 Championship Dean's List Winner
2013 Utah Regional Champion, #1 seed, KP&B Award, Deans List
2013 Boilermaker Regional Champion, #1 seed, Motorola Quality Award
2012 Lone Star Regional Champion, #1 seed, Motorola Quality Award
2012 Hawaii Regional Champions #1 seed, Motorola Quality Award
Last edited by waialua359 : 20-02-2014 at 17:21.
|