At the end of my first week here in Cape Town, the robotics kits were prepared and we were ready to begin class. I forgot to write about this in my previous post but a student contract was also written up during that time.
I planned to have students read and sign this contract at the start of the first class. After this, students would be asked to build the Phase 1 robot base, which has motors to drive around but has no sensors. However, instead of building instructions, students would be given an already built model robot to re-create with their parts. I hoped this would provide them with a more engaging experience and help them gain a greater familiarity with the kit.
I was curious to get a sense for how the students might fare with this. In particular, I was curious to see what they might have trouble figuring out. Bilal and Maja agreed to give it a shot.
Next, Karl and Yves gave it a go!
I believe both groups finished in around 15 minutes, though each group remains convinced they were the faster ones! :p
On Monday, the kits were taken to school and preparations were made for the first class. The technician had still not arrived and so it was decided that we would set up a few computers ourselves. Soon we had five computers up, a data projector connected, and all the necessary software installed and configured. At the same time, the class start time was confirmed with the students' teachers. Soon students began showing up, and once everyone was there we began class. It had been a fairly hectic morning!
We went over the contract and all the students signed them. To help them start with the end in mind, they were shown the final Phase 1 robot in a quick demonstration. However, today they would just be building the robot base - off came the sensors. The mobile base (that can only drive around) was demonstrated and they were given 15 minutes to re-create the robot base from their parts.
Unfortunately, at the end of 15 minutes none of the teams had completed the task. However, combined as a class they had actually figured out a fair bit of the robot. Noting this, we encouraged the teams to discuss and share their ideas with one another. With that advice, they set back to work and some discussion between teams began. In the end, it took the rest of our class time for all the teams to finish. I learned quite a bit about the students and the dynamics of the teams that day.
On Tuesday, the students were shown the program and given time to copy it. As they typed, we walked around and checked for errors. Once they were finished, they learned how to download the program to their robots and run it. After they had some time to run their robots, I explained the program to them, line by line. To structure and solidify their understanding, we had them learn and practice specific phrases for each command.
Next, they were shown an extended driving pattern and asked to modify their programs to make their robots make the same motion. While they worked, we walked around and provided some guidance and suggestions. As each team finished, we recorded them demonstrating their robots.
Groups that finished this first extension were given a second extension to try.
On Wednesday, the students were shown the next stage of the robot that drove forward until a newly added set of touch sensors indicated it had run into an object.
Again, they were given time to first build this extension to the robot then copy a pre-written program. Once finished, they downloaded the program and tested the new robot behavior.
As I recall, I began explaining the program, but I soon realized that I was not prepared enough to properly introduce the students to the new concepts in this program, including variables, a while loop and an if statement. They had quite a bit of trouble following my descriptions of the new ideas and soon our time was up. :(
Before the next class, I remembered that I had been taught to understand and check programs by sort of executing them one line at a time as if I was the robot. This seemed to be a great way to explain the new program. Going line by line, each new concept would be captured by a new carefully chosen phrase. To help capture the idea of variables, a scratchpad could also be used to sort of represent the "robot's memory".
Thursday's class started with a new explanation of the program, this time going line by line and using a part of the board as a scratchpad for the variables.
Once finished, it seemed the students had gained a much better understanding. :) Thus, they were given an extension. Now, when the robot hit the box it should not immediately stop, but rather align itself and then stop. This is actually one of the behaviors of the final Phase 1 robot.
Unfortunately, the students had quite a bit of trouble figuring out how to modify the program. Various parts of the program structure seemed to be confusing them. We tried to give a few hints to head them towards the final Phase 1 robot program, but it did not really work out. More thought would need to go into this step.
Looking at Thursday's photos, you may have noticed that the lights were off in the room. Furthermore, we were using laptops and a white board in the room. This is because the school was without electric power due to some scheduled maintenance work. Thanks to Karl for allowing us to borrow his laptop!
Friday's timetable is different to accomodate some of the Muslim students. As a result, the robotics class is only Monday through Thursday.
Throughout the week, we also spent several mornings setting up the computers ourselves to save the school some money. The technician would come later to set up the lab server and configure the new lab. At the end of the week, Zhaun and I had unpacked almost forty desktops, put each in its proper place, and set a fair number of them up. Thanks to Onno for helping us out one day!
That week I also decided to dress a bit nicer for class and so needed a new dress shirt and tie. In Wynberg, I found a nice gray shirt and tie for around 120 Rand, which is less than $20! On Tuesday, we also went out to Tango's as a house for Robert's last week in Cape Town.
Anyway, the week had been a bit busy and I had learned quite a bit. I was excited to get started with the students and was looking forward to finishing up the touch sensor. :D
I planned to have students read and sign this contract at the start of the first class. After this, students would be asked to build the Phase 1 robot base, which has motors to drive around but has no sensors. However, instead of building instructions, students would be given an already built model robot to re-create with their parts. I hoped this would provide them with a more engaging experience and help them gain a greater familiarity with the kit.
I was curious to get a sense for how the students might fare with this. In particular, I was curious to see what they might have trouble figuring out. Bilal and Maja agreed to give it a shot.
Next, Karl and Yves gave it a go!
I believe both groups finished in around 15 minutes, though each group remains convinced they were the faster ones! :p
On Monday, the kits were taken to school and preparations were made for the first class. The technician had still not arrived and so it was decided that we would set up a few computers ourselves. Soon we had five computers up, a data projector connected, and all the necessary software installed and configured. At the same time, the class start time was confirmed with the students' teachers. Soon students began showing up, and once everyone was there we began class. It had been a fairly hectic morning!
We went over the contract and all the students signed them. To help them start with the end in mind, they were shown the final Phase 1 robot in a quick demonstration. However, today they would just be building the robot base - off came the sensors. The mobile base (that can only drive around) was demonstrated and they were given 15 minutes to re-create the robot base from their parts.
Unfortunately, at the end of 15 minutes none of the teams had completed the task. However, combined as a class they had actually figured out a fair bit of the robot. Noting this, we encouraged the teams to discuss and share their ideas with one another. With that advice, they set back to work and some discussion between teams began. In the end, it took the rest of our class time for all the teams to finish. I learned quite a bit about the students and the dynamics of the teams that day.
On Tuesday, the students were shown the program and given time to copy it. As they typed, we walked around and checked for errors. Once they were finished, they learned how to download the program to their robots and run it. After they had some time to run their robots, I explained the program to them, line by line. To structure and solidify their understanding, we had them learn and practice specific phrases for each command.
Next, they were shown an extended driving pattern and asked to modify their programs to make their robots make the same motion. While they worked, we walked around and provided some guidance and suggestions. As each team finished, we recorded them demonstrating their robots.
Groups that finished this first extension were given a second extension to try.
On Wednesday, the students were shown the next stage of the robot that drove forward until a newly added set of touch sensors indicated it had run into an object.
Again, they were given time to first build this extension to the robot then copy a pre-written program. Once finished, they downloaded the program and tested the new robot behavior.
As I recall, I began explaining the program, but I soon realized that I was not prepared enough to properly introduce the students to the new concepts in this program, including variables, a while loop and an if statement. They had quite a bit of trouble following my descriptions of the new ideas and soon our time was up. :(
Before the next class, I remembered that I had been taught to understand and check programs by sort of executing them one line at a time as if I was the robot. This seemed to be a great way to explain the new program. Going line by line, each new concept would be captured by a new carefully chosen phrase. To help capture the idea of variables, a scratchpad could also be used to sort of represent the "robot's memory".
Thursday's class started with a new explanation of the program, this time going line by line and using a part of the board as a scratchpad for the variables.
Once finished, it seemed the students had gained a much better understanding. :) Thus, they were given an extension. Now, when the robot hit the box it should not immediately stop, but rather align itself and then stop. This is actually one of the behaviors of the final Phase 1 robot.
Unfortunately, the students had quite a bit of trouble figuring out how to modify the program. Various parts of the program structure seemed to be confusing them. We tried to give a few hints to head them towards the final Phase 1 robot program, but it did not really work out. More thought would need to go into this step.
Looking at Thursday's photos, you may have noticed that the lights were off in the room. Furthermore, we were using laptops and a white board in the room. This is because the school was without electric power due to some scheduled maintenance work. Thanks to Karl for allowing us to borrow his laptop!
Friday's timetable is different to accomodate some of the Muslim students. As a result, the robotics class is only Monday through Thursday.
Throughout the week, we also spent several mornings setting up the computers ourselves to save the school some money. The technician would come later to set up the lab server and configure the new lab. At the end of the week, Zhaun and I had unpacked almost forty desktops, put each in its proper place, and set a fair number of them up. Thanks to Onno for helping us out one day!
That week I also decided to dress a bit nicer for class and so needed a new dress shirt and tie. In Wynberg, I found a nice gray shirt and tie for around 120 Rand, which is less than $20! On Tuesday, we also went out to Tango's as a house for Robert's last week in Cape Town.
Anyway, the week had been a bit busy and I had learned quite a bit. I was excited to get started with the students and was looking forward to finishing up the touch sensor. :D
No comments:
Post a Comment