Turtle Art with Sensors
This project has now been merged with Turtle Art, see http://wiki.sugarlabs.org/go/Activities/TurtleArt#Sensors_Palette
and for sensor ideas
See the Sensor input section of the measure page and the sections below for details about how this was accomplished.
Downloading and running the Activity
Latest -- The Activity now works in Spanish too
//screenshots of new turtle art sensors block //sensor experiments
Sensors - how to and where from
// howto needed...
Note: All the children's' names are fictional
On Wednesday, 23rd January, 2008 we had a Turtle Art with Sensors session at the Fablab in Boston. The FabLab at Boston is , amongst the many FabLabs around the world, the closest to the MIT Media Lab research group that has initiated and implemented this concept. See Center for Bits and Atoms.
Fab Lab is an abbreviation for Fabrication Laboratory. It is a group of off-the-shelf, industrial-grade fabrication and electronics tools, wrapped in open source software and programs written by researchers at the Center for Bits and Atoms. It is a place where basically anyone can come and create At any given time one can usually see a lot of interesting projects going on there. For example a lady was working on printing T-shirts with a "Give one get one (hug)" logo This was for a charitable program that her father has started. Then I met a young college student who had come to the FabLab to make a generic LED dot-matrix display, the design for which can be scaled to any meet any design/pattern of any size. His current aim was to build an analog clock from the dot matrix display. The overall atmosphere at the FabLab is quite creative and the people one sees there are really involved in 'creating'
Edward Baafi is the person who oversees and co-ordinates the Activities of the Fablab. He is always around to help - whether it is some problem with the Modella machine or it is a programming doubt - Edward can usually solve all your queries.
A group of high school students meets up every Wednesday at the FabLab. The meet up is supervised by Edward Baafi and they discuss their experiences of the week teaching younger kids in schools nearby. When the kids came in, Edward Baafi explained to them that today's focus was going to be sensors with Turtle Art. They came to a place where I had taken out an assortment of sensor-cables.
We started talking about the XO and their views on the laptop. As soon as we all sat down, Ken couldn't wait to ask me "why is the XO better than the Classmate PC?" Ken is very technologically aware and is used to checking his email on his T-mobile email enabled phone. It wasn't hard for him to understand the technological as well as the educational focus areas of the XO laptop that make it different from any other laptop.
All of the kids - Ken, Ben, Grace, Manu, Andriani, are aware of Turtle Art, Scratch and programming environments. They've been used to using computers while working with younger kids from nearby areas; they've just recently been doing it using XOs.
The original author of the Turtle Art activity is Brian Silverman.
Sensor support has been added by Arjun Sarwal who can be contacted via details given on his user page.
|Genre:||Activity genre::Math and Science|
|Activity group:||,|x|Activity group::x}}|
|Short description:||Short description::A version of Turtle Art that supports sensor input|
|Repository URL:||Source code::http://dev.laptop.org/~arjs/TurtleArtwithSensors-3.xo|
|Available languages:||,|x|Available languages::x}}|
|Available languages (codes):||,|x|Language code::x}}|
|Related projects:||Related projects,|x|Related projects::x}}|
|URL from which to download the latest .xo bundle||Activity bundle::http://dev.laptop.org/~arjs/TurtleArtwithSensors-3.xo|
|Last tested version number:||Activity version::3|
|The releases with which this version of the activity has been tested.||,|x|Software release::x}}|
|Development status:||Devel status::3. Alpha|
|Ready for testing (development has progressed to the point where testers should try it out):||,|x|Ready for testing::x}}|
|smoke tested :|
|test plan available :|
|test plan executed :|
|developer response to testing :|