Vision: Difference between revisions
No edit summary |
|||
| Line 12: | Line 12: | ||
== Programmer stuff == | == Programmer stuff == | ||
'''Collecting and archiving knowledge is as important as code.''' Be good about linking to great intro documents, or writing cheat sheets. There is a ton of jargon out there and things are often much simpler than they sound. | |||
Motion planning sounded hard, but there is not much to it. In our repository in the docs directory, there is a paper, that despite lots of fluff still explains it quite well. I hope that is the same for vision, but I don't know. :-) | |||
* [[Software Architecture]] | * [[Software Architecture]] | ||
Revision as of 09:28, 26 June 2008
Why work on Vision?
Here is Why.
Goals
Have a Milestone 1 demo on or before September 8th, 2008.
Hard Questions
Programmer stuff
Collecting and archiving knowledge is as important as code. Be good about linking to great intro documents, or writing cheat sheets. There is a ton of jargon out there and things are often much simpler than they sound.
Motion planning sounded hard, but there is not much to it. In our repository in the docs directory, there is a paper, that despite lots of fluff still explains it quite well. I hope that is the same for vision, but I don't know. :-)
- Software Architecture
- Build environment
- Codebase Analysis
Hardware
We will buy it as much as possible. If we have anything more than a computer and soldering iron, we have gone too far!
What hardware should we buy to do some demo of an object that can program to move precisely and have it give us input about what it is seeing.
http://www.mobilerobots.com/applications.html
http://www.festo-didactic.com/int-en/learning-systems/new-robotino/
http://www.dyson.com/about/story/anotherproblem.asp
