<?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: Error in codomain while rotating images in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917393#M15302</link>
    <description>To syncronize our discussion and correct my partly erronious thougts:&lt;BR /&gt;&lt;BR /&gt;It is clear, that there can be an expansion of the range while interpolating bicubic and quadratic (because of the interpolation function).&lt;BR /&gt;&lt;BR /&gt;But this effect also appears with the modes of no or linear interpolation.&lt;BR /&gt;&lt;BR /&gt;So in this case, I think, the result is not correct ...&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;&lt;BR /&gt;M.&lt;BR /&gt;</description>
    <pubDate>Fri, 01 Dec 2006 19:39:01 GMT</pubDate>
    <dc:creator>mweissbach</dc:creator>
    <dc:date>2006-12-01T19:39:01Z</dc:date>
    <item>
      <title>Error in codomain while rotating images</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917390#M15299</link>
      <description>Hi @ all&lt;BR /&gt;
&lt;BR /&gt;
I have an grey-value-image with a codomain of [0..125] for all pixel.
After rotating and interpolating it with my own implemented function, I
get an image with a codomain [0..115.06]. When I use the IPP (Version
5.1) I get a range of values [-1.74..120.0] for all pixels. In my
opinion, this is not possible. The same effect takes place by using the
ippi_resize-functions.&lt;BR /&gt;
&lt;BR /&gt;
I don't know, if this is a bug or a error in reasoning the matter. My
idea was, that by rotating or resizing the range of the pixelvalues
remains to be constant. The interpolation does IMHO only nothing or a
shrinking of the range of values of the image.&lt;BR /&gt;
&lt;BR /&gt;
Can you give me some hints whats the reason for this effect?&lt;BR /&gt;
&lt;BR /&gt;
Thanks a lot&lt;BR /&gt;
&lt;BR /&gt;
best regards&lt;BR /&gt;
&lt;BR /&gt;
M.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jul 2006 19:10:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917390#M15299</guid>
      <dc:creator>mweissbach</dc:creator>
      <dc:date>2006-07-10T19:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: Error in codomain while rotating images</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917391#M15300</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I use INTER_NN, INTER_LINEAR and INTER_CUBIC. Of course InterCubic and InterLinear can change the range. The problem is, that the range should get smaller on both borders by using this interpolation. The strange thing is, that the lower border gets negative values. Is there a logical explaination of this behavior?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;M.&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Nov 2006 23:57:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917391#M15300</guid>
      <dc:creator>mweissbach</dc:creator>
      <dc:date>2006-11-29T23:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Error in codomain while rotating images</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917392#M15301</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Why do you think the range should be smaller? &lt;BR /&gt;Because you interpolate the values. Therefore you make somewhere a meanvalue or something similar ... depends on the interpolation algorithm&lt;BR /&gt;&lt;BR /&gt;&amp;gt; It can exceed the maxboundary as well as min extrimely (see attached picture).&lt;BR /&gt;In my opinion it is not possible. Especially in the case of the lower border, which becomes negative. &lt;BR /&gt;&lt;BR /&gt;I think, that the computation is not correct. But I'm not totally sure. My tests give me the results I espected in contrast to the ones from IPP.&lt;BR /&gt;&lt;BR /&gt;M.&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Dec 2006 18:47:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917392#M15301</guid>
      <dc:creator>mweissbach</dc:creator>
      <dc:date>2006-12-01T18:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: Error in codomain while rotating images</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917393#M15302</link>
      <description>To syncronize our discussion and correct my partly erronious thougts:&lt;BR /&gt;&lt;BR /&gt;It is clear, that there can be an expansion of the range while interpolating bicubic and quadratic (because of the interpolation function).&lt;BR /&gt;&lt;BR /&gt;But this effect also appears with the modes of no or linear interpolation.&lt;BR /&gt;&lt;BR /&gt;So in this case, I think, the result is not correct ...&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;&lt;BR /&gt;M.&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Dec 2006 19:39:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Error-in-codomain-while-rotating-images/m-p/917393#M15302</guid>
      <dc:creator>mweissbach</dc:creator>
      <dc:date>2006-12-01T19:39:01Z</dc:date>
    </item>
  </channel>
</rss>

