<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Articles on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/tag/articles/</link><description>Recent content in Articles on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/tag/articles/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Carpentry article in CiSE</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/11/software-carpentry-article-in-cise/</link><pubDate>Tue, 28 Nov 2006 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/11/software-carpentry-article-in-cise/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>The November 2006 issue of
&lt;a href="http://cise.aip.org/">&lt;em>Computing in Science and Engineering&lt;/em>&lt;/a>
includes an article I wrote titled "Software
Carpentry: Getting Scientists to Write Better Code by making Them More
Productive". It's available to subscribers only on the magazine's web
site, but they have kindly given me permission to post
it &lt;a href="{{site.baseurl}}/files/bib/amsci-swc-2006.pdf">here&lt;/a>.
I think it's out too late to bring
November's stats up above October's, but I could be surprised.&lt;/p></description></item><item><title>Computational Result Retracted</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/10/computational-result-retracted/</link><pubDate>Tue, 31 Oct 2006 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/10/computational-result-retracted/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>From the latest &lt;cite>Nature&lt;/cite> (Vol 443, No 7114, p 1013):&lt;/p>
&lt;blockquote>&lt;p>When a new, independent code is used for the calculations on which the conclusions of this Letter were based, the results reported for the evolution of obliquity cannot be reproduced. This code was written in the inertial frame and is more reliable than the one used in the Letter. In most runs, the obliquities can change by only a few degrees and attain large values in only a very few cases. In addition, the obliquity variation shown in the Supplementary Information, although correct, originates from changes to orbital inclination of the planet, and close encounters are not effective in causing large obliquities.&lt;/p></description></item><item><title>German Version of 'Bottleneck'</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/10/german-version-of-bottleneck/</link><pubDate>Thu, 26 Oct 2006 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/10/german-version-of-bottleneck/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>A German version of my article "&lt;a href="http://www.americanscientist.org/template/AssetDetail/assetid/48548">Where's the Real Bottleneck in Scientific Computing?&lt;/a>" has just appeared in &lt;a href="http://www.spektrum.de/artikel/852747">Spektrum&lt;/a> magazine. Pay-per-view, unfortunately, but the Software Carpentry site has had a flurry of hits from .de domains.&lt;/p>
&lt;p>Dec 1: I just received my copy in the mail&amp;mdash;I sound so much...sterner...in German ;-)&lt;/p>
&lt;blockquote>&lt;p>Gregory V. Wilson ist Professor f&amp;uuml;r Computerwissenschaft an der University of Toronto. Sein Kurs ist erh&amp;auml;ltlich unter www.swc.scipy.org/.&lt;/p></description></item><item><title>Design Patterns in Scientific Software</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/07/design-patterns-in-scientific-software/</link><pubDate>Sun, 30 Jul 2006 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/07/design-patterns-in-scientific-software/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>&lt;a href="http://www.cse.nd.edu/Reports/2004/TR-2004-29.pdf">This paper&lt;/a>, via the &lt;a href="http://www.openscience.org">OpenScience Projec&lt;/a>t, is a couple of years old, but a good step in an interesting direction.&lt;/p></description></item><item><title>Data Lineage</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/02/data-lineage/</link><pubDate>Tue, 14 Feb 2006 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2006/02/data-lineage/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>The January 2005 issue of ACM Computing Surveys (vol. 37, no. 1, if you prefer) has good review by Rajendra Bose and James Frew titled "Lineage Retrieval for Scientific Data Processing: A Survey". In it, they look at what scientists do to keep track of what data they have, where it came from, and what has been done to it. Some of my students last term were worrying about the same issues in the context of &lt;a href="http://www.hl7.ca">HL7&lt;/a> medical data. It seems like an ideal place for software engineers to apply their skills: I'd be interested in hearing from people who have home-grown or small-scale systems I could use as a starting point for a lecture in &lt;a href="http://www.software-carpentry.org">Software Carpentry&lt;/a>.&lt;/p></description></item></channel></rss>