|
Project I "Lessons
Learned" |
Project 2 "Lessons
Learned" |
Project 3 "Lessons
Learned" |
| This
activity will be a great tool to use with my
students to demonstrate the importance for recording
what you are doing |
Ok I
learned a lot from this project |
This was
by far the most satisfying of the three projects for
me. I had the chance to view the solutions of others
and get some feedback on mine, neither of which
happened to any great extent on the first two.
|
| If I was going to
redo this activity I would start much smaller. Since
I am learning MLCAD, creating a robot although small
was a major undertaking. |
The only thing that
did not work with his program was that his turns
were way too much for my Pathfinder (due to him
running his on top of carpet and me on a floor-
different terrain) so I tuned the timing a little
and it worked great! It was very interesting to see
his program in Robolab - how people see things
differently is so interesting! |
A curious element of
the whole exercise has been how little actual
collaboration either went on or was required.
|
| One of
the problems of CAD programs like MLCAD and LDraw is
that you can put the LEGO pieces in the wrong places
which you cannot when you are building with the
actual LEGO pieces. |
I did
not want to modify the robot design as I wanted to
focus on the programming aspect. But I had a real
difficult time with slowing down the robot enough to
have it actually create the square |
Everyone
seemed to be doing his/her own thing and more
interested in presenting and showing off their own
solutions rather than working out a solution as a
whole group. |
| MLCAD turned into a
little LEGO video game for me and I love it.
|
I leaned that robolab
is not the most popular program for programming and
that many of my group members did not use that
program |
In general, to have
more collaboration, I think you might need to have a
more complex project, where each one would be
working on a part of the project, and then finally
putting it together |
| I want to learn how
to do the multi-part CAD diagrams... |
Groups need to
communicate early on in the project. It would be
nice to have groups made up of people who are all
using the same program so that communication about
what and how to modify a program is consistent
|
I feel this project
went better than any of the other ones. So I have no
new suggestions for this one. |
| MLCAD is great
especially when using the mutlimodel. It was also
helpful to learn the proper terminology's for the
parts. |
. I encourage my
students to use rotation sensors when distance
accuracy is important. They soon learn that battery
power and surface dramatically effect how a robot
performs especially if it is pushing any kind of
load |
I would like to see
some days where we have scheduled talks with
everyone in the project. Have everyone present a
lesson that we do. Or just have schedule live talks.
|
| It would be nice to
be able to see everyone's robot designs |
The communication
tools worked fine it was not having the same program
and not knowing how to program with the other
programs that was a problem. |
I believe I was the
most comfortable with the communication tools by
this time and therefore it made that aspect of the
project easier. |
| I would like to see
my middle school students share their design with
other students in our district in this same way
|
An important lesson I
learned was to send a screen shot of the program. My
partner was able to recreate the program from there.
|
|
| Trying to give a
detailed step-by-step directions is harder than I
had first thought. Deciding what robot to build and
how to begin it was one of the hardest |
As instructors, it
might be a good idea to pretest our robots to make
sure it is able to carry out the assigned tasks
before we throw it out to the kids. The problem
definition must be very clear. |
|
| MLCAD is cool
|
|
|
