<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>michaelgalloy.com</title>
	<link>http://michaelgalloy.com</link>
	<description>Resources for IDL developers</description>
	<pubDate>Tue, 01 Jul 2008 22:19:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<item>
		<title>IDL Workbench 7.0.3 arrives</title>
		<link>http://michaelgalloy.com/2008/07/01/idl-workbench-703-arrives.html</link>
		<comments>http://michaelgalloy.com/2008/07/01/idl-workbench-703-arrives.html#comments</comments>
		<pubDate>Tue, 01 Jul 2008 21:08:34 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<category><![CDATA[IDLdoc]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/07/01/idl-workbench-703-arrives.html</guid>
		<description><![CDATA[ IDL Workbench 7.0.3 arrived today via the automatic software update mechanism in the Workbench. It provides HDF and netCDF library udpates, better path support, IDLdoc support (rst format only), and even faster code analysis when the Workbench starts. Everything seems to be working well for me during use this afternoon.
Since I&#8217;m most excited about [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://michaelgalloy.com/wp-content/uploads/2008/07/add-routine-comments.png" width="231" height="266" alt="Add routine comments" align="left" hspace="8"/> IDL Workbench 7.0.3 arrived today via the automatic software update mechanism in the Workbench. It provides HDF and netCDF library udpates, better path support, IDLdoc support (rst format only), and even faster code analysis when the Workbench starts. Everything seems to be working well for me during use this afternoon.</p>
<p>Since I&#8217;m most excited about the IDLdoc features, I will describe them in a bit more detail after the jump. <a href="http://michaelgalloy.com/2008/06/18/idldoc-31.html" title="http://michaelgalloy.com/2008/06/18/idldoc-31.html" >IDLdoc 3.1</a> (<a href="http://idldoc.idldev.com/wiki/Downloads" title="IDLdoc downloads page" onclick="javascript:urchinTracker ('/outbound/article/idldoc.idldev.com');">download</a>) is required to integrate with the Workbench.</p>
<p> <a href="http://michaelgalloy.com/2008/07/01/idl-workbench-703-arrives.html#more-209" class="more-link" >(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/07/01/idl-workbench-703-arrives.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Some HDF5 helper routines</title>
		<link>http://michaelgalloy.com/2008/06/27/some-hdf5-helper-routines.html</link>
		<comments>http://michaelgalloy.com/2008/06/27/some-hdf5-helper-routines.html#comments</comments>
		<pubDate>Fri, 27 Jun 2008 23:09:59 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/27/some-hdf5-helper-routines.html</guid>
		<description><![CDATA[I use HDF5 quite a bit and have developed some utility routines, mg_h5_dump (docs, code) and mg_h5_getdata (docs, code), that are quite useful for me.
mg_h5_dump gives similar output to the command line utility h5dump with -A set. mg_h5_getdata allows slices of data to be extracted using IDL's normal indexing rules.
For example,


IDL&#62; f = filepath&#40;'hdf5_test.h5', subdir=&#91;'examples', [...]]]></description>
			<content:encoded><![CDATA[<p>I use HDF5 quite a bit and have developed some utility routines, <code class="routine">mg_h5_dump</code> (<a href="http://www.michaelgalloy.com/lib/hdf5/mg_h5_dump.html" >docs</a>, <a href="http://www.michaelgalloy.com/lib/hdf5/mg_h5_dump.pro" >code</a>) and <code class="routine">mg_h5_getdata</code> (<a href="http://www.michaelgalloy.com/lib/hdf5/mg_h5_getdata.html" >docs</a>, <a href="http://www.michaelgalloy.com/lib/hdf5/mg_h5_getdata.pro" >code</a>), that are quite useful for me.</p>
<p><code class="routine">mg_h5_dump</code> gives similar output to the command line utility <code>h5dump</code> with <code>-A</code> set. <code class="routine">mg_h5_getdata</code> allows slices of data to be extracted using IDL's normal indexing rules.</p>
<p>For example,</p>
<div class="syntax_hilite">
<div id="idl-3">
<div class="idl">IDL&gt; f = filepath<span style="color:#006600; font-weight:bold;">&#40;</span><span style="color:#CC0000;">'hdf5_test.h5'</span>, subdir=<span style="color:#006600; font-weight:bold;">&#91;</span><span style="color:#CC0000;">'examples'</span>, <span style="color:#CC0000;">'data'</span><span style="color:#006600; font-weight:bold;">&#93;</span><span style="color:#006600; font-weight:bold;">&#41;</span><br />
IDL&gt; data = mg_h5_getdata<span style="color:#006600; font-weight:bold;">&#40;</span>f, <span style="color:#CC0000;">'/arrays/3D int array'</span>, $<br />
IDL&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bounds=<span style="color:#CC0000;">'3, 5:*:2, 0:49:3'</span><span style="color:#006600; font-weight:bold;">&#41;</span></div>
</div>
</div>
<p>
For more examples, run the main-level programs at the end of the routines:</p>
<div class="syntax_hilite">
<div id="idl-4">
<div class="idl">IDL&gt; .<span style="">run</span> mg_h5_getdata<br />
IDL&gt; .<span style="">run</span> mg_h5_dump</div>
</div>
</div>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/27/some-hdf5-helper-routines.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>GPULib comments</title>
		<link>http://michaelgalloy.com/2008/06/26/gpulib-comments.html</link>
		<comments>http://michaelgalloy.com/2008/06/26/gpulib-comments.html#comments</comments>
		<pubDate>Thu, 26 Jun 2008 19:04:58 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/26/gpulib-comments.html</guid>
		<description><![CDATA[Mort Canty, author of Image Analysis, Classification and Change Detection in Remote Sensing: With Algorithms for ENVI/IDL, is using GPULib and has started blogging his comments on it. So far, so good!
Full disclosure: I work for Tech-X Corporation and worked on the IDL bindings and examples for GPULib.
]]></description>
			<content:encoded><![CDATA[<p>Mort Canty, author of <a href="http://www.amazon.com/Analysis-Classification-Change-Detection-Sensing/dp/0849372518%3FSubscriptionId%3D0PZ7TM66EXQCXFVTMTR2%26tag%3Dharmonicfunct-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0849372518" onclick="javascript:urchinTracker ('/outbound/article/www.amazon.com');">Image Analysis, Classification and Change Detection in Remote Sensing: With Algorithms for ENVI/IDL</a>, is using GPULib and has started <a href="http://fwenvi-idl.blogspot.com/" title="Fun with ENVI-IDL" onclick="javascript:urchinTracker ('/outbound/article/fwenvi-idl.blogspot.com');">blogging</a> his comments on it. So far, so good!</p>
<p><em>Full disclosure: I work for Tech-X Corporation and worked on the IDL bindings and examples for GPULib.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/26/gpulib-comments.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>DocBook output from IDLdoc</title>
		<link>http://michaelgalloy.com/2008/06/26/docbook-output-from-idldoc.html</link>
		<comments>http://michaelgalloy.com/2008/06/26/docbook-output-from-idldoc.html#comments</comments>
		<pubDate>Thu, 26 Jun 2008 16:50:17 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<category><![CDATA[IDLdoc]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/26/docbook-output-from-idldoc.html</guid>
		<description><![CDATA[ I have the framework in place to have IDLdoc produce output besides HTML. This has been a long process beginning in IDLdoc 2.0 when I switched to using templates instead of embedding the HTML code in the IDL code. I have started by writing a set of templates for DocBook output, but intend to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://michaelgalloy.com/wp-content/uploads/2008/06/vis-screenshot.png" ><img src="http://michaelgalloy.com/wp-content/uploads/2008/06/vis-thumbnail.png" width="304" height="87" alt="Thumbnail of DocBook output" align="right" hspace="8" /></a> I have the framework in place to have IDLdoc produce output besides HTML. This has been a long process beginning in IDLdoc 2.0 when I switched to using templates instead of embedding the HTML code in the IDL code. I have started by writing a set of templates for <a href="http://docbook.sourceforge.net/" title="DocBook project" onclick="javascript:urchinTracker ('/outbound/article/docbook.sourceforge.net');">DocBook</a> output, but intend to write a LaTeX set as well.</p>
<p>Here's an example <a href="http://michaelgalloy.com/wp-content/uploads/2008/06/vis.pdf" >PDF</a> of IDLdoc output for a library of routines for visualization I've been thinking about.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/26/docbook-output-from-idldoc.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Smoothed LIC texture</title>
		<link>http://michaelgalloy.com/2008/06/20/smoothed-lic-texture.html</link>
		<comments>http://michaelgalloy.com/2008/06/20/smoothed-lic-texture.html#comments</comments>
		<pubDate>Fri, 20 Jun 2008 18:08:16 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<category><![CDATA[Information design]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/20/smoothed-lic-texture.html</guid>
		<description><![CDATA[ While producing some flow visualizations lately, I've found that smoothing a random texture gives less pixellated looking result than using a purely random texture. I added a texture keyword a while ago so that a common texture could be used for several LIC images, but now I've discovered that playing around with the texture [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://michaelgalloy.com/wp-content/uploads/2008/06/lic-full.png" ><img src="http://michaelgalloy.com/wp-content/uploads/2008/06/lic-thumb.png" width="180" height="100" alt="lic_thumb.png" align="right" hspace="8" title="Random vs. smooth texture"/></a> While producing some flow visualizations lately, I've found that smoothing a random texture gives less pixellated looking result than using a purely random texture. I <a href="http://michaelgalloy.com/2008/04/10/line-integral-convolution-code.html" title="Line-integral convolution code" >added a <code class="keyword">texture</code> keyword</a> a while ago so that a common texture could be used for several LIC images, but now I've discovered that playing around with the texture a bit can be useful. I've been creating the texture with:</p>
<div class="syntax_hilite">
<div id="idl-6">
<div class="idl">IDL&gt; r = randomu<span style="color:#006600; font-weight:bold;">&#40;</span>seed, xsize, ysize<span style="color:#006600; font-weight:bold;">&#41;</span><br />
IDL&gt; t = bytscl<span style="color:#006600; font-weight:bold;">&#40;</span>smooth<span style="color:#006600; font-weight:bold;">&#40;</span>r, <span style="color:#800000;">3</span>, /edge_truncate<span style="color:#006600; font-weight:bold;">&#41;</span><span style="color:#006600; font-weight:bold;">&#41;</span></div>
</div>
</div>
<p>
Click on the thumbnail image to see the full image.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/20/smoothed-lic-texture.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>IDLdoc 3.1</title>
		<link>http://michaelgalloy.com/2008/06/18/idldoc-31.html</link>
		<comments>http://michaelgalloy.com/2008/06/18/idldoc-31.html#comments</comments>
		<pubDate>Wed, 18 Jun 2008 21:06:27 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<category><![CDATA[IDLdoc]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/18/idldoc-31.html</guid>
		<description><![CDATA[I just released IDLdoc 3.1 (see full release notes are below). As per this short blog post, IDLdoc is getting integrated into the IDL Workbench. This release adds some rst markup features that the IDL Workbench will use -- my favorite is to be able to link to images with:
.. image:: filename
IDLdoc will link to [...]]]></description>
			<content:encoded><![CDATA[<p>I just released IDLdoc 3.1 (see full release notes are below). As per <a href="http://michaelgalloy.com/2008/05/29/idldoc-in-the-idl-workbench.html" title="IDLdoc in the Workbench" >this short blog post</a>, IDLdoc is getting integrated into the IDL Workbench. This release adds some rst markup features that the IDL Workbench will use -- my favorite is to be able to link to images with:</p>
<p><code class="listing">.. image:: filename</code></p>
<p>IDLdoc will link to the image and also copy the image file into the output directory (if OUTPUT keyword to IDLDOC routine is used).</p>
<ol>
<li>Added ability to reference images in rst markup. IDLdoc will automatically copy referenced images into the output.</li>
<li>In rst markup, illegal characters like < and > are automatically converted to character entities.</li>
<li>Added `:Description:` tag for compatibility with IDL Workbench update.</li>
<li>Changed default markup parser to rst when format parser is rst.</li>
<li>Miscellaneous small bug fixes.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/18/idldoc-31.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>code_swarm</title>
		<link>http://michaelgalloy.com/2008/06/16/code_swarm.html</link>
		<comments>http://michaelgalloy.com/2008/06/16/code_swarm.html#comments</comments>
		<pubDate>Tue, 17 Jun 2008 05:48:43 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[Information design]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/16/code_swarm.html</guid>
		<description><![CDATA[
 The code_swarm project has created visualizations of the time history of commits to four popular open source projects. It's interesting how each project has its own unique character; there is a large difference between, say, the Python and Eclipse commits.
The visualizations were made with Processing.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://vis.cs.ucdavis.edu/~ogawa/codeswarm/" title="code_swarm project"></p>
<p><img src="http://michaelgalloy.com/wp-content/uploads/2008/06/code-swarm-python.png" width="219" height="55" alt="Code swarm for Python" align="right" hspace="8"/></a> The <a href="http://vis.cs.ucdavis.edu/~ogawa/codeswarm/" title="code_swarm project" onclick="javascript:urchinTracker ('/outbound/article/vis.cs.ucdavis.edu');">code_swarm</a> project has created visualizations of the time history of commits to four popular open source projects. It's interesting how each project has its own unique character; there is a large difference between, say, the Python and Eclipse commits.</p>
<p>The visualizations were made with <a href="http://processing.org" title="Processing" onclick="javascript:urchinTracker ('/outbound/article/processing.org');">Processing</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/16/code_swarm.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Versions.app</title>
		<link>http://michaelgalloy.com/2008/06/04/versionsapp.html</link>
		<comments>http://michaelgalloy.com/2008/06/04/versionsapp.html#comments</comments>
		<pubDate>Wed, 04 Jun 2008 17:00:40 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[Mac]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/06/04/versionsapp.html</guid>
		<description><![CDATA[I just got the beta release of Versions, a Subversion front end for the Mac. I use the command line interface for Subversion for most of day-to-day work, but occasionally I like a visual interface to do comparisons, show timelines, etc. The Subclipse plugin for the Workbench works fairly well for this, but I don't [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://michaelgalloy.com/wp-content/uploads/2008/06/versions.png" width="124" height="108" alt="Versions.app" align="left" hspace="10"/>I just got the beta release of <a href="http://www.versionsapp.com/" title="Vesions.app" onclick="javascript:urchinTracker ('/outbound/article/www.versionsapp.com');">Versions</a>, a Subversion front end for the Mac. I use the command line interface for Subversion for most of day-to-day work, but occasionally I like a visual interface to do comparisons, show timelines, etc. The Subclipse plugin for the Workbench works fairly well for this, but I don't always have the Workbench running and it's slow to start. Versions provides a very Mac-like experience to version control.</p>
<p>I didn't see any mention of the price; I'm hoping they intend to make their money selling Subversion hosting at Beanstalk.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/06/04/versionsapp.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>IDLdoc in the IDL Workbench</title>
		<link>http://michaelgalloy.com/2008/05/29/idldoc-in-the-idl-workbench.html</link>
		<comments>http://michaelgalloy.com/2008/05/29/idldoc-in-the-idl-workbench.html#comments</comments>
		<pubDate>Thu, 29 May 2008 14:43:13 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<category><![CDATA[IDLdoc]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/05/28/idldoc-in-the-idl-workbench.html</guid>
		<description><![CDATA[IDLdoc support will be added to the IDL Workbench in an update planned for June. This will add some really cool features for those who use IDLdoc and the Workbench:

enhanced hover help on routines with an IDLdoc header
content assistant on tag names when writing IDLdoc comments
menu item and keyboard shortcut to insert an IDLdoc routine [...]]]></description>
			<content:encoded><![CDATA[<p>IDLdoc support will be added to the IDL Workbench in an update planned for June. This will add some really cool features for those who use IDLdoc and the Workbench:</p>
<ol>
<li>enhanced hover help on routines with an IDLdoc header</li>
<li>content assistant on tag names when writing IDLdoc comments</li>
<li>menu item and keyboard shortcut to insert an IDLdoc routine or file header (and preferences to define what tags you want inserted)</li>
</ol>
<p>The Workbench will recognize comments in the rst format.</p>
<p>There will be an IDLdoc 3.1 release any day now to add some features necessary to support this and fix a couple bugs.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/05/29/idldoc-in-the-idl-workbench.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>IDL help fixes</title>
		<link>http://michaelgalloy.com/2008/05/28/idl-help-fixes.html</link>
		<comments>http://michaelgalloy.com/2008/05/28/idl-help-fixes.html#comments</comments>
		<pubDate>Wed, 28 May 2008 15:30:26 +0000</pubDate>
		<dc:creator>Michael Galloy</dc:creator>
		
		<category><![CDATA[IDL]]></category>

		<guid isPermaLink="false">http://michaelgalloy.com/2008/05/27/idl-help-fixes.html</guid>
		<description><![CDATA[I have not been a big fan of the online help in the IDL 7.0 Workbench, but one feature I have been using regularly is the "Send us a comment on this topic" link at the bottom of every help page. Now I click it for every problem in the documentation I see. It doesn't [...]]]></description>
			<content:encoded><![CDATA[<p>I have not been a big fan of the online help in the IDL 7.0 Workbench, but one feature I have been using regularly is the "Send us a comment on this topic" link at the bottom of every help page. Now I click it for every problem in the documentation I see. It doesn't have the same immediate effect that a Wiki would, but it has a similar feel when I get the response back that it's fixed and I will see it in the next version. Hopefully, others are doing the same (hint, hint).</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelgalloy.com/2008/05/28/idl-help-fixes.html/feed</wfw:commentRss>
		</item>
	</channel>
</rss>
