Vision: Difference between revisions

Latest revision as of 00:49, 26 November 2008

Here is Why.

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.

@@ Line 1: / Line 1: @@
-[[Image:Torcs.png|400 px|thumb|Analyze this!]]
+[[Image:Torcs.jpg|500 px|thumb|Analyze this!]]
+== Meta ==
+To create a page on the wiki, just go to the URL and mediawiki will create one on demand.
+I go through and polish wordings just to try to make it easier for people to read. After (nearly) writing a book, I understand how important readability is. I might make mistakes, so please fix it and don't be offended that I am making changes...
 == Why work on Vision? ==
 Here is [[Why]].
@@ Line 5: / Line 11: @@
 == Goals ==
 [[Goals]]
-Have a Milestone 1 demo on or before September 8th, 2008.
-== Hard Questions ==
-[[Software_Architecture]]
 == Programmer stuff ==
+* [http://www.monobotics.ic.uach.cl/ GUI tool for doing vision analysis]
-'''Collecting and archiving knowledge is as important as code.''' Be good about linking to great documents (intro or reference) or writing cheat sheets. There is a ton of jargon out there and things are often much simpler than they sound.
-Motion planning sounds fancy and I like using the word, but there is not much to it. In our repository in the docs directory, there is a paper that, despite lots of fluff, explains it well. We will do some good motion planning in our Milestone 1 with about 6,000 lines of C#! I hope that is the same for vision, but I am less sure :-)
 * [[Software Architecture]]
 * [[Build]] environment