<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MacSingularity Archive &#187; IDL</title>
	<atom:link href="http://macsingularity.org/tag/idl/feed/" rel="self" type="application/rss+xml" />
	<link>http://macsingularity.org</link>
	<description>The archive of Macsingularity</description>
	<lastBuildDate>Fri, 24 Jun 2011 18:35:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>IDL 6.4.1 patch for Leopard Compatibility</title>
		<link>http://macsingularity.org/2007/11/09/idl-641-patch-for-leopard-compatibility/</link>
		<comments>http://macsingularity.org/2007/11/09/idl-641-patch-for-leopard-compatibility/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 19:18:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IDL]]></category>
		<category><![CDATA[Leopard]]></category>

		<guid isPermaLink="false">http://macsingularity.org/2007/11/09/idl-641-patch-for-leopard-compatibility/</guid>
		<description><![CDATA[I&#8217;m not running IDL of any stripe on my Macbook, but it would seem there is a patch for IDL 6.4 that will fix compatibility issues you may encounter with Leopard. From what I can tell from this thread the problem sounds related to the X11 changes in Leopard.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m not running IDL of any stripe on my Macbook, but it would seem there is a <a href="http://www.ittvis.com/forum/message.asp?fmid=4337">patch for IDL 6.4</a> that will fix compatibility issues you may encounter with Leopard.  From what I can tell from <a href="http://groups.google.com/group/comp.lang.idl-pvwave/browse_thread/thread/0564c68bf1ed6c00/f8b2825f620b2553">this thread</a> the problem sounds related to the X11 changes in Leopard.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsingularity.org/2007/11/09/idl-641-patch-for-leopard-compatibility/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IDL and Mouse Cursor problems on OS X</title>
		<link>http://macsingularity.org/2007/03/23/idl-and-mouse-cursor-problems-on-os-x/</link>
		<comments>http://macsingularity.org/2007/03/23/idl-and-mouse-cursor-problems-on-os-x/#comments</comments>
		<pubDate>Fri, 23 Mar 2007 15:17:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IDL]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[Leopard]]></category>
		<category><![CDATA[x11]]></category>

		<guid isPermaLink="false">http://macsingularity.org/2007/03/23/idl-and-mouse-cursor-problems-on-os-x/</guid>
		<description><![CDATA[If you have any issues getting IDL to properly record/recognize the cursor position or mouse clicks, you may want to try this command in the terminal defaults write com.apple.x11 wm_click_through -bool true Frank Varosi here at UF gave me this tip, which he found at this french site. What this command does is it changes [...]]]></description>
			<content:encoded><![CDATA[<p>If you have any issues getting IDL to properly record/recognize the cursor position or mouse clicks, you may want to try this command in the terminal</p>

<pre><code> defaults write com.apple.x11 wm_click_through -bool true
</code></pre>

<p>Frank Varosi here at UF gave me this tip, which he found at this <a href="http://marc.sauvage.free.fr/SApMUG/Xnotes.html#idlcursor">french site</a>.  What this command does is it changes a window manager preference in Apple&#8217;s X11.  This probably only effects the so-called &#8220;Quartz VM&#8221; which is the default window manager.  If you switched to the enlightenment or some other window manager, my guess is this click-through preference has no effect, but I can&#8217;t say for sure.</p>

<p>Personally, I&#8217;ve yet to write IDL programs that look for the cursor location, but I figure this may be helpful to others.</p>

<p><strong>Update</strong> As a commenter noted, you will have to restart X11 for this to do anything, since it&#8217;s changing a preference in Apple&#8217;s quartz-vm window manager.</p>

<p><strong>Update II</strong>  As <a href="#comment-26316">commenter Josh Shiode</a> noted, the Macosforge X11 (and possibly any X11 with Leopard) requires a slightly different command:</p>

<pre><code>        defaults write org.x.x11 wmclickthrough -bool true
</code></pre>
]]></content:encoded>
			<wfw:commentRss>http://macsingularity.org/2007/03/23/idl-and-mouse-cursor-problems-on-os-x/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Using IDL with a local license server</title>
		<link>http://macsingularity.org/2007/03/17/using-idl-with-a-local-license-server/</link>
		<comments>http://macsingularity.org/2007/03/17/using-idl-with-a-local-license-server/#comments</comments>
		<pubDate>Sat, 17 Mar 2007 18:35:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IDL]]></category>

		<guid isPermaLink="false">http://macsingularity.org/2007/03/17/using-idl-with-a-local-license-server/</guid>
		<description><![CDATA[If you&#8217;re using IDL on a Mac, and also have the IDL license server running on the same Mac, it&#8217;s apparently necessary to set HOSTNAME in /etc/hostconfig. In the old days of OS X this was set by default in hostconfig with a line HOSTNAME=-AUTOMATIC- but this is no longer the case in Tiger, and [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re using IDL on a Mac, and also have the IDL license server running on the same Mac, it&#8217;s apparently necessary to set HOSTNAME in <code>/etc/hostconfig</code>.  In the old days of OS X this was set by default in <code>hostconfig</code> with a line</p>

<pre><code>HOSTNAME=-AUTOMATIC-
</code></pre>

<p>but this is no longer the case in Tiger, and maybe Panther.  Your hostname should be something like mycoolmac.myschool.edu.  I would think using <code>-AUTOMATIC-</code> would work as well, since that should grab your hostname from your DNS.</p>

<p>Thanks to Jessica Lair for this info.</p>

<p><em>FYI, I&#8217;m now trying out <a href="http://www.red-sweater.com/marsedit/">MarsEdit</a> for my posts, which I think I may like more than ecto.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://macsingularity.org/2007/03/17/using-idl-with-a-local-license-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MPFIT for IDL least squares fits</title>
		<link>http://macsingularity.org/2007/03/01/mpfit-for-idl-least-squares-fits/</link>
		<comments>http://macsingularity.org/2007/03/01/mpfit-for-idl-least-squares-fits/#comments</comments>
		<pubDate>Thu, 01 Mar 2007 15:37:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IDL]]></category>
		<category><![CDATA[fitting]]></category>
		<category><![CDATA[MPFIT]]></category>

		<guid isPermaLink="false">http://macsingularity.org/2007/03/01/mpfit-for-idl-least-squares-fits/</guid>
		<description><![CDATA[I discovered MPFIT for tweaking parameters and optimizing curve fits. I had never used curvefit (and when I tried, it didn&#8217;t go that well.) MPFIT takes a bit of time to get the hang of, and I had to tweak my curve-generating code to make it play nice with MPFIT&#8230;. and the initial parameters you [...]]]></description>
			<content:encoded><![CDATA[<p>I discovered <a href="http://cow.physics.wisc.edu/~craigm/idl/fitting.html">MPFIT</a> for tweaking parameters and optimizing curve fits.  I had never used curvefit (and when I tried, it didn&#8217;t go that well.)  MPFIT takes a bit of time to get the hang of, and I had to tweak my curve-generating code to make it play nice with MPFIT&#8230;. and the initial parameters you guess have to be close or it won&#8217;t converge.  But, all said and done, I&#8217;m pretty happy with it.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsingularity.org/2007/03/01/mpfit-for-idl-least-squares-fits/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Future of IRAF</title>
		<link>http://macsingularity.org/2005/07/10/the-future-of-iraf/</link>
		<comments>http://macsingularity.org/2005/07/10/the-future-of-iraf/#comments</comments>
		<pubDate>Sat, 09 Jul 2005 19:58:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[community]]></category>
		<category><![CDATA[future]]></category>
		<category><![CDATA[IDL]]></category>
		<category><![CDATA[IRAF]]></category>
		<category><![CDATA[iraf support]]></category>
		<category><![CDATA[iraf.net]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://spac-21.rice.edu/maciraf/news/noao_opinion.html</guid>
		<description><![CDATA[&#60; p>So, we now have an official word on upcoming changes to IRAF support. The leaked news of changes to IRAF certainly generated some discussion, and some emails. Several questions remain, for me, however in light of this news from NOAO. &#60; p>It&#8217;s certainly understandable that NOAO has in mind to take data reduction at [...]]]></description>
			<content:encoded><![CDATA[<p>&lt;</p>

<p>p>So, we now have an <a href="http://spac-21.rice.edu/maciraf/news/iraf_noao_announcement.two">official word</a> on upcoming changes to IRAF support.  The leaked news of changes to IRAF certainly generated some discussion, and some emails.  Several questions remain, for me, however in light of this news from NOAO.</p>

<p>&lt;</p>

<p>p>It&#8217;s certainly understandable that NOAO has in mind to take data reduction at its facilities in new directions, i.e. this new pipeline, data flow system, whatever they want to call it.  IRAF, is after all, a rather old software package.  However, that said IRAF is extremely important to a large number of users, and far more research is done with IRAF than on NOAO telescopes themselves.  IRAF is important to a large portion of the entire astronomical community, not just as a means to reduce data from NOAO facilities.</p>

<p>&lt;</p>

<p>p>With the announcement, however, several questions remain.</p>

<p>&lt;</p>

<p>p><i>Why did it take a leak to generate a discussion in the community?</i></p>

<p>&lt;</p>

<p>p>It took leaked memos, and emails to NOAO to generate their response.
Previously, they were simply going to announce support changes in September.  I don&#8217;t understand why NOAO can&#8217;t solicit opinion directly from the astronomical community before making huge changes that effect all of us.</p>

<p>&lt;</p>

<p>p><i>How much does supporting IRAF really cost?</i></p>

<p>&lt;</p>

<p>p>It&#8217;s my understanding the support costs for support IRAF are
relatively low.  How many emails can they possibly get about IRAF support
get every day?  I only get one every week at that; I&#8217;m sure they get more
but it can&#8217;t be overwhelming, maybe a few a day?</p>

<p>&lt;</p>

<p>p><i>Does NOAO not understand how important IRAF is to the community at large?</i></p>

<p>&lt;</p>

<p>p>IRAF is not just for reducing data from NOAO telescopes.  IRAF is responsible for about 10 times more referreed publications as NOAO telescopes.  NOAO&#8217;s new data-flow system is great, but it is not in any way a replacement for IRAF.  Are we all supposed to use IDL?  It seems like IRAF is a bargain for all the science it helps produce.</p>

<p>&lt;</p>

<p>p><b>IRAF support should be mantained at the current level</b></p>

<p>&lt;</p>

<p>p>IRAF is as important to the astronomical community as any telescope run by NOAO.  As such, it should be treated as a precious resource, not some archaic system who&#8217;s value can be downplayed.  NOAO should continue to maintain support for IRAF as it is today.  The email help line iraf@noao.edu should be kept, and updates and bug fixes to IRAF should not be given any less priority than they are today.</p>

<p>&lt;</p>

<p>p>I understand that NOAO has limited resources.  IRAF is an instance where the reward is far greater than the expense.  IRAF is used by astronomers all over the country and world.  It&#8217;s also used for educational purposes in college and sometimes even high school classrooms over the country.  I know this from direct emails from teachers and students over the years.</p>

<p>&lt;</p>

<p>p>The expertise of those who helped created and maintain IRAF does not exist outside NOAO, as far as I know.  I have no idea how to fix a bug, how to check source code.  All I&#8217;ve been able to do the last few years is help Macintosh users get through a few UNIX hoops they have to do in order to get IRAF.  If the community at large is supposed to somehow help each other through a bulletin board, I don&#8217;t see how this can be a replacement for the IRAF email desk, since the announcement indicdates that DPP staff itself won&#8217;t answer questions.</p>

<p>&lt;</p>

<p>p>Furthermore, there&#8217;s no reason why the development of IRAF should end just because NOAO says it should.  IRAF is an excellent facility for reducing and analyizing data, even if it is old.  Relatively recent developements such as the GUIAPPS, the new enhanced CL that is on the IRAF web site today &#8211; these should all be encouraged and continued, not cast aside.  What exactly is the goal of de-emphasizing IRAF with no alternative planned for the future?</p>

<p>&lt;</p>

<p>p>This entire incident has hurt NOAO&#8217;s reputation.  It would appear that they do understand the deep reliance on IRAF that exists in the astronomical community.  IRAF should be enhanced and celebrated &#8211; not lowered to some second-tier support level.  To me, it seems like that&#8217;s just the first step on the road to retirement.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsingularity.org/2005/07/10/the-future-of-iraf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

