This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Questionable disparity computation performance using VLIB?

Hi Gagan (or someone whoever can answer),

I've waited for another reply for a week, still waiting for a reply to my additional comments.

 

=================================================================================== 

Regarding your questioins,

* What device are you using?

    =>  We obtained the results using PC (Windows XP), but eventually targeting at C6748 EVM.


* What version of library are you using?

    =>  We are using VLIB 2.1


* Did you run the example out of the box or did you do any modification?

    => We changed only some parameters, such as WINDOW_SIZE and BLOCK_SIZE

         for tests.


* What do you mean when you say results are not good?

   => We hope that the disparity map will be a decent result, but the results from using

        the example "VLIB_testDisparity8" were not good (for a variety of parameters).

        The disparity map has big white spots (probably due to using signed char for the disparity?),

         as well as unknown bar-like artifacts (probably due to using block-wise data-reading?).

        It would be nice to have a description about the "VLIB_testDisparity8" test esample.