Today I had the chance to be a referee for the Forsythe Alliance competition (Forsythe County school district) held in Cumming, GA. 40 teams showed up and each team competed in 6 runs with their scores being added together for a grand total. Competition started at roughtly 9am and ended around 4pm with a 1 hour lunch in between and small breaks. All in all, it was a blast and I got to meet a lot of great kids, supportive parents, and very committed coaches and teachers. This county has really gotten behind their kids... check out more here.
Anyway, here are my overall observations and opinions, none of which are based on scientific fact or any advanced statistical calculations - mainly just guessing and memory:
1. Mission most often attempted - Satellite
The surprising part about this mission wasn't that so many teams tried for it - it was the number of teams that tried and failed! Most teams lined it up using SET (standard eyeball trajectory) and I would estimate that 1 in 3 failed. Very surprising, isn't it? It takes 10-20 seconds of your time, so you should make sure you nail it every time.
2. Mission least often attempted - Car/Truck switch
Again, not surprising considering the work needed to get the points (two conditions must be met), but what was surprising was that the teams who did attempt it (maybe 1 out of every 10) got it to work.
3. Sensors hardly used at all
I saw a total of 30 teams come through my table, but none (ZERO) used sensors for any portion of the competion. Repeat - ZERO. With all the colors on the table, black lines, and angled lines, I thought for certain that at least 1 or 2 teams would use a Light sensor to help in some navigation... maybe the Ultrasonic to detect some of the Uranium or Corn items, but not a single one. Pre-programmed movement was the name of the game.
4. No jigs/templates
Once again, I saw no teams using any kind of template or jig device to line up their robots. A few teams did use the small colored lines that go around the inner edge of the base, but not in a way that I would consider as extremely accurate. For example, one team would line the wheels of its robot up with the left-most colored lines, but they didn't line the front of the robot up with any particular line - the result was that the movement they programmed kept missing the target (Corn) because the robot wasn't placed at the proper North-South starting position (N-S-E-W is written on the table, FYI). They had to run the same program 3 times and used trial and error to get the proper starting position. This should have been determined during testing.
5. Direction sheets
I saw 4 or 5 teams with a small "instruction manual" that they had written that had things on it such as the program name to select for a certain mission, the order they wished to run the missions, etc - one even had a "failover" selection in case one mission failed, they knew which missions NOT to run that might interfere with later missions. Very well thought out. I hadn't seen this before and was surprised. In the heat of the game, these teams were very methodical and didn't panic.
6. Wheel issues
Two teams consistently ran a mission that should have worked (oil rig) but a tire had not been checked before the competition and was either off the rim or not in alignment with the other wheel, causing the robot to rotate. Both times the teams grabbed their bot (penalty oil barrel) and ran it again, same result... grabbed the bot (another penalty) and went on to another mission. Check your tires! This is such an easy fix but can cause HUGE problems.
So many teams were stressed and reacting quickly to their robot. This caused many teams to reach and grab their robot (penalty) before it entered the base. One team grabbed the robot as it just entered the base and managed to rip off a large portion of a motor and attachment assembly - they wasted 30-40 seconds fixing it and missed out on 2 missions at least. Slow down - deep breaths... yes, time is ticking away, but hastiness caused too many mistakes for me to remember.
8. Program selection
I can't tell you how many teams wasted precious seconds trying to find the proper program for a mission or combination of missions. Cycling through the program files does take time. The best team I saw that managed this properly by having one teammate finding the program while the other handled adding/removing components. Good teamwork.
9. No RCX
30 teams - all using NXT. I didn't see a single RCX. Of the 10 teams I didn't see, there might have been... not sure.
10. False starts
A few teams were penalized because they pushed the start button before the competition countdown completed. We were very strict with this because so many teams were racing for the satellite and it had to be fair. Don't push your start button until the countdown hits zero.