<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>InsectNation</title>
    <link>http://your-web-site.com/rss/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Articles from the InsectNation Web site.</description>
    
    
        <item>
          <title>Science TV is too nice</title>
          <description>&lt;p&gt;Well well well, another blog post, eh? So soon: it&amp;rsquo;s only been&amp;hellip; erm, two years. Oh. Well I never promised to be prolific. This one&amp;rsquo;s come about because I grumbled briefly on Twitter about the nature of (British) pop-science TV and immediately hit the restrictions of that medium. Twitter is a wonderful way to share neat things that you find online, and to make pithy soundbites &amp;amp; jokes (and for describing what you&amp;rsquo;re eating, the form of public transport that you happen to be on, listing film names with comic vegetable name substitutions&amp;hellip;), but for exploring a non-trivial issue 140 characters is, to put it mildly, a limitation. I have difficulty fitting one of my normal &lt;em&gt;sentences&lt;/em&gt; into 140 characters. So of course I came across as a whining idiot, prompting the reply &amp;ldquo;Yeah, we really should do more about how shit it all is. You don&amp;rsquo;t see that tone ANYWHERE&amp;rdquo; from Dara O&amp;rsquo;Briain. Well, not remotely what I meant, but who can blame him? So here&amp;rsquo;s an attempt at a more coherent and nuanced version that hopefully doesn&amp;rsquo;t make me come across as an anti-science, axe-grinding git. But perhaps as a slightly grumpy science nerd, which is fair enough.&lt;/p&gt;
</description>
          <pubDate>Sun, 14 Apr 2013 00:00:00 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2013/04/14/science-tv-is-too-nice/</guid>
          <link>http://your-web-site.com/articles/2013/04/14/science-tv-is-too-nice/</link>
        </item>
    
        <item>
          <title>Academic journals aren't helping us to do science anymore</title>
          <description>&lt;p&gt;Having recently concluded a long-ongoing saga to get the first &lt;a href=&quot;http://arxiv.org/abs/1012.0791&quot;&gt;ATLAS underlying
event study&lt;/a&gt; both through the experiment&amp;rsquo;s internal review procedures and then
into the perverse format demanded by the academic journal, Physics Review D, to
which we submitted it, it seems an apt time to offer a few comments on the
state of the sacred academic publishing and peer review process.&lt;/p&gt;
</description>
          <pubDate>Sun, 13 Feb 2011 00:00:00 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2011/02/13/academic-journals-arent-helping-us-to-do-science-anymore/</guid>
          <link>http://your-web-site.com/articles/2011/02/13/academic-journals-arent-helping-us-to-do-science-anymore/</link>
        </item>
    
        <item>
          <title>It's a bug, not a feature, René</title>
          <description>&lt;p&gt;I&amp;rsquo;ve had my attention drawn to &lt;a href=&quot;http://permalink.gmane.org/gmane.comp.lang.c%2B%2B.root/11455&quot;&gt;this reply to a ROOT bug report&lt;/a&gt;, which I think highlights a serious problem with how the &lt;a href=&quot;http://root.cern.ch&quot;&gt;ROOT&lt;/a&gt; project interacts with the LHC experiments. In short, someone contacted the ROOTtalk mailing list to inform them that ROOT&amp;rsquo;s calculation of weighted means is incorrect if there are negative weights involved. There is a well-defined procedure for calculating weighted means, and in fact it&amp;rsquo;s dead simple. There&amp;rsquo;s no reason to &lt;em&gt;not&lt;/em&gt; get it right. This is a bug report, about a significant numerical error in just about the simplest statistical quantity that anyone might want to calculate: any statistical analysis tool worth bothering with would provide a bug fix as fast as possible. So how did ROOT respond?&lt;/p&gt;

&lt;p&gt;Well, the response from René Brun, the ROOT project leader, is that ROOT have &amp;ldquo;no plans to change this algorithm&amp;rdquo;. This is absurd: the LHC experiments depend on ROOT to provide them with accurate statistical results. Errors in ROOT mean mistakes in the LHC physics programme: this is not a feature request that can be turned down because it doesn&amp;rsquo;t fit with ROOT&amp;rsquo;s plans, it&amp;rsquo;s a bug which needs to be fixed. That ROOT&amp;rsquo;s management appears to see no reason to get simple calculations correct, and that errors this simple still exist after nearly 20 years of development, is an indictment of ROOT&amp;rsquo;s relationship with the LHC programme&amp;hellip; and of how CERN and the experiments have dropped the ball in making ROOT a useful tool targetted to LHC physics. I&amp;rsquo;ve often heard comments that ROOT is all about empire-building and CERN politics rather than about good science &amp;ndash; I&amp;rsquo;d rather not believe that, but examples such as this make it hard to draw a more appealing conclusion. The nicest thing I can say is that René apparently hasn&amp;rsquo;t understood that this is a bug. If I were feeling more conspiracy-minded I&amp;rsquo;d interpret it as saying that he doesn&amp;rsquo;t care if ROOT is &lt;em&gt;right&lt;/em&gt;, as long as it&amp;rsquo;s &lt;em&gt;used&lt;/em&gt;. And it is certainly used &amp;ndash; ROOT has a virtual monopoly over LHC physics data analysis, without delivering the sort of &lt;em&gt;quality&lt;/em&gt; that such a position demands.&lt;/p&gt;
</description>
          <pubDate>Mon, 27 Dec 2010 17:28:02 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2010/12/27/its-a-bug-not-a-feature-ren/</guid>
          <link>http://your-web-site.com/articles/2010/12/27/its-a-bug-not-a-feature-ren/</link>
        </item>
    
        <item>
          <title>Back to life</title>
          <description>&lt;p&gt;I&amp;rsquo;ve never been the &lt;em&gt;most&lt;/em&gt; active blogger, but 2 years between posts seems a little excessive, even to me! I wish I could explain the cornucopia of reasons for this, but I&amp;rsquo;ll just point a couple of accusatory fingers at the extraordinary busyness of life (in the intervening time I moved to Edinburgh, the LHC restarted, and my working life has generally been batshit insane) and general frustration at my server setup. You may also be frustrated with the slowness of this server: turns out that running a mail server and a Rails application on a 256 MB virtual server puts me deep into the swap memory zone and site performance accordingly drops into the region marked &amp;ldquo;painful&amp;rdquo;. I&amp;rsquo;d have loved to fix this 2 years ago, but a) I&amp;rsquo;ve written enough web apps in the past to not want to make another half-assed one, and b) did I mention work being batshit insane? Anyhoo, someone asked me at a recent meeting when I was going to start blogging again, and after the initial shock of discovering that I have some sort of niche audience I decided that I should start venting my spleen in more substantial ways than the 140 chars offered by &lt;a href=&quot;http://twitter.com/agbuckley&quot;&gt;Twitter&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A bit of recent server upgrading means that this site is not quite as slow as it has been &amp;ndash; I&amp;rsquo;m &lt;em&gt;enormously&lt;/em&gt; impressed by the service from Slicehost, by the way &amp;ndash; and I&amp;rsquo;m going to try and replace Radiant with something a little more fun, speedy, and memory-efficient in this little pre-2011 gap. Suggestions of CMSes/blog engines with user comments, picture galleries, code highlighting support, etc. &lt;em&gt;and&lt;/em&gt; support for static content (such as this site&amp;rsquo;s &lt;a href=&quot;/projects/nightclimbing&quot;&gt;Cambridge night climbing&lt;/a&gt; content) would be much appreciated. Oh, and because I&amp;rsquo;m a picky person and have not found Ruby/Rails to be a terribly pleasant development experience, being based on Python would also be a big bonus!&lt;/p&gt;
</description>
          <pubDate>Fri, 24 Dec 2010 18:55:57 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2010/12/24/back-to-life/</guid>
          <link>http://your-web-site.com/articles/2010/12/24/back-to-life/</link>
        </item>
    
        <item>
          <title>Removing Beamer nav widgets</title>
          <description>&lt;p&gt;Here&amp;rsquo;s a handy tip for all the people I see giving talks made with the super-genius &lt;a href=&quot;http://latex-beamer.sourceforge.net/&quot;&gt;LaTeX Beamer package&lt;/a&gt;, all of whose slides have a row of never-used navigation widgets (back, forward, start, end, next frame&amp;hellip;) getting in the way of the slide content. It&amp;rsquo;s dead easy to remove them, and then (if you&amp;rsquo;re like me) you can finally sleep at night. Just put this in your Beamer document preamble:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;\mode&amp;lt;presentation&amp;gt; {
  \setbeamertemplate{navigation symbols}{}
}
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Voila &amp;mdash; no more silly nav crap! You will now be the envy of obsessive-compulsive, LaTeX fiend scientists everywhere you go!&lt;/p&gt;
</description>
          <pubDate>Wed, 21 Jan 2009 17:24:06 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2009/01/21/removing-beamer-nav-widgets/</guid>
          <link>http://your-web-site.com/articles/2009/01/21/removing-beamer-nav-widgets/</link>
        </item>
    
        <item>
          <title>A week in the land of contradictions</title>
          <description>&lt;p&gt;It&amp;rsquo;s the end of another busy week. Work life has been busy to the point of insanity recently, burrowing its way into every available bit of spare time&amp;hellip; if you consider every weekend since mid October to be spare time rather than &amp;ldquo;essential time&amp;rdquo;, that is. I&amp;rsquo;m actually inclined to the latter view: while happy to declare that my work is captivating and inspiring, some downtime is definitely needed. In the last month I&amp;rsquo;ve been to two week-long conferences in Italy, snatched a week back in Durham and then spent the last week in Chicago. After one more week in Durham, in which to pay some attention to demonstrating and marking Frank&amp;rsquo;s excellent new &lt;a href=&quot;http://www.ippp.dur.ac.uk/compphys/&quot;&gt;computational physics course&lt;/a&gt;, I&amp;rsquo;m off on my travels again, this time to CERN for a week. And then it&amp;rsquo;s Christmas and skiing; January is looking a bit crazy, and I&amp;rsquo;m trying not to think about that. Fortunately Jo has been a star and given me some (unearned) slack, but this schedule isn&amp;rsquo;t really fair on either of us: I think I&amp;rsquo;ll be imposing a more restricted travel schedule in the New Year and hopefully sending some collaborators out to do the salesman thing instead ;)&lt;/p&gt;

&lt;p&gt;Anyway, reflections on the past week: I have to say, I&amp;rsquo;ve really enjoyed &lt;a href=&quot;http://www.fnal.gov/&quot;&gt;Fermilab&lt;/a&gt;. Most people seem to bitch about the &amp;ldquo;boring site&amp;rdquo;, the strip malls of West Chicago, the weather and anything else that springs to mind, but I must be a bit funny in the head because I like it all. Okay, not the strip malls &amp;mdash; a bit of restriction on the suburban planning process would have been welcome &amp;mdash; but here&amp;rsquo;s a list of hat I&amp;rsquo;ve been up to, other than giving talks and coding up experimental analyses in &lt;a href=&quot;http://projects.hepforge.org/rivet/&quot;&gt;Rivet&lt;/a&gt;:&lt;/p&gt;
</description>
          <pubDate>Sat, 22 Nov 2008 01:08:27 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2008/11/22/a-week-in-the-land-of-contradictions/</guid>
          <link>http://your-web-site.com/articles/2008/11/22/a-week-in-the-land-of-contradictions/</link>
        </item>
    
        <item>
          <title>Burying the hatchet</title>
          <description>&lt;p&gt;&amp;ldquo;Ah, the famous Andy Buckley. Or perhaps infamous, no?&amp;rdquo;. When a dapper French gent at a statistics conference addresses you this way, I guess it&amp;rsquo;s normal to feel a bit perturbed, particularly when you&amp;rsquo;ve devoted a serious chunk of time in the last few years to publicly demonizing their work. Really, I suppose it&amp;rsquo;s maybe a minor miracle that Rene Brun and I haven&amp;rsquo;t crossed paths before now &amp;mdash; although I guess this is largely to do with me being keen to avoid a fight.&lt;/p&gt;
</description>
          <pubDate>Mon, 17 Nov 2008 14:03:55 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2008/11/17/burying-the-hatchet/</guid>
          <link>http://your-web-site.com/articles/2008/11/17/burying-the-hatchet/</link>
        </item>
    
        <item>
          <title>XML: restraining the knee-jerk reflex</title>
          <description>&lt;p&gt;XML is a useful technology, sometimes: that&amp;rsquo;s about as positive as I can be about it these days. While there was a period when I got quite excited about the idea of a standard syntax for, well, everything, time tempers such enthusiasm. See, 90% of the time, XML is just too damn cumbersome. When what you want to say is&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;Param1 = 3
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;or something of that complexity, then having to write&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&amp;lt;param name=&amp;quot;Param1&amp;quot; value=&amp;quot;3&amp;quot;/&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;is just a bit hefty. Anyone who&amp;rsquo;s ever tried using Ant or Maven will surely sympathise with the idea that XML is a pain in the arse way to write make-files. And XSL transforms? Phew, glad I&amp;rsquo;m not going back into that arse-end of software engineering gone mad. It&amp;rsquo;s also a pain in the arse to read XMLified data in C++ or Fortran. Hell, even Python and Java make you jump through SAX or DOM-shaped hoops in their lowest common denominator implementations! Frankly, XML is a serious candidate for &amp;ldquo;no silver bullet&amp;rdquo;-type debunking: merely wrapping everything in angle brackets actually &lt;em&gt;solves nothing&lt;/em&gt;, even if it looks totally SOAP-AJAX-Web 2.0, dude. Much of the time, something simpler is quite enough.&lt;/p&gt;
</description>
          <pubDate>Mon, 10 Nov 2008 21:57:36 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2008/11/10/xml-restraining-the-knee-jerk-reflex/</guid>
          <link>http://your-web-site.com/articles/2008/11/10/xml-restraining-the-knee-jerk-reflex/</link>
        </item>
    
        <item>
          <title>The God Delusion</title>
          <description>&lt;p&gt;I&amp;rsquo;ve recently finished reading Richard Dawkins&amp;rsquo; &lt;em&gt;The God Delusion&lt;/em&gt;. I was pretty determined to not read it when it first came out since a) I object to specifically indulging in writing that I know I&amp;rsquo;ll agree with &amp;mdash; I suspect that searching out compliant opinions leads to foam-mouthed Daily Mail reader behaviour and obstinate old man disease, and b) Herr Dawkins has been on a bit of an ego/PR trip in recent years, in an area which he&amp;rsquo;s not really all that qualified to talk about. But then, as he points out in the book, it&amp;rsquo;s not like religious &amp;ldquo;authorities&amp;rdquo; are really qualified to say anything meaningful about well&amp;hellip; anything, so when Jo got a copy, I decided to steal it and finish it before her ;)&lt;/p&gt;
</description>
          <pubDate>Sun, 09 Nov 2008 23:17:16 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2008/11/09/the-god-delusion/</guid>
          <link>http://your-web-site.com/articles/2008/11/09/the-god-delusion/</link>
        </item>
    
        <item>
          <title>Bundling LaTeX for arXiv submission</title>
          <description>&lt;p&gt;I always have trouble submitting papers to the &lt;a href=&quot;http://www.arxiv.org&quot;&gt;arXiv&lt;/a&gt;, on account of my tendancy to use a whole bunch of style files etc. that aren&amp;rsquo;t in the standard arXiv collection. They aren&amp;rsquo;t usually in my document source directory, either, but are spread around my system in various &lt;code&gt;texmf&lt;/code&gt; trees. Accordingly, getting papers to upload is a pain (and if you try to upload just a PDF, arXiv detects that the PDF was made with TeX and refuses to accept it! Dang, foiled!)&lt;/p&gt;

&lt;p&gt;So here&amp;rsquo;s the method that seems to work for me.&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Get the &lt;a href=&quot;http://www.ctan.org/tex-archive/macros/latex/contrib/snapshot/&quot;&gt;&lt;code&gt;snapshot&lt;/code&gt;&lt;/a&gt; package, and use it in your document with the usual &lt;code&gt;\usepackage{snapshot}&lt;/code&gt;&lt;/li&gt;
  &lt;li&gt;Run &lt;code&gt;latex&lt;/code&gt; etc. on your document until it&amp;rsquo;s happy (note, I use &lt;code&gt;pdflatex&lt;/code&gt; pretty much exclusively these days, but arXiv will use good o&amp;rsquo; DVI-producing &lt;code&gt;latex&lt;/code&gt;, so that&amp;rsquo;s what you need to use when producing your submission)&lt;/li&gt;
  &lt;li&gt;If your document was called &lt;code&gt;mydoc.tex&lt;/code&gt;, you will now have a dependencies file, &lt;code&gt;mydoc.dep&lt;/code&gt;. This can be used to bundle your source files for submission. To do this, get &lt;a href=&quot;http://www.ctan.org/tex-archive/support/bundledoc/&quot;&gt;&lt;code&gt;bundledoc&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
  &lt;li&gt;Run bundledoc on the deps file &amp;mdash; you may need to provide an explicit config file. Here&amp;rsquo;s my command: &lt;code&gt;bundledoc --config=$HOME/local/texmf/tex/latex/bundledoc/tetex.cfg mydoc.dep&lt;/code&gt;&lt;/li&gt;
  &lt;li&gt;You now have a tarball or zip archive, depending on whether you used the TeTeX/TeX Live or MikTeX config file. This should be okay for uploading to arXiv. Happy bundling.&lt;/li&gt;
&lt;/ol&gt;
</description>
          <pubDate>Fri, 26 Sep 2008 16:12:11 GMT</pubDate>
          <guid>http://your-web-site.com/articles/2008/09/26/bundling-latex-for-arxiv-submission/</guid>
          <link>http://your-web-site.com/articles/2008/09/26/bundling-latex-for-arxiv-submission/</link>
        </item>
    
    
  </channel>
</rss>

