<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Offline on Miles Macklin</title>
    <link>http://blog.mmacklin.com/tags/offline/</link>
    <description>Recent content in Offline on Miles Macklin</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2019 Miles Macklin</copyright>
    <lastBuildDate>Sun, 03 Oct 2010 23:37:47 +0000</lastBuildDate><atom:link href="http://blog.mmacklin.com/tags/offline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracing</title>
      <link>http://blog.mmacklin.com/2010/10/03/tracing/</link>
      <pubDate>Sun, 03 Oct 2010 23:37:47 +0000</pubDate>
      
      <guid>http://blog.mmacklin.com/2010/10/03/tracing/</guid>
      <description>Gregory Pakosz reminded me to write a follow up on my path tracing efforts since my last post on the subject. It&#39;s good timing because the friendly work-place competition between Tom and me has been in full swing. The great thing about ray tracing is that there are many opportunities for optimisation at all levels of computation. This keeps you &#34;hooked&#34; by constantly offering decent speed increases for relatively little effort.</description>
    </item>
    
  </channel>
</rss>
