After the high emotions at the last meeting, I was prepared for this meeting to be a challenge.
Well, kids will always surprise you. They all walked in as if nothing untoward had happened at the last meeting. They quickly reached agreement on their robot base, and there are no hard feelings at all. Actually, they told me they had reached this agreement at the end of the last meeting - somehow I must have missed it during all the shouting and name-calling!
They have developed their own design, a basic chassis with two drive wheels and a slider. It should travel reasonably straight, turn easily, and can drive forward or backward with places for attachments on both front and back.
The next step is to start working on the missions, which were released just a few days ago. As we predicted, there are several missions which require delivering items, as opposed to last year where there were several retrievables. First I showed the team a video from the High Tech Kids website which showed several innovative approaches to solving the retrievables missions from Ocean Odyssey (http://www.hightechkids.org/?2-1-1054#FLL_Strategy_Videos). Since all our team members had competed in Ocean Odyssey, they were able to appreciate the variety of solutions and it really got them in the right mood for brainstorming.
Next, we reviewed the NanoQuest missions. They wanted to look at the Cable Tester (truck) and the Stuck Nanotip first, so they broke into pairs with the goal of brainstorming at least five approaches to each mission.
They still had trouble working together, however. Being all in one room, they managed to get in each others' way constantly, and spent a lot of time listening in on each others' discussions. It took considerable persuasion to get them on track again. How would they have managed if there were more kids on the team?
By the end of the meeting, they had several ideas for most missions and at least two for every mission except the Individual Atoms.
Thursday, September 28, 2006
Week 2: September 15
Since other extra-curricular activities have not yet started for the team members, we decided we could take a full day for this meeting. The project was scheduled for the morning, with a generous lunch/soccer break followed by an afternoon on robotics.
The research project was first on the agenda. The kids had used the comments feature of our private blog to brainstorm ideas for the project topic. Surprisingly, they were able to reach agreement on a topic and begin to flesh it out. They have decided to investigate ways of utilizing nanotechnology to capture electricity from lightning. (They are nothing if not ambitious!) Since the challenge was officially released during our meeting time, we were able to check that this topic can fit within the project challenge for this year.
So the kids each presented a little bit from the reading they had done since the last meeting, and they identified several areas where they want to find out more, including nanocapacitors, nanosponges, nanocatalysts, and solar paint. Again, everyone chose an area to research before the next meeting.
After their soccer/lunch break, we reconvened to work with the robots. Since the team still had not decided on a base robot, that was the main focus of discussion. The kids were totally unable to reach agreement, and worse, they were incapable of discussing the pros and cons with any logic. Language got emotional, tempers flared, and the kids took turns stomping off.
After some nasty name-calling erupted, Chaz and I had to call the group to attention and remind them of some basic team rules like respect and gracious professionalism. They weren't really ready to settle down, but some grudging compromises were made.
The research project was first on the agenda. The kids had used the comments feature of our private blog to brainstorm ideas for the project topic. Surprisingly, they were able to reach agreement on a topic and begin to flesh it out. They have decided to investigate ways of utilizing nanotechnology to capture electricity from lightning. (They are nothing if not ambitious!) Since the challenge was officially released during our meeting time, we were able to check that this topic can fit within the project challenge for this year.
So the kids each presented a little bit from the reading they had done since the last meeting, and they identified several areas where they want to find out more, including nanocapacitors, nanosponges, nanocatalysts, and solar paint. Again, everyone chose an area to research before the next meeting.
After their soccer/lunch break, we reconvened to work with the robots. Since the team still had not decided on a base robot, that was the main focus of discussion. The kids were totally unable to reach agreement, and worse, they were incapable of discussing the pros and cons with any logic. Language got emotional, tempers flared, and the kids took turns stomping off.
After some nasty name-calling erupted, Chaz and I had to call the group to attention and remind them of some basic team rules like respect and gracious professionalism. They weren't really ready to settle down, but some grudging compromises were made.
Week 2: September 12
We split our time between the project and the robotics at this meeting, beginning with the project. Each team member presented the information they had researched on the topics chosen at the Sept 6th meeting. It's clear this is a large topic and needs to be narrowed down so their research can be focussed on an area relevant to the final project, otherwise the team will spend a lot of research time on topics that are later discarded. Last year the team found that very frustrating, so we are attempting to reach agreement on a topic much earlier this season.
Several topics emerge as interesting possibilities: carbon nanotubes and energy solutions (creating or storing) are at the top of the list. The team agreed to use our new private blog as a way to communicate their ideas to each other until the next meeting. They did agree to abide by the standard brainstorming rules - keeping an open mind and not making negative remarks about other suggestions. We'll see how it works.
In the robotics, they showed the robots they had built at home. There were strong feelings about the merits and problems of each robot, and it seemed difficult for the kids to focus on individual design elements. Comments like "my robot's better than yours" abounded. The meeting ended without any agreement, so the discussion of the robot base will continue at the next meeting.
Several topics emerge as interesting possibilities: carbon nanotubes and energy solutions (creating or storing) are at the top of the list. The team agreed to use our new private blog as a way to communicate their ideas to each other until the next meeting. They did agree to abide by the standard brainstorming rules - keeping an open mind and not making negative remarks about other suggestions. We'll see how it works.
In the robotics, they showed the robots they had built at home. There were strong feelings about the merits and problems of each robot, and it seemed difficult for the kids to focus on individual design elements. Comments like "my robot's better than yours" abounded. The meeting ended without any agreement, so the discussion of the robot base will continue at the next meeting.
Sunday, September 10, 2006
Week 1: September 8, First Robotics Meeting
Up until this point, we were still not sure if others would be joining our team. We had advertised for girls to join us, but couldn't find anyone who was interested and available. So we have only the four boys that are returning from last year. That means these four kids will have been together for two years (they were four of our original six from last year).
We have two reservations about restricting the team in this way: these four won't be challenged by new approaches and new ideas; and it may make it even harder to rejuvenate the team with "fresh blood" next year. Nevertheless, the decision was taken and we are all content with the situation for this year.
Since the team membership is now decided, this was the first meeting where we really got down to business with the robot. All kids have had a chance to play with it and experiment, so we set down to the task of considering how this robot kit can solve this year's challenges. The kids came up with some ideas for what would be important in the robot base, and these were recorded. Lots of ideas were thrown out for discussion: treads vs. wheels, how many wheels, where the driving wheels should be, size of the robot, centre of gravity, ways of attaching sensors, etc.
The team left the meeting with lots of ideas and a general sense that maybe they would be happy using the robot from the Lego Education design, with some modifications. This is a big step since they really want to be original and design their robot from scratch. However, this approach became very time-consuming last year, and also fairly divisive.
For now, they have each agreed to build a robot from other plans or pictures, which they will bring to the next meeting. The emphasis will be on demonstrating any new approaches or great ideas that can be incorporated into their modified base.
The other robot designs they are building:
http://mindstorms.lego.com/MeetMDP/BBonahoom.aspx
http://mindstorms.lego.com/MeetMDP/BDavis.aspx
http://mynxt.matthiaspaulscholz.eu/robots/goliathII/index.html
We have two reservations about restricting the team in this way: these four won't be challenged by new approaches and new ideas; and it may make it even harder to rejuvenate the team with "fresh blood" next year. Nevertheless, the decision was taken and we are all content with the situation for this year.
Since the team membership is now decided, this was the first meeting where we really got down to business with the robot. All kids have had a chance to play with it and experiment, so we set down to the task of considering how this robot kit can solve this year's challenges. The kids came up with some ideas for what would be important in the robot base, and these were recorded. Lots of ideas were thrown out for discussion: treads vs. wheels, how many wheels, where the driving wheels should be, size of the robot, centre of gravity, ways of attaching sensors, etc.
The team left the meeting with lots of ideas and a general sense that maybe they would be happy using the robot from the Lego Education design, with some modifications. This is a big step since they really want to be original and design their robot from scratch. However, this approach became very time-consuming last year, and also fairly divisive.
For now, they have each agreed to build a robot from other plans or pictures, which they will bring to the next meeting. The emphasis will be on demonstrating any new approaches or great ideas that can be incorporated into their modified base.
The other robot designs they are building:
http://mindstorms.lego.com/MeetMDP/BBonahoom.aspx
http://mindstorms.lego.com/MeetMDP/BDavis.aspx
http://mynxt.matthiaspaulscholz.eu/robots/goliathII/index.html
Thursday, September 07, 2006
Week 1: September 6, First Project Meeting
My friend Monique has stepped forward to lead the group in their research project this year. The team met in her home (most meetings are at my place) and gathered around her dining room table to share what they have already learned about nanotechnology. It's a big topic and you can tell that the kids are both intrigued and intimidated by it.
They talked about scale, and tried to put a group of pictures in order from largest to smallest. The pictures included things like single molecules of DNA or carbon, and light waves at various frequencies.
Next Monique brought out a set of test tubes, a pitcher of water, and blue food colouring. They made a series of mixtures, starting out with pure food colouring and diluting it to one-tenth the previous concentration with each step. It didn't take long to understand that one part per billion is very, very little, so one-billionth of anything must be very, very small.
Finally, they considered a list of products that are already on the market, supposedly using nanotechnology in some way. In many cases it wasn't clear just what technology was being used in each of these products, or just how the product was improved by using nanotechnology. They discussed how "nano" could (potentially, not necessarily) be just a marketing term to make something seem better.
Each team member left the meeting with a couple of areas to look into further.
They talked about scale, and tried to put a group of pictures in order from largest to smallest. The pictures included things like single molecules of DNA or carbon, and light waves at various frequencies.
Next Monique brought out a set of test tubes, a pitcher of water, and blue food colouring. They made a series of mixtures, starting out with pure food colouring and diluting it to one-tenth the previous concentration with each step. It didn't take long to understand that one part per billion is very, very little, so one-billionth of anything must be very, very small.
Finally, they considered a list of products that are already on the market, supposedly using nanotechnology in some way. In many cases it wasn't clear just what technology was being used in each of these products, or just how the product was improved by using nanotechnology. They discussed how "nano" could (potentially, not necessarily) be just a marketing term to make something seem better.
Each team member left the meeting with a couple of areas to look into further.
Thursday, August 31, 2006
Preseason: August 30 Open House
Back in the spring, I held an information meeting for families who were interested in FLL after hearing about our experiences. Out of that, three new teams of homeschoolers have formed, and our team has offered to mentor them and help out in whatever ways we can. On this day, one of the other families came over to hang out and try out the new NXT robot kits. So this afternoon was a gathering of three kids from our team, two kids from her team, and a neighbour's son who happened into the chaos.
We had two of the NXT robots at this get-together, so the kids spent time building with them, doing some on-brick programming, and playing with the sensors. The sound and ultrasonic sensors have a definite "cool" factor: there was lots of hand-waving and shouting to make the robot respond.
On our team, all three of our families have decided to purchase the NXT kit. This means that all the kids have the opportunity to be working on the robot at home between meetings. Somehow it seems to give the kids more confidence to be using the newest kit, but it also means that we have another steep learning curve in front of us, as not everything we learned about the RCX will be transferable to this new design.
We had two of the NXT robots at this get-together, so the kids spent time building with them, doing some on-brick programming, and playing with the sensors. The sound and ultrasonic sensors have a definite "cool" factor: there was lots of hand-waving and shouting to make the robot respond.
On our team, all three of our families have decided to purchase the NXT kit. This means that all the kids have the opportunity to be working on the robot at home between meetings. Somehow it seems to give the kids more confidence to be using the newest kit, but it also means that we have another steep learning curve in front of us, as not everything we learned about the RCX will be transferable to this new design.
Saturday, August 26, 2006
Preseason: August 25 Building Day
After the fun of Ocean Odyssey, there was no question that we would participate in NanoQuest. Unfortunately, we lost both of the girls from our team - both returned to institutional school this year and won't have time to participate.
Our returning team members got together in late summer to build some of the new models from the NanoQuest Challenge field kit. It was a busy, fun day. These models are complicated, and some are quite tricky to build.
We can see where they go on the mat, but we're not quite sure of placement or what the missions might be. There are a lot of loose items and we are guessing they will have to be delivered from base, rather than retrieved from the field. Last year included a lot of retrieving, so delivering will be new to us.
The adults spent a while considering our coaching strategies for this year, while the kids built. We agreed that Chaz and I will focus on the robotics, and Monique will lead the project meetings. The younger sibs should be able to play on their own this year and won't need any special activities planned for them. We also agreed to a schedule much like last year: every Tuesday and alternate Fridays for a half-day each time, with part of each Tuesday meeting devoted to the project.
The team also started talking about nanotechnology, considering the science behind the various mission models. One of the big questions from the kids was about how much of this technology is actually possible. Are there really stain-free pants? Well, okay, fine, but do scientists really think they can build an elevator to space?
There are some clear areas of interest already - the ethics and environmental questions are big for this team after their extensive work on environmental issues last year. The space elevator and the possibilities of carbon nanotubes being used for various purposes have really caught the imagination of a couple of the kids.
And there is also some concern about how difficult this topic is - how can children be expected to comprehend this to a level where they can offer valid insights and truly innovative solutions that are not just imaginary? The kids are feeling like they have their work cut out for them, and in truth they are a little apprehensive.
Our returning team members got together in late summer to build some of the new models from the NanoQuest Challenge field kit. It was a busy, fun day. These models are complicated, and some are quite tricky to build.
We can see where they go on the mat, but we're not quite sure of placement or what the missions might be. There are a lot of loose items and we are guessing they will have to be delivered from base, rather than retrieved from the field. Last year included a lot of retrieving, so delivering will be new to us.
The adults spent a while considering our coaching strategies for this year, while the kids built. We agreed that Chaz and I will focus on the robotics, and Monique will lead the project meetings. The younger sibs should be able to play on their own this year and won't need any special activities planned for them. We also agreed to a schedule much like last year: every Tuesday and alternate Fridays for a half-day each time, with part of each Tuesday meeting devoted to the project.
The team also started talking about nanotechnology, considering the science behind the various mission models. One of the big questions from the kids was about how much of this technology is actually possible. Are there really stain-free pants? Well, okay, fine, but do scientists really think they can build an elevator to space?
There are some clear areas of interest already - the ethics and environmental questions are big for this team after their extensive work on environmental issues last year. The space elevator and the possibilities of carbon nanotubes being used for various purposes have really caught the imagination of a couple of the kids.
And there is also some concern about how difficult this topic is - how can children be expected to comprehend this to a level where they can offer valid insights and truly innovative solutions that are not just imaginary? The kids are feeling like they have their work cut out for them, and in truth they are a little apprehensive.
Saturday, July 29, 2006
Rookie Year Recap
Our rookie year, Ocean Odyssey, was a lot of work and a lot of fun.
Our team members were 4 boys and 2 girls, aged 8 to 11, all homeschooled. A couple of the kids had done a little bit with the robot but for the most part it was all new, to me as well. The season was busy and chaotic, as we figured out the robot, the FLL organization, and what was expected at competition.
We ran the team as a cooperative effort, with all parents helping out in some way. I acted as head coach, another mom assisted me with the technical meetings, the one dad in our group guided the kids in the project, and another mom kept time the younger siblings occupied.
In mid-November, we competed at a regional tournament along with 15 other teams (mostly from private schools in Toronto). Our robot had a high score of 127 that day. Throughout our three matches, the team got points from five different missions, but never managed to score on more than three missions in a single round. Nevertheless, we had once been told that a rookie team is doing well if they manage to solve two missions, so we were still proud of ourselves.
At that same tournament, we were surprised and excited to win the first-place award for our project, and to place fourth overall, earning a spot at Provincials. Our project was about pollution in the Great Lakes, and how it affects the beluga whales in the Gulf of St. Lawrence. The team proposed using engineered wetlands to extract the pollution, and (working with Citizens' Environment Watch) had learned how to do benthic invertebrate testing to monitor pollution levels and measure the success of these proposed wetlands.
At Provincials (three weeks later), we were missing two team members so the team had to rework their project skit, and pair up differently to run the robot during the robot matches. The kids had also reworked some of the missions, with the result that the robot's high score that day was 172. That was the 21st-highest score of the day -- not good enough to advance into the "sweet sixteen". They were able to score points in 6 missions by this point, but were only able to score in 4 missions (plus move some of the bonus items into higher-scoring positions) during a single round.
In the other competitive aspects, the kids did even better, winning a first-place trophy for the "Innovative Solution" in their research project.
These competitions were a highlight for the the team - the level of excitement is unbelievable at these events, and the kids loved it. (The parents took Tylenol.) All-in-all, it felt like a very successful season: friendships were forged and lots of fun was had by all.
Our team members were 4 boys and 2 girls, aged 8 to 11, all homeschooled. A couple of the kids had done a little bit with the robot but for the most part it was all new, to me as well. The season was busy and chaotic, as we figured out the robot, the FLL organization, and what was expected at competition.
We ran the team as a cooperative effort, with all parents helping out in some way. I acted as head coach, another mom assisted me with the technical meetings, the one dad in our group guided the kids in the project, and another mom kept time the younger siblings occupied.
In mid-November, we competed at a regional tournament along with 15 other teams (mostly from private schools in Toronto). Our robot had a high score of 127 that day. Throughout our three matches, the team got points from five different missions, but never managed to score on more than three missions in a single round. Nevertheless, we had once been told that a rookie team is doing well if they manage to solve two missions, so we were still proud of ourselves.
At that same tournament, we were surprised and excited to win the first-place award for our project, and to place fourth overall, earning a spot at Provincials. Our project was about pollution in the Great Lakes, and how it affects the beluga whales in the Gulf of St. Lawrence. The team proposed using engineered wetlands to extract the pollution, and (working with Citizens' Environment Watch) had learned how to do benthic invertebrate testing to monitor pollution levels and measure the success of these proposed wetlands.
At Provincials (three weeks later), we were missing two team members so the team had to rework their project skit, and pair up differently to run the robot during the robot matches. The kids had also reworked some of the missions, with the result that the robot's high score that day was 172. That was the 21st-highest score of the day -- not good enough to advance into the "sweet sixteen". They were able to score points in 6 missions by this point, but were only able to score in 4 missions (plus move some of the bonus items into higher-scoring positions) during a single round.
In the other competitive aspects, the kids did even better, winning a first-place trophy for the "Innovative Solution" in their research project.
These competitions were a highlight for the the team - the level of excitement is unbelievable at these events, and the kids loved it. (The parents took Tylenol.) All-in-all, it felt like a very successful season: friendships were forged and lots of fun was had by all.
Subscribe to:
Posts (Atom)