<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: More on Speleothem Dating</title>
	<atom:link href="http://climateaudit.org/2008/12/14/more-on-speleothem-dating/feed/" rel="self" type="application/rss+xml" />
	<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/</link>
	<description>by Steve McIntyre</description>
	<lastBuildDate>Tue, 21 May 2013 15:32:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Geoff Sherrington</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169906</link>
		<dc:creator><![CDATA[Geoff Sherrington]]></dc:creator>
		<pubDate>Tue, 23 Dec 2008 01:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169906</guid>
		<description><![CDATA[Re: &lt;a href=&quot;#comment-316619&quot; rel=&quot;nofollow&quot;&gt;Chris H (#20)&lt;/a&gt;,

Thank you Chris H. Both approaches are possible. My inquiry was to catch up with modern approaches. There is a particular case, seen for example with the several peaks commonly arising from isotope dilution in U work where one of the abundances is much, much less than others and so sets the error, as you noted in another way.]]></description>
		<content:encoded><![CDATA[<p>Re: <a href="#comment-316619" rel="nofollow">Chris H (#20)</a>,</p>
<p>Thank you Chris H. Both approaches are possible. My inquiry was to catch up with modern approaches. There is a particular case, seen for example with the several peaks commonly arising from isotope dilution in U work where one of the abundances is much, much less than others and so sets the error, as you noted in another way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris H</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169905</link>
		<dc:creator><![CDATA[Chris H]]></dc:creator>
		<pubDate>Mon, 22 Dec 2008 03:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169905</guid>
		<description><![CDATA[Re: &lt;a href=&quot;#comment-316597&quot; rel=&quot;nofollow&quot;&gt;Geoff Sherrington (#19)&lt;/a&gt;, Both approaches are used. In the multiple-collector world, the canned control software tends to calculate ratios. These ratios are averaged over time and they are invariably treated as independent. However, strictly speaking they aren&#039;t as usually there is a shared peak measurement. One should attempt to estimate the covariance of the ratios, but I doubt if this is normally done. From the mass spec software I&#039;ve seen, any covariance is assumed to be zero. Of course, one can get around this by putting the best determined isotope in the denominator, which will minimize the correlation. In contrast, with noble gas machines (e.g. argon dating), which usually peak hop, one has to extrapolate peaks to gas inlet time (the isotopes get pumped by the machine itself during measurement). So each isotope tends to be treated as a separate measurement and they are essentially independent. However, one can then calculate the covariance expected in the ratio error estimates and this is normally done. At least I do it. ;-)]]></description>
		<content:encoded><![CDATA[<p>Re: <a href="#comment-316597" rel="nofollow">Geoff Sherrington (#19)</a>, Both approaches are used. In the multiple-collector world, the canned control software tends to calculate ratios. These ratios are averaged over time and they are invariably treated as independent. However, strictly speaking they aren&#8217;t as usually there is a shared peak measurement. One should attempt to estimate the covariance of the ratios, but I doubt if this is normally done. From the mass spec software I&#8217;ve seen, any covariance is assumed to be zero. Of course, one can get around this by putting the best determined isotope in the denominator, which will minimize the correlation. In contrast, with noble gas machines (e.g. argon dating), which usually peak hop, one has to extrapolate peaks to gas inlet time (the isotopes get pumped by the machine itself during measurement). So each isotope tends to be treated as a separate measurement and they are essentially independent. However, one can then calculate the covariance expected in the ratio error estimates and this is normally done. At least I do it. <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Sherrington</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169904</link>
		<dc:creator><![CDATA[Geoff Sherrington]]></dc:creator>
		<pubDate>Mon, 22 Dec 2008 00:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169904</guid>
		<description><![CDATA[Quick question. If one uses an isotopic ratio (like from a mass spectrometer, measured at the same instant) of say U234 to  U238, there will be instrumental errors with each isotope and so errors with the ratios. Is it permitted maths to treat the ratio as a single figure and to do customary statistics on a set of ratios, or does the error of each isotope have to be carried through separately to arrive at total error?]]></description>
		<content:encoded><![CDATA[<p>Quick question. If one uses an isotopic ratio (like from a mass spectrometer, measured at the same instant) of say U234 to  U238, there will be instrumental errors with each isotope and so errors with the ratios. Is it permitted maths to treat the ratio as a single figure and to do customary statistics on a set of ratios, or does the error of each isotope have to be carried through separately to arrive at total error?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris H</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169903</link>
		<dc:creator><![CDATA[Chris H]]></dc:creator>
		<pubDate>Thu, 18 Dec 2008 15:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169903</guid>
		<description><![CDATA[Re: &lt;a href=&quot;#comment-316018&quot; rel=&quot;nofollow&quot;&gt;Alan Wilkinson (#15)&lt;/a&gt;, Yes, that&#039;s what I&#039;m talking about. The top equation above is a bit like a highly constrained line fit to a single point. Because of the constraints, you can&#039;t just put any line through the single data point. Now let x=238U/234U and y=230Th/234U. Both the slope and intercept depend on the age t. The way I would approach this (I&#039;m not a U-series person but an Ar-Ar dater), I would set up a minimization where we have to find not only t but also x(true) and y(true). x(true) and y(true) are exactly constrained to fit the top equation. Now, assuming that sigma(x) and sigma(y) are uncorrelated (we don&#039;t have correlation info, and if they are correlated, it gets more complicated - like fitting a straight line through points with x and y errors and the errors are correlated), then you want to find x(true), y(true) and t such that ((x(meas)-x(true))/sigma(x))^2+((y(meas)-y(true))/sigma(y))^2 is minimized. The assumption of independence is equivalent to assuming that the error ellipse is aligned with the axes. Correlation tilts the error ellipse. This is graphically like finding t such that the error ellipse around the measured x and y isotope ratios is as small as possible when expanded to just touch the line. Now, one can probably do this in R, but most people in the biz would likely just get Ken Ludwig&#039;s Isoplot public domain software (see http://www.bgc.org/isoplot_etc/software.html) over at the Berkeley Geochronology Center (BGC). I don&#039;t use it myself as I tend to write my own software, but I&#039;m pretty sure he has the whole thing worked out.]]></description>
		<content:encoded><![CDATA[<p>Re: <a href="#comment-316018" rel="nofollow">Alan Wilkinson (#15)</a>, Yes, that&#8217;s what I&#8217;m talking about. The top equation above is a bit like a highly constrained line fit to a single point. Because of the constraints, you can&#8217;t just put any line through the single data point. Now let x=238U/234U and y=230Th/234U. Both the slope and intercept depend on the age t. The way I would approach this (I&#8217;m not a U-series person but an Ar-Ar dater), I would set up a minimization where we have to find not only t but also x(true) and y(true). x(true) and y(true) are exactly constrained to fit the top equation. Now, assuming that sigma(x) and sigma(y) are uncorrelated (we don&#8217;t have correlation info, and if they are correlated, it gets more complicated &#8211; like fitting a straight line through points with x and y errors and the errors are correlated), then you want to find x(true), y(true) and t such that ((x(meas)-x(true))/sigma(x))^2+((y(meas)-y(true))/sigma(y))^2 is minimized. The assumption of independence is equivalent to assuming that the error ellipse is aligned with the axes. Correlation tilts the error ellipse. This is graphically like finding t such that the error ellipse around the measured x and y isotope ratios is as small as possible when expanded to just touch the line. Now, one can probably do this in R, but most people in the biz would likely just get Ken Ludwig&#8217;s Isoplot public domain software (see <a href="http://www.bgc.org/isoplot_etc/software.html" rel="nofollow">http://www.bgc.org/isoplot_etc/software.html</a>) over at the Berkeley Geochronology Center (BGC). I don&#8217;t use it myself as I tend to write my own software, but I&#8217;m pretty sure he has the whole thing worked out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven mosher</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169902</link>
		<dc:creator><![CDATA[steven mosher]]></dc:creator>
		<pubDate>Thu, 18 Dec 2008 04:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169902</guid>
		<description><![CDATA[RE 16. Sharing source is like showering with other men. Some of us have no problem whatsoever, other&#039;s are rightly ashamed.]]></description>
		<content:encoded><![CDATA[<p>RE 16. Sharing source is like showering with other men. Some of us have no problem whatsoever, other&#8217;s are rightly ashamed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169901</link>
		<dc:creator><![CDATA[Kevin]]></dc:creator>
		<pubDate>Wed, 17 Dec 2008 17:28:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169901</guid>
		<description><![CDATA[I see it all the time in industrial engineering.

1) Results don&#039;t correlate, send your test setup.


2) I can do that here. Send me your program.


3) Something funny seems to be happening, send your code.


4) I can&#039;t see the function I want to look at, send me uncompiled code.


5) Please send me uncompiled code soon.


I don&#039;t attribute it to deceit. Instead: hiding untidy code, or hiding issues unrelated to the point of contention, or the &quot;author&quot; never studied the code either but inherited or harvested it.

Even happens between people working for the same company at the same location. Sharing software can be a sensetive subject.]]></description>
		<content:encoded><![CDATA[<p>I see it all the time in industrial engineering.</p>
<p>1) Results don&#8217;t correlate, send your test setup.</p>
<p>2) I can do that here. Send me your program.</p>
<p>3) Something funny seems to be happening, send your code.</p>
<p>4) I can&#8217;t see the function I want to look at, send me uncompiled code.</p>
<p>5) Please send me uncompiled code soon.</p>
<p>I don&#8217;t attribute it to deceit. Instead: hiding untidy code, or hiding issues unrelated to the point of contention, or the &#8220;author&#8221; never studied the code either but inherited or harvested it.</p>
<p>Even happens between people working for the same company at the same location. Sharing software can be a sensetive subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Wilkinson</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169900</link>
		<dc:creator><![CDATA[Alan Wilkinson]]></dc:creator>
		<pubDate>Wed, 17 Dec 2008 09:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169900</guid>
		<description><![CDATA[Re: &lt;a href=&quot;#comment-315919&quot; rel=&quot;nofollow&quot;&gt;Steve McIntyre (#11)&lt;/a&gt;,

Chris H is talking data point weighting, not errors or confidence levels of the derived parameter estimates?

He is right that these must be applied if significantly unequal.]]></description>
		<content:encoded><![CDATA[<p>Re: <a href="#comment-315919" rel="nofollow">Steve McIntyre (#11)</a>,</p>
<p>Chris H is talking data point weighting, not errors or confidence levels of the derived parameter estimates?</p>
<p>He is right that these must be applied if significantly unequal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris H</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169899</link>
		<dc:creator><![CDATA[Chris H]]></dc:creator>
		<pubDate>Tue, 16 Dec 2008 22:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169899</guid>
		<description><![CDATA[#11: In the words of the the Mythbusters when looking at a blown up car &quot;well there&#039;s your problem&quot; (possibly). When you use the nonlinear optimization routine, it should be a weighted optimization where you minimize the chi-squared value. That will be calculated as ((the model isotope ratio minus the measured ratio)/(1 sigma measurement error))^2. Sum over all fitted isotope ratios. Please excuse the meta formula, but I think you&#039;ll get the drift.]]></description>
		<content:encoded><![CDATA[<p>#11: In the words of the the Mythbusters when looking at a blown up car &#8220;well there&#8217;s your problem&#8221; (possibly). When you use the nonlinear optimization routine, it should be a weighted optimization where you minimize the chi-squared value. That will be calculated as ((the model isotope ratio minus the measured ratio)/(1 sigma measurement error))^2. Sum over all fitted isotope ratios. Please excuse the meta formula, but I think you&#8217;ll get the drift.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. F. Linton</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169898</link>
		<dc:creator><![CDATA[D. F. Linton]]></dc:creator>
		<pubDate>Tue, 16 Dec 2008 19:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169898</guid>
		<description><![CDATA[#9.  I think you now have the adjustment equation correct.  I changed mine to match but I haven&#039;t had any luck replicating the BN6 values.  I fell back to a simple check of the measured and corrected 234U to 238U ratio columns.  These are related by equation (2).  If you solve (2) for lambda_234 and plug in those values and the corresponding ages you get implied lambda_234 values ranging from 2.8274e-6 to 2.8423e-6.  The mean of these implied lambda values is 2.8353e-6.  I think that one problem in replicating Table 1 comes from the limited precision of the values given.  If you use the given value for lambda_234 and compute the implied ages, you get, for lines 3 to the end:


      Frank Age   Computed Age  Difference
      105600      105871        -271
      107500      107517         -17
      105500      105444          56
      102200      102249         -49
      105400      105118         282
      105600      105591           9
      104600      104590          10
      106800      106776          24
       93600       93569          31
      118300      118153         147
      111200      111109          91
       98600       98842        -242
      114500      114402          98
       97700       97620          80
      105300      105354         -54
      101900      101973         -73
      101900      102005        -105
      108400      108574        -174
      116400      116302          98
      114300      114380         -80

Given the exponentials, t might be quite sensitive to precision uncertainties.]]></description>
		<content:encoded><![CDATA[<p>#9.  I think you now have the adjustment equation correct.  I changed mine to match but I haven&#8217;t had any luck replicating the BN6 values.  I fell back to a simple check of the measured and corrected 234U to 238U ratio columns.  These are related by equation (2).  If you solve (2) for lambda_234 and plug in those values and the corresponding ages you get implied lambda_234 values ranging from 2.8274e-6 to 2.8423e-6.  The mean of these implied lambda values is 2.8353e-6.  I think that one problem in replicating Table 1 comes from the limited precision of the values given.  If you use the given value for lambda_234 and compute the implied ages, you get, for lines 3 to the end:</p>
<p>      Frank Age   Computed Age  Difference<br />
      105600      105871        -271<br />
      107500      107517         -17<br />
      105500      105444          56<br />
      102200      102249         -49<br />
      105400      105118         282<br />
      105600      105591           9<br />
      104600      104590          10<br />
      106800      106776          24<br />
       93600       93569          31<br />
      118300      118153         147<br />
      111200      111109          91<br />
       98600       98842        -242<br />
      114500      114402          98<br />
       97700       97620          80<br />
      105300      105354         -54<br />
      101900      101973         -73<br />
      101900      102005        -105<br />
      108400      108574        -174<br />
      116400      116302          98<br />
      114300      114380         -80</p>
<p>Given the exponentials, t might be quite sensitive to precision uncertainties.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Davis</title>
		<link>http://climateaudit.org/2008/12/14/more-on-speleothem-dating/#comment-169897</link>
		<dc:creator><![CDATA[Mike Davis]]></dc:creator>
		<pubDate>Tue, 16 Dec 2008 18:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=4672#comment-169897</guid>
		<description><![CDATA[Replicating methods: using a hat put 20 of each number from 0 thru 9 in hat. Then begin pulling numbers out one by one. What can I say? It has worked for me in the past.]]></description>
		<content:encoded><![CDATA[<p>Replicating methods: using a hat put 20 of each number from 0 thru 9 in hat. Then begin pulling numbers out one by one. What can I say? It has worked for me in the past.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
