![]() |
Re: 2014 MN State Championship
Quote:
|
Re: 2014 MN State Championship
Quote:
My bet would be that there are more Iowa teams with practice bots than MN teams with practice bots. :yikes: |
Re: 2014 MN State Championship
Quote:
We also also modified our 2013 robot with one of our passive assisters we gave out to teams to practice with. I believe 2220 may build a practice bot and I know 3130 did for the first time this year. |
Re: 2014 MN State Championship
3883 sadly did not build a practice bot either. :(
|
Re: 2014 MN State Championship
Quote:
|
Re: 2014 MN State Championship
Quote:
Yes, the time from Duluth to State last year was a long time with only 6 hours of unbag time, but we were so excited to qualify that it didn't matter. |
Re: 2014 MN State Championship
I didn't know practice robots were such a rare thing in Minnesota! Maybe next year with the Roborio coming out teams will have 2 control systems available and practice robots will become more common. Having a practice robot advanced our team so much further than I thought possible. It allowed a lot of our younger students to troubleshoot problems that they probably wouldn't encounter on the actual robot. I'm hopeful that other teams can have that opportunity next year!
|
Re: 2014 MN State Championship
It's not a question of having multiple control systems... We have our Break Away, Rebound Rumble, Ultimate Ascent, and of course Aerial Assist all up and running. The issue we have is one of time/woman-power - We just don't have the desire and time during the build season to build two identical robots. This would probably change if we spent more time on CAD and had a shop cut the parts for us... but at least thus far our robots have been almost entirely hand-made - very little CNC.
|
Re: 2014 MN State Championship
Quote:
|
Re: 2014 MN State Championship
Quote:
|
Re: 2014 MN State Championship
Quote:
|
Re: 2014 MN State Championship
Quote:
But bagging and the build deadline really need to be ditched altogether. It's a broken system modeled off an outdated competition structure. We no longer have a logistical, real-life ship deadline to get all our machines to the same event. All other teams at our events necessarily have had the same time since kickoff to work on their machine, unless they've invented time travel. As it is, the higher resource teams will still be able to practice when their bot is in the bag, while those with less are out of luck. But all of this has been said before... I'm sort of confused about the MSHSL sponsorship too. Schools already had complete freedom to award robotics letters, compensate coaches, and the whole deal (we did). I struggle to see how MSHSL involvement is anything but limiting, introducing a plethora of rules about funding, district association, student membership, transportation, and plenty of other nonsense that teams are far better off dealing with themselves. The event operation has also been rather closed off in the past, at times charging entry fees, as well as the exhorbitant prices one might expect for any photos, merchandise, and match recordings from the event. I look forward to official district status, since this will make qualification for any state championship event make a lot more sense, and hopefully give us more freedom to run these events. |
Re: 2014 MN State Championship
Quote:
But I lose my own bet. |
Re: 2014 MN State Championship
Quote:
In short, being a part of the MSHSL has helped us expand into every high school in the state with more than 400 students, has kept teams around that would otherwise have faded, and gives us another selling point for sponsors. As far as I know, the only way 2220 has changed our operations since the MSHSL move is adding the required $50 fee (which is covered as a team scholarship as necessary). We already had most of the rules-- regarding GPA and substance abuse, etc-- before the move, so those weren't added. What changes have you had to make because of the switch? |
Re: 2014 MN State Championship
Quote:
|
| All times are GMT -5. The time now is 08:32. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi