<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: LIC flow code</title>
	<atom:link href="http://michaelgalloy.com/2007/12/09/lic-flow-code.html/feed" rel="self" type="application/rss+xml" />
	<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html</link>
	<description>Resources for IDL developers</description>
	<pubDate>Thu, 28 Aug 2008 00:37:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: michaelgalloy.com &#187; Line-integral convolution code</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-54782</link>
		<dc:creator>michaelgalloy.com &#187; Line-integral convolution code</dc:creator>
		<pubDate>Fri, 11 Apr 2008 06:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-54782</guid>
		<description>[...] finished the line-integral convolution (LIC) implementation as a DLM and cleaned it up a bit (see other articles for background). More work is needed, but it can give useful results now. The movie at the [...]</description>
		<content:encoded><![CDATA[<p>[...] finished the line-integral convolution (LIC) implementation as a DLM and cleaned it up a bit (see other articles for background). More work is needed, but it can give useful results now. The movie at the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Galloy</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-54274</link>
		<dc:creator>Michael Galloy</dc:creator>
		<pubDate>Tue, 08 Apr 2008 21:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-54274</guid>
		<description>OK, I &lt;em&gt;finally&lt;/em&gt; have this code as a DLM. Execution time is a couple order of magnitudes faster: from 187.0 seconds down to 2.1 seconds for the 512 by 256 example running on my iMac. 

I'm going to package this in a visualization library with some other stuff and make it available soon.</description>
		<content:encoded><![CDATA[<p>OK, I <em>finally</em> have this code as a DLM. Execution time is a couple order of magnitudes faster: from 187.0 seconds down to 2.1 seconds for the 512 by 256 example running on my iMac. </p>
<p>I&#8217;m going to package this in a visualization library with some other stuff and make it available soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaelgalloy.com &#187; Overview of flow visualization in IDL</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-51090</link>
		<dc:creator>michaelgalloy.com &#187; Overview of flow visualization in IDL</dc:creator>
		<pubDate>Wed, 19 Mar 2008 19:06:28 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-51090</guid>
		<description>[...] is available through vel, plot_field, or using particle_trace without appropriate seeds. I wrote an article about LIC and have a slow implementation. LIT, OSTR, and GSTR are not available from the IDL [...]</description>
		<content:encoded><![CDATA[<p>[...] is available through vel, plot_field, or using particle_trace without appropriate seeds. I wrote an article about LIC and have a slow implementation. LIT, OSTR, and GSTR are not available from the IDL [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Galloy</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-40931</link>
		<dc:creator>Michael Galloy</dc:creator>
		<pubDate>Thu, 17 Jan 2008 16:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-40931</guid>
		<description>I started on the DLM for the LIC implementation, hopefully I can finish it up this weekend.  

I think that it would be good to answer your question about the key points of understanding the LIC method. I'll write up a brief description with the article about the DLM.

On the second question, I'm not sure if LIC can solve your problem. I'm certainly no export on this technique, I just read a few papers. But I haven't seen it used to twirl an image as you describe. I have seen it used on images to create motion blur and a "painted" effect.</description>
		<content:encoded><![CDATA[<p>I started on the DLM for the LIC implementation, hopefully I can finish it up this weekend.  </p>
<p>I think that it would be good to answer your question about the key points of understanding the LIC method. I&#8217;ll write up a brief description with the article about the DLM.</p>
<p>On the second question, I&#8217;m not sure if LIC can solve your problem. I&#8217;m certainly no export on this technique, I just read a few papers. But I haven&#8217;t seen it used to twirl an image as you describe. I have seen it used on images to create motion blur and a &#8220;painted&#8221; effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wu zhenzhong</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-40874</link>
		<dc:creator>wu zhenzhong</dc:creator>
		<pubDate>Thu, 17 Jan 2008 08:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-40874</guid>
		<description>I am a studend from China!Now I am doing a image transform in c/c++ just like the twirl transform in the photoshop! Somebody told me that the LIC method could  solve the problem .
      Maybe because I know little about image ,or my English is poor,I can not understand the paper --Imaging Vector Fields Using Line Integral Convolution well. I do not know how to present it in C/C++.
       I do not know if LIC can solve my problem.The input image is not transformed in twirl.Of course,you can see the twirl transform in the photoshop.
       Could you help me,please?My question are:
        1?Can you please give me the key points of understanding LIC method?
        2?Does LIC method can solve my problem?
        If there are C/C++ codes  with your answer to the two questions is better!  
 
        
         THANK YOU!</description>
		<content:encoded><![CDATA[<p>I am a studend from China!Now I am doing a image transform in c/c++ just like the twirl transform in the photoshop! Somebody told me that the LIC method could  solve the problem .<br />
      Maybe because I know little about image ,or my English is poor,I can not understand the paper &#8211;Imaging Vector Fields Using Line Integral Convolution well. I do not know how to present it in C/C++.<br />
       I do not know if LIC can solve my problem.The input image is not transformed in twirl.Of course,you can see the twirl transform in the photoshop.<br />
       Could you help me,please?My question are:<br />
        1?Can you please give me the key points of understanding LIC method?<br />
        2?Does LIC method can solve my problem?<br />
        If there are C/C++ codes  with your answer to the two questions is better!  </p>
<p>         THANK YOU!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Galloy</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-35570</link>
		<dc:creator>Michael Galloy</dc:creator>
		<pubDate>Tue, 18 Dec 2007 17:53:18 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-35570</guid>
		<description>Yes, datasets have to be scaled to the size of the desired output image. This part is easy, see the main-level example program in the code for an example.

But, yes, the major problem is that it is really slow for any interesting size dataset. A DLM seems to be the way to go here. I'll be doing some work in this area in January, so I'm hoping to have a faster solution then.</description>
		<content:encoded><![CDATA[<p>Yes, datasets have to be scaled to the size of the desired output image. This part is easy, see the main-level example program in the code for an example.</p>
<p>But, yes, the major problem is that it is really slow for any interesting size dataset. A DLM seems to be the way to go here. I&#8217;ll be doing some work in this area in January, so I&#8217;m hoping to have a faster solution then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mankoff</title>
		<link>http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-35569</link>
		<dc:creator>mankoff</dc:creator>
		<pubDate>Tue, 18 Dec 2007 17:37:37 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgalloy.com/2007/12/09/lic-flow-code.html#comment-35569</guid>
		<description>I was excited to use this code. We need to provide vector display of data on a globe, but unfortunately the vector options in IDL make vector length a fraction of the grid cell, so any projection other than /CYLINDRICAL provides misleading vector lengths due to changing grid cell sizes. Your code appears to solve this.

There are two issues I have come across: 1) Our dataset is a FLTARR(36,24). It seems I need to scale this by a factor of 10 or more to get decent graphics from MG_LIC. 2) The speed moves from acceptable but slow to unacceptably slow once the array is enlarged.

I look forward to a DLM. I'll subscribe to the comments feed on this post to monitor progress. I'll also discuss doing the port ourselves as we are quite interested in this functionality, and let you know if we decide to do so.</description>
		<content:encoded><![CDATA[<p>I was excited to use this code. We need to provide vector display of data on a globe, but unfortunately the vector options in IDL make vector length a fraction of the grid cell, so any projection other than /CYLINDRICAL provides misleading vector lengths due to changing grid cell sizes. Your code appears to solve this.</p>
<p>There are two issues I have come across: 1) Our dataset is a FLTARR(36,24). It seems I need to scale this by a factor of 10 or more to get decent graphics from MG_LIC. 2) The speed moves from acceptable but slow to unacceptably slow once the array is enlarged.</p>
<p>I look forward to a DLM. I&#8217;ll subscribe to the comments feed on this post to monitor progress. I&#8217;ll also discuss doing the port ourselves as we are quite interested in this functionality, and let you know if we decide to do so.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
