Some of the key computer vision skills required for Humanoid Robotic Vision from my point of understanding are:
1.) Hough transforms to detect line/planes/contours etc.
2.) Perspective vision (Especially if we use two cameras for (eye-like) vision, and for depth mapping).
3.) Block matching for correcting the left and right side vision problems.(Jut close one eye and you'll find the image significantly different from when its two eyes, to simulate this kind of correction for a computer is a pretty difficult task and is ongoing current research efforts.)
4.) Calculating odometry information by calculating the kinematic transforms for each step the robot takes. This is necessary for keeping balance without a special sensor for balance.
5.) Calculating the floor planes from the visual information using standard 3-D reconstruction techniques and/or depth maps.
6.) Creating an occupancy grid once we have made the floor plane and clustered it into object blocked clusters and free clusters.
7.) Making an efficient algorithm to plan paths based on the Occupancy Grid. (Maybe A* or Dijkstra's or something)
1.) Hough transforms to detect line/planes/contours etc.
2.) Perspective vision (Especially if we use two cameras for (eye-like) vision, and for depth mapping).
3.) Block matching for correcting the left and right side vision problems.(Jut close one eye and you'll find the image significantly different from when its two eyes, to simulate this kind of correction for a computer is a pretty difficult task and is ongoing current research efforts.)
4.) Calculating odometry information by calculating the kinematic transforms for each step the robot takes. This is necessary for keeping balance without a special sensor for balance.
5.) Calculating the floor planes from the visual information using standard 3-D reconstruction techniques and/or depth maps.
6.) Creating an occupancy grid once we have made the floor plane and clustered it into object blocked clusters and free clusters.
7.) Making an efficient algorithm to plan paths based on the Occupancy Grid. (Maybe A* or Dijkstra's or something)
These seem like some solid points. You may also want to look into some OCR (optical character reader) methods as well.
ReplyDelete