Changeset 705
- Timestamp:
- 02/22/10 21:06:48 (2 years ago)
- Files:
-
- 1 modified
-
branches/2010-image-rec/docs/report.tex (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
branches/2010-image-rec/docs/report.tex
r702 r705 164 164 \end{figure} 165 165 166 The next step with our algorithm is to make it work on cases where it fails, 167 those with lines appearing within our safe zone. It is possible that this 166 The next step with our algorithm is to make it work on cases where it fails, in \ref{fig:safe-region} 167 there is an example of an image where line pixels appear in the assumed safe zone. Further work will 168 include excluding these pixels from the histogram. It is possible that this 168 169 could be done by excluding portions of the ``safe zone'' which exceed a 169 170 threshold in brightness, or to apply the previous image's histogram to the safe 170 zone and exclude those pixels that fall far outside it. There is also work to 171 zone and exclude those pixels that fall far outside it. Another case where our algorithm fails is 172 is in \ref{fig:hough-failure}. The obstacle very close to the camera in the image includes more texture than our 173 algoristhm expects of an obastacle, and missclassifies it as a set of line pixels. 174 A similar problem occurs where regions further away may have lower texture than grassy regions 175 nearer the camera. One solution may be to add to the percieved texture in an image based on height within 176 the image. There is also work to 171 177 be done for it to be run on the robot. The algorithm must be able to run in 172 178 real time to support live decision-making, which means that it must be ported

