<?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: MBH98 Source Code: Status Report</title>
	<atom:link href="http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/</link>
	<description>by Steve McIntyre</description>
	<lastBuildDate>Fri, 24 May 2013 06:52:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Sam Urbinto</title>
		<link>http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/#comment-35256</link>
		<dc:creator><![CDATA[Sam Urbinto]]></dc:creator>
		<pubDate>Wed, 07 Nov 2007 17:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=289#comment-35256</guid>
		<description><![CDATA[Mann&#039;s code:  Based on a question from Steve and what Jimmy Smith said and steven mosher said, I&#039;m bumping this one.  Have at it gents.]]></description>
		<content:encoded><![CDATA[<p>Mann&#8217;s code:  Based on a question from Steve and what Jimmy Smith said and steven mosher said, I&#8217;m bumping this one.  Have at it gents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Mitroy</title>
		<link>http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/#comment-35255</link>
		<dc:creator><![CDATA[Jim Mitroy]]></dc:creator>
		<pubDate>Mon, 08 Aug 2005 09:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=289#comment-35255</guid>
		<description><![CDATA[The ftnchek program is designed to check the syntax of program
vs strict fortran standards.  So programs which fail the checks
can potentially give different results depending on the
compiler/CPU mix.

Uninitialized variables are usually set to zero, and most
compilers do have an option to enforce this.  But, the people
who write programs with unitialized variables generally do
not bother fiddling with compiler options.

The 470 or so such mixed REAL*4/REAL*8 mode expressions
mean the program is more susceptible to round-off error
creeping in and possibly polluting the quality of any
computation.  I noticed that the code had an SVD in there,
if I was doing an SVD I would generally like to maintain
the integrity of all the 15 digits of REAL*8.  It should
be noted that there are compilers with options that can
force everything to be REAL*8.

For the record, I like to know what is happening to all
15 digits of my floating point numbers as I add, subtract,
multiply and divide them.  Mixed-mode arithemetic and/or
unitialized variables do not constitute good programming
practice.

Jim Mitroy]]></description>
		<content:encoded><![CDATA[<p>The ftnchek program is designed to check the syntax of program<br />
vs strict fortran standards.  So programs which fail the checks<br />
can potentially give different results depending on the<br />
compiler/CPU mix.</p>
<p>Uninitialized variables are usually set to zero, and most<br />
compilers do have an option to enforce this.  But, the people<br />
who write programs with unitialized variables generally do<br />
not bother fiddling with compiler options.</p>
<p>The 470 or so such mixed REAL*4/REAL*8 mode expressions<br />
mean the program is more susceptible to round-off error<br />
creeping in and possibly polluting the quality of any<br />
computation.  I noticed that the code had an SVD in there,<br />
if I was doing an SVD I would generally like to maintain<br />
the integrity of all the 15 digits of REAL*8.  It should<br />
be noted that there are compilers with options that can<br />
force everything to be REAL*8.</p>
<p>For the record, I like to know what is happening to all<br />
15 digits of my floating point numbers as I add, subtract,<br />
multiply and divide them.  Mixed-mode arithemetic and/or<br />
unitialized variables do not constitute good programming<br />
practice.</p>
<p>Jim Mitroy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Mitroy</title>
		<link>http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/#comment-35254</link>
		<dc:creator><![CDATA[Jim Mitroy]]></dc:creator>
		<pubDate>Sun, 07 Aug 2005 03:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=289#comment-35254</guid>
		<description><![CDATA[Since the economy of the free world apparently depends on the
hockey stick I decided to run the code through the the FORTRAN
syntax checker ftnchek.

There were close to 100 screen fulls of warnings concerning
mixed mode (mainly REAL*4/REAL*8) arithmetic.  The tail-end
of the output is enclosed below.

This is what I got

..............................................................
..............................................................
Warning near line 2960 col 13 file multiproxy.f: real G
promoted to real*8 S: may not give desired precision
   3012 570   RETURN
Error near line 3012 file multiproxy.f: missing END statement
inserted at end of file

 2 syntax errors detected in file multiproxy.f
 476 warnings issued in file multiproxy.f

Warning: Subprogram CSVD argument usage mismatch at position 6:
Dummy arg IP in module CSVD line 2749 file multiproxy.f is used before set
Actual arg IP0 in module %MAIN line 1138 file multiproxy.f is not set

**************************  END ftnchek output ********************

I really would be happier if decisions concerning the future of
the world economy did not depend on whether the compiler sets
unitialized variables to zero.

&lt;strong&gt;Steve:&lt;/strong&gt; Could some of the diagnostics be compiler-specific? He&#039;s  produced results, so at some level I presume that his program must at least compile.]]></description>
		<content:encoded><![CDATA[<p>Since the economy of the free world apparently depends on the<br />
hockey stick I decided to run the code through the the FORTRAN<br />
syntax checker ftnchek.</p>
<p>There were close to 100 screen fulls of warnings concerning<br />
mixed mode (mainly REAL*4/REAL*8) arithmetic.  The tail-end<br />
of the output is enclosed below.</p>
<p>This is what I got</p>
<p>&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..<br />
&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..<br />
Warning near line 2960 col 13 file multiproxy.f: real G<br />
promoted to real*8 S: may not give desired precision<br />
   3012 570   RETURN<br />
Error near line 3012 file multiproxy.f: missing END statement<br />
inserted at end of file</p>
<p> 2 syntax errors detected in file multiproxy.f<br />
 476 warnings issued in file multiproxy.f</p>
<p>Warning: Subprogram CSVD argument usage mismatch at position 6:<br />
Dummy arg IP in module CSVD line 2749 file multiproxy.f is used before set<br />
Actual arg IP0 in module %MAIN line 1138 file multiproxy.f is not set</p>
<p>**************************  END ftnchek output ********************</p>
<p>I really would be happier if decisions concerning the future of<br />
the world economy did not depend on whether the compiler sets<br />
unitialized variables to zero.</p>
<p><strong>Steve:</strong> Could some of the diagnostics be compiler-specific? He&#8217;s  produced results, so at some level I presume that his program must at least compile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Huldén</title>
		<link>http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/#comment-35253</link>
		<dc:creator><![CDATA[Larry Huldén]]></dc:creator>
		<pubDate>Wed, 03 Aug 2005 05:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=289#comment-35253</guid>
		<description><![CDATA[Is it possible that Mann originally believed in his hookey stick that much that he made the calculations quickly to get the results published and expected that they would be more thoroughly verified later? Because nobody has later been able to verify what he did he doesn&#039;t dare to disclose everything because the original reconstruction was not properly done. I feel pretty sure that he will never disclose completely the methods and data used in MBH98 &amp; 99.]]></description>
		<content:encoded><![CDATA[<p>Is it possible that Mann originally believed in his hookey stick that much that he made the calculations quickly to get the results published and expected that they would be more thoroughly verified later? Because nobody has later been able to verify what he did he doesn&#8217;t dare to disclose everything because the original reconstruction was not properly done. I feel pretty sure that he will never disclose completely the methods and data used in MBH98 &amp; 99.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fFreddy</title>
		<link>http://climateaudit.org/2005/08/02/mbh98-source-code-status-report/#comment-35252</link>
		<dc:creator><![CDATA[fFreddy]]></dc:creator>
		<pubDate>Tue, 02 Aug 2005 15:21:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.climateaudit.org/?p=289#comment-35252</guid>
		<description><![CDATA[Steve, the link to the lexicon is bust.  &lt;strong&gt;Steve:&lt;/strong&gt; Fixed.]]></description>
		<content:encoded><![CDATA[<p>Steve, the link to the lexicon is bust.  <strong>Steve:</strong> Fixed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
