<?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: RGB2Gray round off? in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885767#M10801</link>
    <description>&lt;P&gt;Ops, just double-check with developer, the more correct statement is that we provide +/- 1 precision in that function because of performance tradeoff. Please let us know if this is critical issue for you.&lt;/P&gt;
&lt;P&gt;Vladimir&lt;/P&gt;</description>
    <pubDate>Tue, 06 Feb 2007 04:40:11 GMT</pubDate>
    <dc:creator>Vladimir_Dudnik</dc:creator>
    <dc:date>2007-02-06T04:40:11Z</dc:date>
    <item>
      <title>RGB2Gray round off?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885765#M10799</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;According to the image processing documentation, functional results are often "rounded to the nearest integer". I am finding this not to be the case. For example, the following code demonstrates what I'm finding. &lt;BR /&gt;&lt;BR /&gt;     BYTE* boo = new BYTE[ 1 * 3 ];&lt;BR /&gt;     IppiSize boo_roi;&lt;BR /&gt;     boo_roi.height = 1;&lt;BR /&gt;     boo_roi.width = 3;&lt;BR /&gt;     boo[0] = 113;&lt;BR /&gt;     boo[1] = 134;&lt;BR /&gt;     boo[2] = 115;&lt;BR /&gt;&lt;BR /&gt;     BYTE* bood = new BYTE[ 1 * 1];&lt;BR /&gt;     ippiRGBToGray_8u_C3C1R( boo, 3, bood, 1, boo_roi);&lt;BR /&gt;&lt;BR /&gt;     printf("TEST RGB TO GRAY on (113,134,115) = %d yet math = %.4f
",bood[0], &lt;BR /&gt;      0.299*113 + 0.587*134 + 0.114*115);&lt;BR /&gt;&lt;BR /&gt;Output is the following : &lt;BR /&gt;TEST RGB TO GRAY on (113,134,115) = 125 yet math = 125.5550&lt;BR /&gt;&lt;BR /&gt;So if the floating point value of one-pixel rgb image if 125.550, shouldn't the nearest integer be 126, not 125?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Matt&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Jan 2007 08:48:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885765#M10799</guid>
      <dc:creator>yaddayadda22</dc:creator>
      <dc:date>2007-01-30T08:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: RGB2Gray round off?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885766#M10800</link>
      <description>&lt;P&gt;Hi Matt,&lt;/P&gt;
&lt;P&gt;you are right, it was an issue in IPP 5.1. We have fixed it in IPP 5.2 beta&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt; Vladimir&lt;/P&gt;</description>
      <pubDate>Mon, 05 Feb 2007 06:56:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885766#M10800</guid>
      <dc:creator>Vladimir_Dudnik</dc:creator>
      <dc:date>2007-02-05T06:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: RGB2Gray round off?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885767#M10801</link>
      <description>&lt;P&gt;Ops, just double-check with developer, the more correct statement is that we provide +/- 1 precision in that function because of performance tradeoff. Please let us know if this is critical issue for you.&lt;/P&gt;
&lt;P&gt;Vladimir&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2007 04:40:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/RGB2Gray-round-off/m-p/885767#M10801</guid>
      <dc:creator>Vladimir_Dudnik</dc:creator>
      <dc:date>2007-02-06T04:40:11Z</dc:date>
    </item>
  </channel>
</rss>

