Lab 11

Lab 11 better known as–judgement day. The team came to this lab 30 minutes early in order to try to complete the code and leave time to also fix bugs during the lab. Final testing was done by choice giving team’s the ability to test and tweak with each team’s  AEV and respectable codes. After, team A had tested and tested and tested the code seemed to be fully functional giving the AEV the tools needed to complete the mission with faults. Once, the team got a loosely defined as “perfect” run, then a scorer was requested. With palms sweating and hearts beating fast, the team placed the AEV on the track and turned on the power on–that was the first mistake. The run got half way completed, stopping way short of the gate sensor on its return journey for no reason at all. This made the team suspicious so the engineers tested the AEV again without changing anything about the code and the AEV again had a perfect run. Then, the team requested a scorer again and this time only had one place to mark off and that was for incidental touching by one of the members. This validated one very scary truth about this AEV project, and that is the amount of variation from run to run leads to so many inconsistencies. This is why the runs themselves are not graded on performance but on completion.

Leave a Reply

Your email address will not be published. Required fields are marked *