When you get to technical judging, there will be a Game table set up just like at the performance runs. There are generally two judges: one to judge your robot design, and one to judge your programs. Your team will be asked to run their missions and describe what is happening with their robot. They will also be asked to describe their robot and how they came up with the design. About half way through, the programming judge will ask the programmers of the group to go with him to show him the team’s programs. The robot design judge will continue with the rest of the group.
Some of the questions the technical judges may ask are:
- How did you come up with the design of your robot?
- What’s cool about your robot design?
- Which sensors did you use and why?
- How did you divide up the missions?
- What did you try that didn’t work?
- What did you change to make it work?
- What were some of the challenges you faced and how did you overcome them?
The thing to remember about technical judging is to talk about the sensors your team uses and what sets their robot apart from the others.
No matter how you rehearse technical judging, the technical judges will always throw a wrench into your process. We have tried to be organized and go in a somewhat logical progression, but the judges always end up directing the team off on a tangent.
The important thing is that your team remembers specific points about their program(s) and robot and that they make sure they communicate them.