Lesson8.md

@@ -16,15 +16,11 @@ TODO: Skriv
 
 ## **Plan**
 
-TODO: Skriv ordentligt
+We plan to work on Thursday the 28th of April and on Thursday the 5th of May. We plan to use both days in their entirety and have not set a time limit for the sessions.
 
-* begin by brainstorming ideas, using the track and provided videos and inspiration, in order to come up with a plan
+In the first session, we will discuss ideas and experiment with them, using the track and the videos provided in the lesson plan as inspiration. Based on an initial wannabe-brainstorm, we will make a plan for the experiments.
 
-* perform experiments based on brainstorming
-
-We will attempt to complete the exercises within 6 hours (based on the fact that we have not managed to complete the previous lessons in less time than that).
-
-Camilla will write the code, Emil will take notes, and Ida and Nicolai will be in charge of performing and visually documenting the experiments.
+We have decided not to make a clear division into roles, due to the rather ad hoc nature of our task. We will most likely have some sort of unspoken division of labor, but.we want it to be flexible so that everyone can take part in all tasks.
 
 ## **Brainstorming**
 
@@ -34,9 +30,7 @@ Next, we discussed how to follow the track and turn on the platforms. We discuss
 
 The discussion regarding the Y-shaped lines led to a suggestion that rather than having the robot turn on the platform, the shape might be utilized to have the robot go down the "leg" of the Y and then drive backwards up to the next platform, in the hopes of saving time. The idea is illustrated in Figure 1. There was debate as to whether or not it was doable (or practical) to do this. We might try it out when we get further into the project.
 
-[INDSÆT FIGURE 1]
-
-![image alt text](image_0.jpg)
+[TODO: Y-back.jpg]
 
 *Figure 1: TODO*
 
@@ -58,7 +52,7 @@ Finally, we briefly continued our discussion on how to perform the turns on the
 
 We decided to begin by testing the use of different sensors, with regards to following the track and making turns on the platforms. Later on, it might be interesting to focus on testing the efficiency of different ways of turning on the platforms.
 
-We ended up with the following concrete, initial plan:
+We ended up with the following initial, concrete plan:
 
 1. Run the LineFollower program from week TODO on the track to see how it performs
 
@@ -70,16 +64,18 @@ We ended up with the following concrete, initial plan:
 
 ### **Experimenting with LineFollower**
 
-…
+In order to use the LineFollower program, we rebuilt the robot so that the light sensor pointed towards the ground.
+
+[Insert rebuilt picture]
 
 ### Experimenting with the gyro sensor
 
 …
 
-### **Rebuilding the robot**
-
 ### **TODO SUBHEADING**
 
+OBS skriv om: ville nok være bedre at have behaviors og at håndtere dem så én behavior kører færdig, før en behavior med lavere prioritet kan overtage (lige nu kører vi på if-statements og er derfor nødt til at sleepe, mens vi drejer 180 grader, så den ikke bliver fucket op af at læse hvid undervejs i drejet)
+
 ## *Video 1: TODO*
 
 #### **TODO SUBSUBHEADING**
@@ -94,3 +90,7 @@ We ended up with the following concrete, initial plan:
 
 [3] Fred G. Martin, Robotic Explorations: A Hands-on Introduction to Engineering, Prentice Hall, 2001.
 
+## **Appendix: Unconstrained idea generation**
+
+TODO: Skriv om idéer fra "dum" idé-generering (kommentér på længere oppe i rapporten)
+