704
edits
Changes
Jump to navigation
Jump to search
mLine 57:
Line 57: + + + + + + + +
no edit summary
[[Image:BraitenbergWorld.png]]
[[Image:BraitenbergWorld.png]]
The students would be able to see the code to the emulation and also working it graphically. but the interest here is to have a platform for the student to be able to construct it's own robots under different bases
For example line-followers, avoid detection, labyrinth solvers and Brainterberg's ideas explored in:
* http://people.cs.uchicago.edu/~wiseman/vehicles/
* http://instruct.westvalley.edu/lafave/Vehicles_online.html
* http://www.cogs.susx.ac.uk/users/christ/popbugs/intro.html
* http://mrl.nyu.edu/~perlin/
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.