<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OpticalFlowPyrLK performance in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/OpticalFlowPyrLK-performance/m-p/871228#M8948</link>
    <description>&lt;DIV style="margin:0px;"&gt;Hi,&lt;BR /&gt;IPPtest program ps_ippcvem64t.exe returns clocks per element (pixel) per feature point. So toreproduce it tou should devide your time by numFeat parameter.&lt;BR /&gt;&lt;BR /&gt;Igor&lt;/DIV&gt;
&lt;BR /&gt;</description>
    <pubDate>Tue, 13 Jan 2009 08:11:48 GMT</pubDate>
    <dc:creator>Igor_B_Intel1</dc:creator>
    <dc:date>2009-01-13T08:11:48Z</dc:date>
    <item>
      <title>OpticalFlowPyrLK performance</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/OpticalFlowPyrLK-performance/m-p/871227#M8947</link>
      <description>We have executed the example 14-5 of the Manual Image Processing (vol.2) to test OpticalFlowPyrLK with the Yosemite (images of 252x316 pixels). We have used the following values for the input parameters:&lt;BR /&gt;(1) A Gaussian kernel of length 5: 151, 21186, 5319, 2186, 151&lt;BR /&gt;(2) Levels from 1 to 3 (numLevel)&lt;BR /&gt;(3) rate =2&lt;BR /&gt;(4) winSize of 3, 5 and 7&lt;BR /&gt;(5) numIter of 1,2 and 3&lt;BR /&gt;(6) Theshold=0&lt;BR /&gt;(7) prevPt is initialized by using:&lt;BR /&gt; for (i=0;i&lt;ROISIZE.WIDTH&gt;&lt;/ROISIZE.WIDTH&gt; prevPt&lt;I&gt;.x=i%roiSize.width; prevPt&lt;I&gt;.y= i/roiSize.width;&lt;BR /&gt; }&lt;BR /&gt;Then, the flow is obtained for all the pixels.&lt;BR /&gt;(8) nextPt is equal than prevPt.&lt;BR /&gt;We obtain 2879.2 cycles per pixel (in the input image) with a Gaussian filter of length 5, numLevel=1, numIter=1, winSize=3 (cycles of the processor clock obtained with instruction rdtsc). This is a high value. With other combination the number of cycles is yet higher. &lt;BR /&gt;Nevertheless, with the IPPtest programps_ippcvem64t.exe we obtain 10 , 6, or 2 clocks per element (depends on the input parameters) for images of 256x256 pixels.&lt;BR /&gt;What are we doing wrong? Is the source code for ps_ippcvem64t.exe available? We cannot reproduce the clocks per element of this test (we suppose clocks per element are cycles per pixel in this context).&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;/I&gt;&lt;/I&gt;</description>
      <pubDate>Wed, 07 Jan 2009 18:06:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/OpticalFlowPyrLK-performance/m-p/871227#M8947</guid>
      <dc:creator>mancita</dc:creator>
      <dc:date>2009-01-07T18:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: OpticalFlowPyrLK performance</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/OpticalFlowPyrLK-performance/m-p/871228#M8948</link>
      <description>&lt;DIV style="margin:0px;"&gt;Hi,&lt;BR /&gt;IPPtest program ps_ippcvem64t.exe returns clocks per element (pixel) per feature point. So toreproduce it tou should devide your time by numFeat parameter.&lt;BR /&gt;&lt;BR /&gt;Igor&lt;/DIV&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jan 2009 08:11:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/OpticalFlowPyrLK-performance/m-p/871228#M8948</guid>
      <dc:creator>Igor_B_Intel1</dc:creator>
      <dc:date>2009-01-13T08:11:48Z</dc:date>
    </item>
  </channel>
</rss>

