Goals: Difference between revisions
From SpaceElevatorWiki.com
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
'''Vision:''' | '''Vision:''' | ||
* Get Intel code compiling on Ubuntu and into a Mercurial tree. (20 hours) | * Get Intel code compiling on Ubuntu and into a Mercurial tree. (20 hours) | ||
* Hook up .Net wrapper to Intel vision code. ( | * Hook up .Net wrapper to Intel vision code. (10 hours) | ||
* Create / find a 2-frame GUI tool which takes a picture and applies Intel code to it and displays an output image | * Create / find a 2-frame GUI tool which takes a picture and applies appropriate Intel code to it and displays an output image (40 hours) | ||
* Call the Intel code to generate simple analysis. (40 hours) | |||
* Hook the '''input''' of vision recognition to the '''output''' of the 3-D engine! (40 hours) | * Hook the '''input''' of vision recognition to the '''output''' of the 3-D engine! (40 hours) | ||
'''Driving:''' | '''Driving:''' | ||
* Create a C# wrapper for the Torcs driving APIs | * Get Torcs compiling on Ubuntu and in a Mercurial tree (10 hours) | ||
* Port smart baseline driving code to C# | * Create a C# wrapper for the Torcs world and driving APIs (100 hours) | ||
* | * Port smart clean baseline driving code to C# (100 hours) | ||
* Test it and stress it by creating various terrain. (40 hours) | |||
* Hook the '''output''' of the vision recognition into the '''input''' of the driving engine! (40 hours) | * Hook the '''output''' of the vision recognition into the '''input''' of the driving engine! (40 hours) | ||
Revision as of 00:53, 10 June 2008
Vision:
- Get Intel code compiling on Ubuntu and into a Mercurial tree. (20 hours)
- Hook up .Net wrapper to Intel vision code. (10 hours)
- Create / find a 2-frame GUI tool which takes a picture and applies appropriate Intel code to it and displays an output image (40 hours)
- Call the Intel code to generate simple analysis. (40 hours)
- Hook the input of vision recognition to the output of the 3-D engine! (40 hours)
Driving:
- Get Torcs compiling on Ubuntu and in a Mercurial tree (10 hours)
- Create a C# wrapper for the Torcs world and driving APIs (100 hours)
- Port smart clean baseline driving code to C# (100 hours)
- Test it and stress it by creating various terrain. (40 hours)
- Hook the output of the vision recognition into the input of the driving engine! (40 hours)
Debugging features:
- hook the output of the vision recognition into the input of the 3-D engine, by creating ghost images.)
- Ability to log all changes to the world including results of vision analysis, so that we can replay to figure out what happened.
Later Goals
- Add other features like waypoints, stopsigns. (Someone else doing this we should hook up with)
Better 3-D Engine?
- Evaluate better & more professional-looking 3-D and physics engines