I like auto mode, but it was a big reason for our two losses, which came when we decided we wanted a better auto mode and the changes we made didnt exactly work, we got up to the ramp first, but our robot went in reverse too fast and no boxes were knocked over... those boxes eventually got knocked on the other side, and that was the difference we lost by.... so, auto mode is a very BIG factor this year, which is cool b/c ours worked most of the time, but i think it will be in the competition next year, and many years to come, until they come up w/ something more complex than it

I really like auton mode, but it sure makes the programming a lot harder. Especially when you're on a team like mine, where the robot is finished either a few hours before shipping or at the competition itself. I had to program the entire autonomous mode in the pitts, having no idea what it would do (it made the robot flip itself on the bar). Other than that though, it really adds a lot to the competition.

With regards to programming, I only finally figured out a few days ago while fiddling around how to drive the robot and make it repeat everything exactly in auton mode. We sure could have used this sooner.

The main problem with auto mode this year is that, well, it was its first year. Now that teams have some experience with it, it will definately be better next year for all teams. We only perfected it during the Chesapeke Regional, and realized from the beginning that because we were so new to it dead reckoning was the only way to make it work, because it was so simple. No-one had enough experience with autonomous mode this year to use sensors a great deal, and the folly of most teams was that they kept at it. One of our programmers is playing with autonomous mode during the summer to figure out how to make more complex programs work.

I like the auton mode- even though in the end it turned out to be a factor against us- and for that matter anyone else who had a white tape auton mode. I can't belive that they used the wrong tape(/censors?)(It didn't work right with that tape...). Our robot was good at folowing the tape up the ramp and fast as well. Oh well we have new programs that are being worked out. Preperation for the future! LoL. To bad we wont get to test any in another competition this year.

Good luck in your regionals and Nats. Sorry we can't join you.

I agree that auton mode shouldn't get much longer than 15 seconds. Any more time and it'll be too difficult to plan a good auton activity for the bot. With 15 seconds, you can pretty much accomplish one thing and that's it.

Yeah it is a good thing to have i mean on an educational level cause you have know how it works before you play.

I think autonomous really adds to the game. It's been pretty much distinguishing how well a team does, and gives the programmers something to do. I'm all for keeping it next year, and it really tells you how good a team is at the game as a whole, and not just mechanically at building a robot. Having good autonomous is probably the most important thing this year, and hope they don't take it away for next year.

I've been thinking about it, and I believe there definitely will be an autonomous mode next year. If you remember, on the game submission thing it asked what sensors you would like the game to highlight.

Hehe, I really will have a job again next year!

I definitely liked the 15 seconds of autonomous. It made the game a lot more interesting. A cool, new twist for next year might be to put the 15 seconds at the end of the match... that would definitely be challenging!

that would def. make sensors important

KEEP IT.

I'd love to see it only run for ~10 seconds though.

The problem I find with the last 10 seconds for an autonomous mode is that the game would lack a "home zone" which has been there forawhile now. I like the idea of a homezone, be it where you started or even on top of a giant ramp. It highlights the ability for a team to push, take punishment, and simply move well with a drivetrain.
Though if the autonomous mode is only 10 seconds, this I wouldn't mind either. Just no more than 15!!!

As for new sensors, what do YOU think we should have? We have optical and rotation sensors, a gyroscope... What new sensors can the FIRST kit provide that may be useful for a new autonmous mode?

on the topic of a homezone, why can you do that in auto? that way you would have some sort of idea of what to program, instead of just random driving around like it would be w/o a homezone. But it would def. be foolish to get rid of the idea... unless they find something cooler of course

Perhaps it wouldn't be so hard if the homezone was covered in reflective tape. It'd FINALLY catch on!

Get Auton before it gets you...
 

I vote against autonomous mode.

Basically, it is as a killer on 2 levels: It is a huge increase in time and energy (and pressure) for the coders. It all but requires teams to do dangerous things in and around the pits.

It IS cool, but it is also such a huge advantage if you can pull it off that teams that want to be in the hunt push themselves that much harder to make it happen. For our team that resulted in us doing what we have NEVER done before: complete a practice robot. It has also ment 4 or 5 times the effrot from the coding team to get the best our of the auton code. Encouraging this level of extra effort is not in the long-term best interest of FIRST.

As to safety, I have never seen as many near misses in the pits as I have this year. My own team is no exception, we try to be as safe as we can but we are not always successful -- my apologies to the HOT team and the Killer Bees, our pit neighbors in Ypsilanti :-0 It is down-right dangerous out there due to people trying out the latest changes/tweaks to their autonomous code.

If FIRST keeps autonomous next year, I believe they will have to address these two issues: burning out coders and hurting someone in and around the pits.

JOe J.