Lab3.markdown

@@ -235,6 +235,10 @@
 > ![G3](http://gitlab.au.dk/uploads/group-22/lego/8b5ba5b544/G3.png)
 > ##### Fig. 9: Graph showing the profile of a single clap of sound level over time.
 >
+> ![G4](http://gitlab.au.dk/uploads/group-22/lego/5be9aa34ac/G4.png)
+> ##### Fig. 10: Graph showing the results from the ClapCar program. When the curve matches the algorithm of the
+> inner loop the robot beeps twice. Here the curve matches the algorithm three time seen by the three spikes.
+>
 > We noticed that it is possible to trick the robot into thinking it hears a clap by shouting a short word to the sound sensor. This is due to the fact that the robot only distinguishes between volume and duration of a sound meaning that different sounds can actually result in the same sound profile. The graph below [fig. ??] shows a series of claps showing three distinct peaks. Each peak is a registered clap. The smaller peaks will not result in a beep as the sound profile does not match that of a clap. 
 >
 > ---
@@ -244,11 +248,11 @@
 > To make a party finder robot which detects and drives in the direction of the loudest sound.
 >
 > #### Plan
-> We intended to mount two sound sensors on the robot [fig. ??] and use the readings from these sensors to always
+> We intended to mount two sound sensors on the robot (see fig. 11) and use the readings from these sensors to always
 > drive towards the location with the loudest sound level.
 >
 > ![P2](http://gitlab.au.dk/uploads/group-22/lego/ed19ec2872/P2.png)
-> ##### Fig. 10: Picture showing how we mounted the two sound sensors on the NXT robot.
+> ##### Fig. 11: Picture showing how we mounted the two sound sensors on the NXT robot.
 >
 > The two sound sensors were mounted on the opposite sides of the robot facing away from each other at a 90 degree
 > angle (perpendicular to each other), as can be seen in fig. ??.