Kettering Results from Week 2

[EricLeifermann]

Originally Posted by MrMatt

As a mentor from 2619, I would like to thank teams 245 and 70 for a great showing at finals. Hope to see both of you at State!

Congrats Matt, from an OLD friend. I was cheering you guys on the whole time.

[Not2B]

Well, that was fun. Glad 33 and 548 joined us. Thanks!

Here's my views on the good, the bad, and the ugly.

The good:
- Nice, small regional feel.
- Much smoother than I expected, the volunteers did a GREAT job.
- The volunteers were all so NICE too.
- The second screen in the cafe area was nice to have.
- Good judging. Good judge selection.

The bad (or at least, could be improved):
- Lack of seating. That was inconvenient.
- Lack of power. That was frustrating.
- The sound level was actually painful. We couldn't even talk to the person next to us.

The ugly:
- The number of teams that had trouble getting to the field. I could care less about how that affected the game. (Trust me, I really don't). But I could feel the frustration from the teams. I wish they had more time to prep. Maybe it's just growing pains.
- My team might noogie me for this, shaking more gray hairs loose (hence the ugly), but I like hearing from guest speakers. Please don't get rid of too many.
- You should SEE some of the pictures I got of my team when they were not looking. Talk about ugly. heh heh heh.

[IKE]

[quote=Not2B;833365]Well, that was fun. Glad 33 and 548 joined us.

The ugly:
- The number of teams that had trouble getting to the field. I could care less about how that affected the game. (Trust me, I really don't). But I could feel the frustration from the teams. I wish they had more time to prep. Maybe it's just growing pains.
QUOTE]

This is the downside of the 12 match/40 team format. There is not a lot of prep and fix-it time. All that aside, believe it or not, there were fewer No shows than at Midwest which had significantly longer times between matches.

This format reinforces the need for a robust robot and prepared pit crew.

[Tom Line]

It also reinforces the need for Labview to improve their build times. 5+ minutes to build means that teams utilizing labview are taking a big gamble trying to make a code change between rounds - one error compiling and you're in trouble.

C++ teams? Not so much.

[joeweber]

I agree with the slow down load time. Our programer had the program ready to down load, but it sure seemed to take for ever when they are calling you for second call and it is still loading!!!! Evrybodys saying hurry up but all you can do is watch the line get longer.

[Clinton Bolinger]

Here are the results:

Kettering - http://www.firstinmichigan.org/stati...ults_Week_2_KU

Overall - http://www.firstinmichigan.org/stati...esults_Overall

Looks like 2771 is going to States Congrats, you guys are an amazing rookie team.

Thanks to 818 and 1 for selecting us to be on your alliance it was great. Juggernauts your shooter was awesome, dropping both Super Cells in the final seconds against 1504, 910, and 1025.

Congrats to 245, 70, and 2619. It seems like 2619 always gets the best of us at Kettering (Rookie Regional 2008 and Kettering District 2009).

Team 33 congratulations on winning chairmans you are truly an inspiration to us younger teams.

-Oris-

[JNelson]

Looks like 2771 is going to States Congrats, you guys are an amazing rookie team.

Thanks to 818 and 1 for selecting us to be on your alliance it was great. Juggernauts your shooter was awesome, dropping both Super Cells in the final seconds against 1504, 910, and 1025.

Congrats to 245, 70, and 2619. It seems like 2619 always gets the best of us at Kettering (Rookie Regional 2008 and Kettering District 2009).

Team 33 congratulations on winning chairmans you are truly an inspiration to us younger teams.

-Oris-[/quote]


Thanks Oris. We certainly are enjoying the ride, and learning a ton from other teams

[Raumiester2010]

Originally Posted by IKE

This format reinforces the need for a robust robot and prepared pit crew.

ill agree with you on that one... we got lucky and our robot still hasn't suffered any major breakdowns (knock on wood) and we missed all the practice rounds because we did another one of our famous "change our strategy/robot on the first day of competition" like at Atlanta where we did a huge re-mod last year which, like in this instance, made us WAY more competitive than we would have.

oh ya, if anyone was wondering why we didn't move on the first match of quarter- finals, bad batts SUCK. we checked it with the volt meter and it read out 13 volts, when it went under a load it dropped to 9. couldn't move at all. i feel kinda bad because a lot of us thought it was the programmer's fault, thought it was bad code.

so, heads up to other teams about the tricky batteries. the only way we could check it was to run it for a second in the robot before the matches.
maybe you guys can come up with a better solution but thought i would give everyone a warning.

Good luck to everyone in the coming weeks and congrats to team 33 on chairmans

[Not2B]

Originally Posted by IKE

This format reinforces the need for a robust robot and prepared pit crew.

I wholeheartedly agree. I think that was a wakeup call for lots of teams.

It never occurred to me that the main auto mode for 90% of the teams would be FULL STEAM AHEAD into walls, robots, metal bars, etc... Glad we seem to be holding up without issues.

Hey - other Michigan teams yet to compete! Get ready for fast turn matches and robot beatings.