Parliament To Discuss CRU - FUSAG In East Anglia
Posted: Fri Jan 22, 2010 9:16 pm
a discussion forum for Polywell fusion
https://www.talk-polywell.org/bb/
Some times big endian vs little endian can make a difference.Anyone who has actually done complex research simulations and data handling knows full-well that one can induce subtelties in the results by nominally irrelevant variations in method, and even the type of computer can make a difference (try running any simulations requiring >a million steps on a 32 bit and 64 bit versions of the same software, and you'll see what I mean!).
In support of this, even if the data preprocessing and model file are disclosed, the software to run these is still a black-box, and can't be analysed due to closed source "proprietary" methods - ie someone has fenced an area to make a buck. This is a vote for a requirement of open source software in scientific research. However it does take resources to produce good software.chrismb wrote:It's been a bug bear of mine dating way back into other fields. When I was a Research Fellow 10 years ago I became very disillusioned with the way the 'research industry' had started treating simulations like black-box devices no more complicated than using a calibrated ruler, and thus with, effectively, almost non-existant disclosure of how a simulation was actually done [wherein papers were getting to the point of essentially saying "and software xyx.1 was used, as shown in the graph of diagram 1; conclusions, data set and xyz.1 simulations matched, so data set proved!..."].
A 'piece of research' must be able to be reproduced by someone else, and if it can't then it is of no academic use. So if some means has been adopted to control the flow of data into a simulation in a certain way [which is not unreasonable in itself, as long as it is clearly explained], this must be fully disclosed, else the result would not be repeatable.
If I ever found a case like that I'd strongly suspect a bug in the code.MSimon wrote:Some times big endian vs little endian can make a difference.
Yes. If the data is output to your file (tape - memory stick - etc.) is big endian and the next computer to use it is little endian there is a bug if the answers are unreal.hanelyp wrote:If I ever found a case like that I'd strongly suspect a bug in the code.MSimon wrote:Some times big endian vs little endian can make a difference.
Regarding 'open source' for simulation software: The source being open for study and criticism is vital for healthy science. Source covered by a 'copyleft' license is nice and useful, but not so vital.
This problem is effectively non-existent with competent programmers. The data formats are all ASCII anyway, text files. Very simple CSV or fixed width formats. Extraordinarily simple to read and parse.MSimon wrote:Yes. If the data is output to your file (tape - memory stick - etc.) is big endian and the next computer to use it is little endian there is a bug if the answers are unreal.
Ian "Harry" Harris says the climate stuff was not done by competent programmers.competent programmers
http://www.anenglishmanscastle.com/HARRY_READ_ME.txtAs another pundit said: this isn’t just the smoking gun pointing to the fraud of global warming, it’s a mushroom cloud!
From a commenter at Flopping Aces:…The file — 274 pages long — describes the efforts of a climatologist/programmer at the Climatic Research Unit (CRU) of the University of East Anglia to update a huge statistical database (11,000 files) of important climate data between 2006 and 2009.
The computer coding, along with the programmer’s apparently unsuccessful efforts to complete the project, involve data that are the foundation of the study of climate change — recordings from hundreds of weather stations around the world of temperature and precipitation measurements from 1901 to 2006, sun/cloud computer simulations, and the like.
…
The CRU at East Anglia University is considered by many as the world’s leading climate research agency. Here’s how CBSNews.com…’s Declan McCullagh describes its enormous impact on policymakers:
“In global warming circles, the CRU wields outsize influence: It claims the world’s largest temperature data set, and its work and mathematical models were incorporated into the United Nations Intergovernmental Panel on Climate Change’s 2007 report. The report … is what the Environmental Protection Agency acknowledged it ‘relies on most heavily’ when concluding carbon dioxide emissions endanger public health and should be regulated.”
As you read the programmer’s comments below, remember, this is only a fraction of what he says.
- “But what are all those monthly files? DON’T KNOW, UNDOCUMENTED. Wherever I look, there are data files, no info about what they are other than their names. And that’s useless …” (Page 17)
- “It’s botch after botch after botch.” (18)
- “The biggest immediate problem was the loss of an hour’s edits to the program, when the network died … no explanation from anyone, I hope it’s not a return to last year’s troubles … This surely is the worst project I’ve ever attempted. Eeeek.” (31)
- “Oh, GOD, if I could start this project again and actually argue the case for junking the inherited program suite.” (37)
- “… this should all have been rewritten from scratch a year ago!” (45)
- “Am I the first person to attempt to get the CRU databases in working order?!!” (47)
- “As far as I can see, this renders the (weather) station counts totally meaningless.” (57)
- “COBAR AIRPORT AWS (data from an Australian weather station) cannot start in 1962, it didn’t open until 1993!” (71)
- “What the hell is supposed to happen here? Oh yeah — there is no ’supposed,’ I can make it up. So I have : – )” (98)
- “You can’t imagine what this has cost me — to actually allow the operator to assign false WMO (World Meteorological Organization) codes!! But what else is there in such situations? Especially when dealing with a ‘Master’ database of dubious provenance …” (98)
- “So with a somewhat cynical shrug, I added the nuclear option — to match every WMO possible, and turn the rest into new stations … In other words what CRU usually do. It will allow bad databases to pass unnoticed, and good databases to become bad …” (98-9)
- “OH F— THIS. It’s Sunday evening, I’ve worked all weekend, and just when I thought it was done, I’m hitting yet another problem that’s based on the hopeless state of our databases.” (241).
- “This whole project is SUCH A MESS …” (266)
Are you getting it yet Josh?This is NOT science. A scientist reveals everything and dares you to break it. This is a scam.
First US Army Group. The fake "Calais-invasion Army" that Patton "ran" to fox the Nazis.MSimon wrote:Didn't any one get FUSAG?
Google FUSAG in East Anglia.