Quote:
Originally Posted by dibblec
I would like to see FIRST consider the following:
1) Have two or three drive trains that are approved and can be used, period. I have been impressed with the new one from AndyMark this year. Not that I have a lot to compare to from the ones in the past, but our team feels like it gives us a better starting point to be competitive.
4) Add one week to the stop build day or at least for rookie, 2nd and maybe 3rd year teams. This would just help with programming. How many teams startup and really understand things like visioning. There are teams on the forums just asking some of the basics on how to use Autonomous. Yet, you see samples of very sophisticated code for visioning from years of experience which is great, but how does not always help a young team to get started in programming. The answers on this forum a sometimes vague and answered by people with a lot of experience in a way that a new team should just understand what they mean. Having an extra week could allow more experience teams that stop building assist new teams just get through their code. That seems to be in the spirit of FIRST. Helping others get better. Understandably so, that is hard when we are all in a 6 week crunch time.
|
I don't see how either of these two make sense.
For 1, what do you gain from restricting people to specific drivetrains? What if a team wants to build a swerve drive, or a jump/H/octocanum drive? Our team likes to use 8020 and build a custom chassis, since it is so much easier to prototype and play around with frame geometry on 8020. If you want to use the kitbot (which is certainly a good drivetrain), then you are welcome to. Don't force it down the throats of teams that want to go the extra step and come up with something innovative.
For number 4, you could argue this would improve a lot of things, but it'll also be unfair for a lot of teams. There are teams that have been vets of FIRST for a long time that can't do what some rookie and 2nd year teams are capable of now. Allowing an extension for teams that have been in existence for only 3 years, regardless of their state of readiness, but ignoring those vet teams that still need help won't help.
I think this thread has derailed enough, and we should bring it back to the topic of discussing stop build day and the bagging rule.