Musings on Climategate

CRU code: You gotta be kidding!

Posted in AGW Political, AGW Rhetorical by emelks on December 9, 2009

This module is in the documents\cru-code\linux\mod directory. Apparently, this module allows the user to manually specify “forcing” and “climate sensitivity” to run through the computations.

Forgive me if I’m slow but isn’t that what these “models” are supposed to do?

Any insight would be greatly appreciated.

! pattscale.f90
! module procedure written by Tim Mitchell
! includes subroutines necessary for pattern scaling to equilibrium

module PattScale

implicit none



subroutine GetKaySet (KaySet,Forc2co2,FitAlpha,FitBeta,Sens2co2Init,TrendTLen)

real, intent(out) :: Forc2co2,FitAlpha,FitBeta,Sens2co2Init

integer, intent(in) :: KaySet ! may be MissVal or zero or >=1
integer, intent(out) :: TrendTLen

real, parameter :: MissVal = -999.0

integer :: AllocStat,ReadStatus
integer :: QKaySet


if (KaySet.EQ. 0) then ! allow selection of QKaySet if required
print*, ” > These are the available sets of constants: ”
print*, ” > 1 : 3.47, 1.3388, -96.613, 1.9, 100″
read (*,*,iostat=ReadStatus), QKaySet
if (ReadStatus.LE.0.AND.QKaySet.GE.1.AND.QKaySet.LE.1) exit
end do
QKaySet = KaySet
end if

Okay, so the module displays on the screen five constants and tells the user to select one. I’ve not yet found the KaySet file, but it seems a bit odd that the program is allowing the user to select these values.

if (QKaySet.EQ. 1) then ! allow designation of constants if possible
Forc2co2=3.47 ; FitAlpha=1.3388 ; FitBeta=-96.613 ; Sens2co2Init=1.9 ; TrendTLen=100
QKaySet = MissVal
end if

if (KaySet.EQ.MissVal) then ! designate constants individually
print*, ” > Enter the radiative forcing for a doubling of CO2: ”
read (*,*,iostat=ReadStatus), Forc2co2
if (ReadStatus.LE.0.AND.Forc2co2.GT.0) exit
end do

WHAT??? They’re having the user enter the value for radiative forcing? Isn’t that supposed to be a variable determined by the model???

print*, ” > Enter the alpha and beta parameters for dS/dT=alpha*e(beta*dT/dt): ”
read (*,*,iostat=ReadStatus), FitAlpha, FitBeta
if (ReadStatus.LE.0) exit
end do

print*, ” > Enter the initial climate sensitivity for a doubling of CO2: “

Once again, WHAT?????? How is this determined? Since it’s a user-specified value, where does the user get the appropriate value to enter?

read (*,*,iostat=ReadStatus), Sens2co2Init
if (ReadStatus.LE.0.AND.Sens2co2Init.GT.0) exit
end do
print*, ” > Enter the period length over which to calc dT/dt: ”
read (*,*,iostat=ReadStatus), TrendTLen
if (ReadStatus.LE.0.AND.TrendTLen.GT.0) exit
end do
end if

end subroutine GetKaySet

end module PattScale

And then I see, in documents\yamal\sf2.txt:

Dear Keith.

Stepan Shiyatov said me you need only data covered last 2 millenium. Now I send data of 35 samples covered earlier millenium. These are all samples concerning this period and they are checked (there are about 130 more samples from 0 to 1800 AD not checked at this time). I hope your desire to see low growth about 350 BC will be more or less satisfied. However for some reason there are no good correlation between number of samples and growth rate. For instance, about 700 BC provided by only one sample with very high growth during just this period. I don’t know why, may be number of trees depends on burial conditions as well.

I have to note that 364 BC (not 360 BC as I wrote before) on sample No. 60 slightly looks like false. On sample 453 it is normal ring, on other sample it is very small. Therefore I can’t still say something definitely.

Best wishes,
Rashit Hantemirov

” I hope your desire to see low growth about 350 BC will be more or less satisfied”???? I’m guessing that low growth = low temperature in CRUland, and if that’s the case is the emailer hoping that the data proves to be of Keith’s liking? And what’s the deal with more samples isn’t turning into the desired growth rate? It sounds a lot like cherrypicking to me.

I understand those who are struggling to find any way to justify what is contained in the .zip file. Some say that the above code is meaningless unless proven to have been used in a publically distributed document. Others say the email is irrelevant. But taken together, it’s irrefutable that this group has been, and still is, attempting to defraud the people of the world using garbage data.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: