Revision as of 15:19, 9 June 2008

Software Architecture

Diagram PDF ODG (FIXME: Upload to wiki?) (I will get uploads to wiki working --KC) There will be 3 main modules:

Driving module will use an interface like this of Torcs:

Input: high level information from the Vision and world simulator.
Output: high level orders to the simulator (which may be replaced by a real car).

Vision module I/O:

World simulator I/O: (Initially, we should probably use Torcs)

Input: sensors -> move the car. (???)
Output: visual output for the user, screenshots for vision module, info that we can query to find out where stuff actually is, etc.

@@ Line 7: / Line 7: @@
 * World Simulator
-== AI ==
+== Driving ==
-AI module will use an interface like this of Torcs:
+Driving module will use an interface like this of Torcs:
-* Input: high level information from the Vision.
+* Input: high level information from the Vision and world simulator.
 * Output: high level orders to the simulator (which may be replaced by a real car).
@@ Line 17: / Line 17: @@
 Vision module I/O:
 * Input: screenshot of the world (real or virtual).
-* Output: the informations necessary to the AI.
+* Output: object geometry, etc. and other information necessary to the AI.
 == World Simulator ==
-World simulator I/O:
+World simulator I/O: ''(Initially, we should probably use Torcs)''
-* Input: sensors -> move the car.
+* Input: sensors -> move the car. (???)
-* Output: visual output for the user, screenshots for vision module.
+* Output: visual output for the user, screenshots for vision module, info that we can query to find out where stuff actually is, etc.