<?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 Real-Complex Pack2D format - corrections? in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782059#M1615</link>
    <description>At least for the case with even width and even height and for the left-bottom element this table is correct - it MUST be Re A(M/2, 0) and it is.&lt;BR /&gt;You can check it with ippiCplxExtendToPack_32fc32f_C1R function.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Igor</description>
    <pubDate>Tue, 06 Dec 2011 11:11:27 GMT</pubDate>
    <dc:creator>igorastakhov</dc:creator>
    <dc:date>2011-12-06T11:11:27Z</dc:date>
    <item>
      <title>Real-Complex Pack2D format - corrections?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782058#M1614</link>
      <description>I have been using the ippiDFT* functions to do FFTs on real image data. These functions result in RCPack2D data, as described here: &lt;A href="http://software.intel.com/sites/products/documentation/hpc/composerxe/en-us/ippxe/ipp_manual_lnx/hh_goto.htm#IPPI/ippi_ch10/ch10_real_complex_packed_rcpack2d_format.htm"&gt;http://software.intel.com/sites/products/documentation/hpc/composerxe/en-us/ippxe/ipp_manual_lnx/hh_goto.htm#IPPI/ippi_ch10/ch10_real_complex_packed_rcpack2d_format.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I believe there are many errors in that table. For example, shouldn't the bottom left entry be 'Re A(M-1, 0)', not 'Re A(M/2, 0)'? Certainly it should be the same as the rest of the row. And, there should be only real components in the first or last columns, correct?&lt;BR /&gt;&lt;BR /&gt;For what its worth, I've been able to implement my filters with correct resultsbased on what seems natural for the RCPack2D format to do if 2D DFTs are performe real-&amp;gt;complex for the rows, then complex-&amp;gt;complex for the columns (N/2+1 of them). If my understanding is correct, which gives correct results in practice using the functions, then this table has many errors.&lt;BR /&gt;</description>
      <pubDate>Mon, 05 Dec 2011 02:03:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782058#M1614</guid>
      <dc:creator>skycle</dc:creator>
      <dc:date>2011-12-05T02:03:35Z</dc:date>
    </item>
    <item>
      <title>Real-Complex Pack2D format - corrections?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782059#M1615</link>
      <description>At least for the case with even width and even height and for the left-bottom element this table is correct - it MUST be Re A(M/2, 0) and it is.&lt;BR /&gt;You can check it with ippiCplxExtendToPack_32fc32f_C1R function.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Igor</description>
      <pubDate>Tue, 06 Dec 2011 11:11:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782059#M1615</guid>
      <dc:creator>igorastakhov</dc:creator>
      <dc:date>2011-12-06T11:11:27Z</dc:date>
    </item>
    <item>
      <title>Can anyone shed some light as</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782060#M1616</link>
      <description>&lt;P&gt;Can anyone shed some light as to why the following example will not work for "large" images (300x300)&amp;nbsp;I got it to work for small sizes (up to 300x290), but when I use "big" data sizes, I get a stack overflow on ippiDFTFwd_RToPack_32f_C1R. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;// create sample data&lt;/P&gt;
&lt;P&gt;int w=1024;&lt;BR /&gt;int h=1024;&lt;BR /&gt;float imgsize=w*h;&lt;BR /&gt;float* indata=new float[imgsize];&lt;BR /&gt;for(int i=0;i&amp;lt;w;i++){&lt;BR /&gt;&amp;nbsp; &amp;nbsp;for(int j=0;j&amp;lt;h;j++){&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;indata[i+j*w]= i*1.f;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; }&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;float *ipp_float=new float[imgsize]; // real result data&lt;/P&gt;
&lt;P&gt;float *ipp_pack = new float[imgsize];//intermediate packed data&lt;/P&gt;
&lt;P&gt;IppiSize ippSize={w,h};&lt;/P&gt;
&lt;P&gt;IppiDFTSpec_R_32f* ippPlan ;&lt;BR /&gt;ippiDFTInitAlloc_R_32f(&amp;amp;ippPlan,ippSize,IPP_FFT_NODIV_BY_ANY,ippAlgHintFast);&lt;BR /&gt;// this is crashing horribly with stack overflow when indata is large 1024x1024&lt;BR /&gt;ippiDFTFwd_RToPack_32f_C1R(indata, w ,ipp_pack ,w ,ippPlan,0 );&lt;BR /&gt;&lt;BR /&gt;ippiDFTInv_PackToR_32f_C1R(ipp_pack , w*sizeof(Ipp32f) ,ipp_float, w*sizeof(Ipp32f) ,ippPlan,0 );&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2013 21:25:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782060#M1616</guid>
      <dc:creator>brooke_s_</dc:creator>
      <dc:date>2013-04-18T21:25:04Z</dc:date>
    </item>
    <item>
      <title>*update* The above code seems</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782061#M1617</link>
      <description>&lt;P&gt;*update* The above code seems to allow either width or height to be greater than 290, but not both.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2013 21:35:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Real-Complex-Pack2D-format-corrections/m-p/782061#M1617</guid>
      <dc:creator>brooke_s_</dc:creator>
      <dc:date>2013-04-18T21:35:33Z</dc:date>
    </item>
  </channel>
</rss>

